Informativa sulla privacy

The short version

• Your recordings never leave your device. Not with an account, not without one. There is no setting that changes this and no server of ours that could hold them.
• Without an account, nothing at all leaves your device except an optional crash report. You can write, prompt and record without ever telling us who you are.
• With an account, your scripts sync — and only your scripts. The title and the text, so the phone and the browser show the same library. You can delete the account, and its scripts, at any moment.
• Voice following never sends your speech to us. The phone asks Android to recognise it, the browser asks the browser maker. We receive words, use them to find your place, and throw them away. Section 5 explains this in full.
• Advertising exists on the articles, and nowhere else. Not in the browser app, not in the Android app, and never on the prompter screen, where somebody is reading aloud on camera. Advertising pays for the writing; it has no business beside your own.
• We do not sell your personal information and we do not share it for cross-context behavioural advertising. The rest of this document is the detail behind those points, written so it can be checked rather than taken on trust.

1. Who is responsible for your data

The controller of the personal data described here — the data controller under the GDPR, the business under United States privacy laws, the controlador under the LGPD and the responsable under the Mexican LFPDPPP — is:

Ilya Yarshou, sole trader (jednoosobowa dzialalnosc gospodarcza), Jana Piltza 42/5, 30-392 Krakow, Poland. Registered in the Central Registration and Information on Business (CEIDG). NIP 6762498757, REGON 542473948.

Privacy enquiries: privacy@followscript.com. Everything else: support@followscript.com.

We have not appointed a data protection officer, because the scale and nature of the processing described here does not require one under Article 37 GDPR. Enquiries from any country, in any of the languages this app supports, reach a person at those addresses.

2. What stays on your device

Followscript is built to work without an account, and most of what it holds never has anywhere else to be. The following are written to your phone, or to your browser's own storage, and are never transmitted to us:

• Your takes — the video and audio you record, with their duration, date and the script they belong to. These never leave the device under any circumstance. Signing in does not upload them, and there is no plan that would. What you export, you export yourself, to wherever you choose.
• Your settings — speaking pace, font size, mirroring, where the reading line sits, chosen resolution, interface language, and whether crash reporting is on. These describe the screen you are reading from, so they belong to that screen and are not synced.
• Your scripts, when you are signed out — the text you type, paste, import from a file, or receive through the Android share sheet.
• Recovery information — a small file naming a recording that was interrupted, so the app can tell you what happened next time you open it. It is deleted once you have dealt with it. On Android these live in the private storage area the operating system gives every app. In a browser they live in that browser's own storage for followscript.com, which means clearing site data removes them and a private window forgets them when it closes. Uninstalling the app removes its private storage. Anything you exported is yours to keep or delete.

3. Your account, and what syncing carries

An account exists so that a script written on a laptop can be read from a phone. It is optional, it is free, and the app is fully usable without one.

What we hold when you have an account

• An identifier for you. The stable identifier Google gives us for your account, plus your email address as a label so the account screen can tell you which account you are in. There is no password: signing in is Google and nothing else, so there is nothing of that kind for us to hold.
• Your scripts — the title, the text, the times you created and last edited them, and a marker when you delete one, so the deletion travels to your other device instead of the script reappearing. This is the whole of what syncing carries.
• Your sessions — one row for each device signed in, holding a hash of the session credential, a coarse label such as "Chrome on Windows" or "Pixel 8" so you can recognise a device you do not use any more, and the dates it was opened and last used. That is the complete list. There is no analytics attached to an account, no record of when you prompt or for how long, no count of your takes, and no profile built from any of it.

What syncing does not carry

Your recordings. Your settings. Anything the microphone hears. These stay where section 2 says they stay, whether or not you are signed in.

Deleting the account

Settings, Sync, Delete this account in the app, or the account panel in the browser, or by writing to privacy@followscript.com. There is also a page for it at followscript.com/account-deletion, which explains the same thing.

Deleting removes the account row, the identity behind it, every session, and every script we hold for it. It is a deletion, not a flag, and it is not reversible. Backups taken before the deletion are overwritten on their own schedule, within 30 days.

The copies on your own devices are untouched. We have no way to reach into your phone or your browser, and closing an account is not the moment we would start.

4. Signing in, and keeping you signed in

With Google. Google tells us a stable identifier for your account, your email address and whether Google has verified it. Nothing else — not your name, not your picture, not your contacts. We check what Google sends and then discard Google's own token; every request afterwards is between your device and us.

There is no other way in, and that is the point. We hold no password, so there is none to be guessed, reused from another site, or stolen from us. There is no reset link and no confirmation link, because there is no password to reset and no address for us to prove — Google has already proved it. The whole class of harm that comes from a service storing credentials does not arise here, because this service stores none.

Staying signed in uses a credential stored on your device: on Android in the app's private storage, excluded from Android's cloud backup so a restored backup cannot carry a working session; in a browser in a cookie the page itself cannot read. Sessions expire after 60 days of not being used, and signing out ends them immediately at our end as well as yours.

5. Voice following and speech recognition

The feature that makes Followscript what it is — text that waits for you rather than scrolling on a timer — works by listening to you speak and matching what it hears against the words in your script. That matching happens on your device, in both the app and the browser. Your script is never sent anywhere for it.

Followscript does not do the recognition itself. It asks the platform, and this is the one place where your voice may leave your device:

• On Android, the operating system speech recognition service. Where that service runs on the device, your speech is processed locally. Where it runs in the cloud — which on most Android phones means Google, as the provider of the default service — the audio is sent by Android to that provider and handled under that provider's terms and privacy policy, not ours.
• In a browser, the Web Speech API. Chrome sends the audio to Google's recognition service; Safari sends it to Apple's. Again under their terms, not ours. Firefox has no implementation, so voice following is unavailable there and the prompter says so and offers a steady scroll instead. In every case Followscript receives only the recognised words, uses them to decide where you are in your script, and discards them. We never receive your audio, we never store the transcription, and none of it is sent to us or to anyone else by us. If you would rather nothing was processed this way, use manual or auto mode, where the script scrolls at a pace you set and the microphone is not used for following at all. Recording a take still uses the microphone to capture sound into your video, but that audio is written to your file and nowhere else. We say this plainly because it is the part of the app most likely to matter to someone reading a privacy policy carefully, and burying it would be dishonest.

6. Crash reports

A crash nobody hears about is a crash that keeps happening to everybody, so the Android app can send a diagnostic report when it fails. This uses Firebase Crashlytics, provided by Google. It is on by default and you can switch it off at Settings, Send crash reports, immediately and permanently, which also deletes any reports still queued on your device.

Sent in a crash report

• The stack trace: which line of our code failed.
• Device model, operating system version, orientation.
• Free memory and storage at the moment of the failure.
• The app version and build.
• A Crashlytics installation identifier, specific to that installation and reset when the app is reinstalled or its data cleared.

Never sent

• Your script text.
• Your recordings, video or audio.
• Your name, email address or phone number.
• Any advertising identifier.
• Your location. The app also records short technical breadcrumbs — that a recording was being finalised, for example — so a stack trace can be understood. These describe what the app was doing, never what you wrote or recorded. Firebase Analytics is deliberately not included in Followscript. We do not measure how you use the app, which screens you open, or how long you spend in it. Google acts as our processor for Crashlytics.

7. Permissions the app asks for

Android grants each of these only when you allow it, and you can withdraw any of them at any time in your phone settings. Refusing one disables the feature that needs it and nothing else.

• Camera — to show the viewfinder and record a take. Video is written to your device.
• Microphone — to follow your voice through the system recognition service, and to record sound into your take.
• Notifications — to show the recording notification Android requires while a take is in progress, so a recording can never run silently in the background.
• Display over other apps — for the floating prompter, so your script can sit above another camera or streaming app. Requested only if you turn that feature on.
• Access to a file you choose — to import a .txt or .docx script. Android hands the app that one file; it cannot browse your storage. The app requests no permission for contacts, location, calendar, call logs, SMS, or your photo library at large. In a browser the only permission asked for is the microphone, and only when you start voice following. The browser asks, not us, and you can withdraw it in the browser's own site settings.

8. Purchases and subscriptions

Followscript Pro is sold through Google Play. Google processes the payment, and in the European Economic Area Google is the seller of record. We never receive your card number, your bank details, your billing address or your name from a purchase.

What we do receive from Google, solely to unlock what you paid for and to answer support requests, is confirmation that a purchase exists together with an anonymous purchase token, the product bought and its status. Where you have an account, that entitlement is attached to it so the subscription follows you rather than the handset.

If you contact us about a payment we may need your Google Play order number, which you would be providing to us yourself.

9. The website and the browser app

followscript.com carries three things: pages to read, the browser version of the prompter at /app, and this document.

Our hosting provider records the usual technical entries for each request — IP address, time, the page requested, the referring page, the browser and operating system version — to keep the site running and defend it against abuse. Those logs are kept for no longer than 30 days and are not combined with anything else.

Measurement

The website and the browser prompter use Google Analytics 4 to count visits: how many people open a page, which pages, roughly where in the world, on what kind of device, and whether they come back. We look at it to answer one question we cannot answer any other way — whether the browser prompter is used at all, and whether that number is growing.

Four rules govern it, and they are enforced in the code rather than promised in prose:

• Nothing loads before you consent. No Google script is fetched and no cookie is set until you accept. Declining loads nothing from Google at all — not a script, not a cookie, not a single request to it — and you are not asked again.
• You are never named to it. No account identifier, no email address, no user id is ever sent. Google sees an anonymous visitor. What section 4 says stays true: there is no analytics attached to your account, and nothing here can be joined to one.
• Nothing you write is sent. The address of a script you are editing carries an identifier your own browser invented, never its title and never its text. The page title is fixed. What you write is not read, sampled or summarised.
• You can change your mind at any time. "Cookie settings" in the footer — on the website and on the app's own screens — clears the decision and asks again. Withdrawing stops any further collection. Unlike advertising, this does run on the prompter screen, and the difference is deliberate. An advert beside a running take competes for the attention of somebody reading aloud to a camera; a page count does not, and without it we would not know the browser prompter had any users. Google acts as an independent controller for Analytics under its own policies.

Reading counts on the articles

The articles also count their own readers, on our server and without Google. This is how we learn which articles are read, which are left within seconds by somebody arriving from a search engine, and which lead somebody on to try the prompter.

• Nothing is stored in your browser. No cookie, no local storage, no identifier kept on your device. There is nothing to accept or decline, because nothing is placed there.
• You are recognised for one day at most. Your IP address and your browser's user-agent string are combined with a random value that changes every day and turned into a one-way code. The IP address itself is not stored. The day's random value is deleted when the next day begins, and from then on nobody, us included, can tell whose code it was.
• What is recorded is small. Which article was opened and when, whether it was the first page of the visit, the kind of place the visit came from — a search engine, an AI assistant, social media, email, an advert, another website, another page of this one, or none — and clicks on the article's buttons and on links into the prompter. The address of the page you came from is used to tell those kinds apart and is not kept. How far you scrolled and how long the page was on screen are used once, to decide whether a visit from a search engine ended within seconds, and are not kept either.
• It runs on the articles and nowhere else. Not on the prompter, not in the browser app, not in the Android app. Visits by known crawlers and by the site's administrator are not counted.

Advertising

The articles carry Google AdSense. Three rules govern it, and they are enforced in the code rather than promised in prose:

• Nothing loads before you consent. No advertising script is fetched and no advert is requested until a consent platform records your decision. Declining leaves the space empty. In the European Economic Area and the United Kingdom this runs through a certified Transparency and Consent Framework platform; where that framework does not apply, our own consent record governs.
• Never on the prompter. The screen where somebody is reading aloud in front of a camera carries no advertising, and an advert refreshing beside a running take is worse still. This is not a setting.
• Nothing of yours is passed to it. Your scripts are not read, sampled, summarised or used to target anything. The advertising script sees the page it is on, and what your browser tells it, exactly as it would on any other website. Where you consent to personalised advertising, Google processes that as an independent controller under its own policies. Where you decline, adverts are non-personalised or absent. You can change your mind at any time through the consent link in the footer.

The Android app has none of this

There is no advertising SDK and no analytics SDK inside the Android app, and adding one would be a material change announced under section 16 before it happened.

10. Why we are allowed to do this

For people in the European Economic Area, the United Kingdom and Switzerland, Article 6 GDPR requires a lawful basis for each purpose.

• Running the app on your device — performance of a contract, Art. 6(1)(b).
• Keeping an account and syncing your scripts — performance of a contract, Art. 6(1)(b). You asked for the account; this is what it does.
• Keeping you signed in, and ending sessions — performance of a contract, Art. 6(1)(b).
• Unlocking a Pro subscription — performance of a contract, Art. 6(1)(b).
• Crash reports — legitimate interests, Art. 6(1)(f), and you can object at any time by using the switch in Settings.
• Server logs and security — legitimate interests, Art. 6(1)(f).
• Measuring visits to the website and the browser app — consent, Art. 6(1)(a), withdrawable at any time, and nothing is loaded before it is given.
• Counting readers of the articles — legitimate interests, Art. 6(1)(f): knowing which articles are read is how we decide what to write next, and the count is built so that it cannot follow you past the end of the day. Nothing is stored on your device for it. You can object at any time by writing to privacy@followscript.com.
• Advertising on the website and in the browser app — consent, Art. 6(1)(a), withdrawable at any time, and nothing is loaded before it is given.
• Answering you when you write to us — legitimate interests, Art. 6(1)(f), or legal obligation where accounting law applies.

11. How long anything is kept

• Takes, settings, and scripts held only on your device — for as long as you keep them. We hold no copy and no schedule applies to us.
• Scripts synced to an account — until you delete the script or the account. A deleted script leaves a marker with no text in it, kept so the deletion can reach your other devices, and removed once every device has seen it.
• Account and identity — until you delete the account.
• Sessions — 60 days from last use, or immediately when you sign out.
• Crash reports — retained by Crashlytics on Google's standard schedule, up to 90 days, and deleted when you switch reporting off.
• Visit measurement — retained by Google Analytics on the property's own schedule, currently 14 months, and no longer collected at all once you withdraw consent.
• Reading counts on the articles — the daily random value is deleted when its day ends, and from then on the records cannot be linked to anyone. They are kept as anonymous statistics for as long as the article exists.
• Server logs — up to 30 days.
• Backups of the account database — up to 30 days, after which a deletion is complete everywhere.
• Support correspondence — up to 24 months after the matter is closed.
• Invoices and accounting records — for as long as Polish tax law requires, currently five years from the end of the tax year.

12. Who else is involved

• Google Ireland and Google LLC — Google Play distribution and payments, Firebase Crashlytics, Google sign-in, Google Analytics on the website and the browser app, AdSense, and speech recognition where the platform uses it. European Union and United States.
• Apple Inc. — speech recognition in Safari, where you use it. United States.
• Our website and application hosting provider — serving followscript.com and holding the account database described in section 3. European Union.
• Our email provider — receiving and answering the messages you send us. European Union. Followscript itself sends you no email at all. Beyond these, we disclose personal data only where we are legally compelled to — a valid order from a court or public authority — or to establish, exercise or defend a legal claim. We do not sell personal information, and we do not share it for cross-context behavioural advertising. If Followscript were ever sold or transferred, you would be told before any personal data changed hands.

13. Transfers outside your country

The account database, including the text of synced scripts, is held inside the European Economic Area.

Crash reports are processed by Google, which may process them in the United States. Speech sent by your platform to Google or Apple for recognition may be processed outside your country under their policies. Where personal data leaves the European Economic Area through us, the transfer relies on the European Commission standard contractual clauses together with our providers' certification under the EU-US Data Privacy Framework, and on equivalent safeguards for the United Kingdom and Switzerland.

For people in Brazil, these are international transfers under Articles 33 to 36 LGPD and rely on the same contractual safeguards. For people in Mexico, transfers to our providers are those necessary for the relationship between you and us under Article 22 of the LFPDPPP, and no separate consent is required for them.

14. Children

Followscript is for adults. Section 2 of the Terms of Use sets the minimum age at 18, we do not direct the app at anyone younger, and we do not knowingly collect personal data from them. That threshold is deliberately above every age the law sets — 13 in the United States under COPPA, 16 in much of the European Union, 12 in Brazil for the special protections of Article 14 LGPD, 18 in India under the DPDP Act — so that no question about age turns on where you live.

An account can be opened with an email address, and we do not verify age when it is. If you believe someone under 18 has an account here, tell us at privacy@followscript.com and we will close it and delete what it holds.

15. Your rights, wherever you are

Write to privacy@followscript.com to exercise any of the rights below. We answer within one month, and within any shorter period your own law requires. We never charge for this and we never treat you differently for asking.

Two things are worth knowing before you write.

What we can act on. If you have an account, we hold what section 3 lists and can give you a copy of it, correct it, or delete it. Deleting the account does all of that at once, and you can do it yourself without writing to anybody.

What we cannot act on. Your recordings, your settings, and any script you have not synced are on your device and not with us. A request to access or delete those is something only you can carry out, in the app or by uninstalling it. We will always tell you plainly when that is the case rather than sending you an empty file.

European Economic Area, United Kingdom and Switzerland

• Access to your personal data and a copy of it (Art. 15), and portability in a machine-readable form (Art. 20).
• Rectification of anything inaccurate (Art. 16) and erasure (Art. 17).
• Restriction of processing (Art. 18) and objection to processing based on legitimate interests (Art. 21) — which for crash reports is simply the switch in Settings.
• Withdrawal of any consent you gave, at any time, without affecting what was lawful before (Art. 7(3)) — which for advertising is the consent link in the site footer.
• A complaint to your supervisory authority. Ours is the Polish Urzad Ochrony Danych Osobowych, ul. Stawki 2, 00-193 Warsaw. You may equally complain to the authority where you live or work. No decision producing legal or similarly significant effects is made about you by automated means. There is no profiling.

United States

If you live in California, Colorado, Connecticut, Virginia, Utah, Texas, Oregon, Montana or another state with a comprehensive privacy law, you have the right to know what personal information is collected and for what purpose, to obtain a copy of it, to correct it, to delete it, and to appeal a refusal. You may use an authorised agent, and we will not discriminate against you in any way for exercising these rights.

For the twelve months before the date of this policy, the categories collected were identifiers (an email address and a provider identifier where you have an account; a Crashlytics installation identifier; an IP address in website logs; a one-way code on the articles that changes every day), internet or device activity (device model, operating system, app version, crash diagnostics, pages requested), and, only where you have an account, the content of the scripts you chose to sync. They come from you and from your device, and are used for the purposes in section 10. We have not sold personal information, and we have not shared it for cross-context behavioural advertising, in that period or ever. Advertising on the website is shown only with consent and is not personalised without it. We do not collect sensitive personal information for the purpose of inferring characteristics, so no right to limit its use arises. We honour Global Privacy Control signals sent by your browser on followscript.com.

Brazil

Under Article 18 of Lei 13.709/2018 you may ask us to confirm whether we process your data; to give you access to it; to correct incomplete, inaccurate or out-of-date data; to anonymise, block or delete data that is unnecessary, excessive or processed unlawfully; for portability; for deletion of data processed on the basis of consent; for information about with whom we have shared it; for information about the consequences of refusing consent; and to withdraw consent.

Requests, and any complaint, go to privacy@followscript.com, which is also the contact for our person responsible for data protection (encarregado) under Article 41 LGPD. You may also complain to the Autoridade Nacional de Protecao de Dados (ANPD).

Mexico

This document serves as our privacy notice (aviso de privacidad integral) under the LFPDPPP. The responsable is Ilya Yarshou, at the address in section 1. The categories of personal data are those in sections 2 to 9; we do not collect sensitive personal data and we carry out no asset or financial data processing.

The purposes necessary for the relationship between us are: providing the app, keeping an account and syncing scripts where you ask for one, unlocking a purchase, diagnosing faults, and answering you. There are no secondary purposes and no marketing purposes, so there is nothing you need to opt out of; if that ever changes you will be told before it takes effect and given a way to refuse.

You may exercise your ARCO rights — access, rectification, cancellation and opposition — and limit the use or disclosure of your data, by writing to privacy@followscript.com with your name, a means of contacting you, proof of your identity, and a clear description of what you want. We answer within 20 business days and act within 15 further business days, as the law provides. If you are not satisfied you may go to the authority responsible for data protection oversight, currently the Secretaria Anticorrupcion y Buen Gobierno.

16. Security

Most of what protects you here is architectural rather than technical: the material most worth protecting is not ours to lose. Your recordings never reach us. Your scripts reach us only if you ask for an account, and only their text.

For what we do hold:

• We store no passwords at all. Signing in is Google and nothing else, so there is no credential of yours in our database to read, to leak, or to strengthen later.
• Session credentials are stored as hashes too. A leaked copy is a list of hashes, not a list of working sessions, and any session can be revoked at our end immediately.
• The browser never holds a credential a script on the page could read. The session lives in a cookie the page cannot see, which is why an injected script cannot walk off with your account.
• The database is inside the European Economic Area, reachable only over an encrypted connection, and access to it is limited to the person named in section 1.
• The website and the API are served only over HTTPS. Your device still does most of the work: your recordings and unsynced scripts are protected by your phone's storage isolation, or your browser's, and by whatever lock screen and device encryption you use. Keeping your device locked and updated matters more here than anything we could do at our end. If a breach ever occurred that was likely to result in a risk to your rights, we would notify the competent supervisory authority within 72 hours and tell you directly where the law requires it.

17. Changes to this policy

When we change this policy we update the date at the top. If a change is material — a new purpose, a new recipient, a new category of data — we will say so prominently in the app before it takes effect, and where the law requires consent we will ask for it rather than assume it. Earlier versions are available on request.

What changed on 10 September 2026. Optional accounts and script syncing were added, along with a browser version of the prompter that carries advertising. The earlier text said Followscript had no account and no server; that is no longer true if you choose to sign in, and sections 3, 4, 9, 10, 11, 12 and 16 are new or rewritten to describe exactly what an account holds. Two things did not change and are stated more plainly than before: your recordings never leave your device, and without an account nothing does.

What changed on 11 September 2026. Signing in is now Google and nothing else. Accounts made from an email address and a password are gone, and so is everything that existed to serve them: the stored password hashes, the reset links, and the confirmation links. We now hold no credential of yours of any kind. Advertising left the browser app entirely: it appears beside the articles and nowhere else, so no screen you write or read on carries any.

What else changed on 11 September 2026. The website and the browser prompter now count visits with Google Analytics, which section 9 describes in full. It is a new recipient and a new purpose, so it is asked for rather than assumed: nothing is loaded until you accept, declining loads nothing, and "Cookie settings" in the footer takes the decision back. Nothing you write is sent to it and your account is not named to it — the list in section 4 is unchanged. The Android app is unaffected and still contains no analytics SDK of any kind.

What changed on 24 September 2026. The articles now count their own readers on our server, as the new part of section 9 describes: nothing is stored in your browser, you are recognised for one day at most, and the IP address is not kept. Google Analytics is unchanged and still needs your consent; the sentence saying that declining loads nothing now says, more precisely, that it loads nothing from Google. The prompter, the browser app and the Android app are unaffected.

18. How to reach us

Privacy: privacy@followscript.com

Support: support@followscript.com

Account deletion: followscript.com/account-deletion

Post: Ilya Yarshou, Jana Piltza 42/5, 30-392 Krakow, Poland

This policy is drafted in English. Translations are provided so you can read it in your own language; where a translation and the English text differ, the English text governs, except where your own consumer law provides otherwise.