Privacy Policy

1. Who we are

Répliq ("the App") is a theater rehearsal app operated by Evgenii "Johnny" Slakva ("we", "us"), who decides what is collected and why.

Questions, requests, and anything else described on this page reach a person at support@repliq.to.

2. The short version

We collect what the App needs to work, and nothing for advertising. We do not sell your data, we do not share it with advertisers, and we do not track you across other apps or websites.

What you create — your scripts, the voices you cast for them, the audio those voices produce — is stored on our servers, so that it reaches your other devices and the cast you share it with. Your own voice is not. Speech recognition happens on your device, and no recording of you ever reaches us.

3. Accounts

There are two kinds of account:

• A device account. Created automatically, with no sign-up, the first time you open the App with a connection. It has no name, no email, and no credentials — only an identifier for your installation and the time it was created. We compare that time with when you first took a play, imported a script or prepared one, to understand how people start using the App. It can hold everything section 4 describes, including scripts you prepare. Because it has no credentials, it cannot be recovered: if you delete the App without signing in, a new installation starts a new device account, and the scripts the old one held cannot be moved to it. Your subscription is not lost that way — it belongs to your Apple ID, and Restore Purchases brings it back. What the old device account held stays on our servers, no longer connected to any installation; if you restored your subscription on the new installation, write to us from the App and we can find the old account and delete it.
• A signed-in account. Created when you sign in with Apple. Signing in is required only to share a script you prepared and to set the name shown with it; everything else works without it. It is what lets your scripts follow you to another device and survive reinstalling the App. Signing in on a device that already has a device account claims that account, so nothing it holds is lost; if your Apple ID already has an account, what the device account holds is moved into it.

When you sign in, Apple gives us an identifier for you, your name as Apple provides it, and an email address. That address may be your real one or an Apple private-relay address, depending on the choice you make in Apple's sign-in sheet. We store all of these, plus a token that lets us revoke the sign-in when you delete your account. We use them to identify your account, to restore it on a new device, and to contact you about the service — never to market to you.

4. What we store on our servers

Répliq keeps your work on our servers, the way any app that syncs does, so that it reaches your other devices and the cast you share it with. The rule is simple: what you create in the App is stored on our servers. Section 5 is what never does.

• The work you create. The script text you paste, the roles and lines it was parsed into, the voices you cast for them, and the audio generated from them.
• What you do with it. The snapshot and code behind each script you share; which scripts you imported and where they came from, so that later corrections by their author reach you, and — when you arrived through a link or code we published — which of our campaigns it belonged to (for example, an email or a post), so we can tell which of our outreach brings people who go on to use the App; and which plays you took from the catalog.
• Your rehearsal practice. Which lines you have rehearsed, how well you know them, your bookmarks and your settings, so that your progress follows you from one device to another.
• Subscriptions. Your subscription status, supplied by our subscription-management provider from your App Store purchase. We never see your payment details — Apple handles payment and does not give them to us.
• Operational records. Server logs, job records, and per-request costs from the AI and voice providers, which we use to run the service, diagnose problems, prevent abuse, and understand what the service costs us. Logs contain technical data such as IP addresses and are not archived — see section 11.
• Diagnostic copies of AI requests. When your script is sent for parsing, we keep a copy of what we sent and what came back, so that we can investigate a script that parsed badly. This copy contains the submitted text. It is erased when you delete your account.
• Crash and error reports. When the App fails, it sends a report to a third-party error-reporting provider: what went wrong, where in the code it happened, and technical details of the device such as its model, operating system version and app version. These reports are configured to exclude your script text and your email address, and we use them only to find and fix faults. They are not linked to your account: a report carries a random identifier for the installation, never your account or your email.

5. What never reaches us

Your voice, and everything the App hears while you rehearse. Speech recognition is done by your device's own recognizer; no recording and no transcript is ever sent to us. This is not a detail of how the App happens to work today — it is how the App is built, and we do not intend to change it. Section 6 describes it in full.

Separately, the App keeps your downloaded scripts and their audio on the device, so that rehearsal works without a connection. Those are copies of what is already on our servers, and deleting the App removes them.

6. Speech recognition

Rehearsal listens to you speak your lines. Recognition is performed by your device's own speech recognizer, and no audio of your voice is ever sent to our servers — we receive nothing from it, not the audio and not the transcript. Depending on your device settings, Apple's speech recognition may process audio on the device or send it to Apple; that processing is governed by Apple's privacy policy, not this one.

7. How your script text is processed

Preparing a script sends its text to an AI service, which identifies the characters and splits the dialogue into lines, and then sends those lines to a text-to-speech service, which generates the character voices. Both are third-party providers acting on our instructions.

We keep copies of submitted text and of generated audio in caches, so that preparing the same material again does not repeat work that has already been paid for. Separately, each line of a prepared script keeps the one recording chosen for it, which is what makes everyone in a cast hear the same recording.

8. Third parties

We use a small number of providers to run the service. Rather than name each one — providers change, and a list here would go stale — we describe what they do:

• Apple, named because you meet it directly: Sign in with Apple, App Store billing, and your device's speech recognition.
• AI text processing, to parse a script into characters and lines.
• Speech synthesis, to generate character voices.
• Hosting, database and file storage, to run the service and store scripts and audio.
• Subscription management, to tell us whether your App Store subscription is active.
• Error and crash reporting, to find and fix faults in the App.
• Website analytics, to count visits to repliq.to.

These providers process data on our instructions and under their own terms, and may keep it for as long as their own policies allow, for example as a record of requests or for debugging and abuse prevention. We do not use your scripts to train AI models. Where a provider offers to exclude what we send from its training, we have taken that option. None of our providers is an advertising network. Your data may be processed in the United States and other countries.

9. Analytics

We do not use advertising networks, advertising identifiers, or cross-app tracking, and we do not build profiles of you.

We do measure how the service itself is used — for example how long rehearsals run, how many roles a script has, and where the App fails — so that we can make it work better and understand what it costs to run. We look at these measurements in aggregate, and they are not used to identify you or to contact you.

Campaign labels. Some of the links and codes we publish carry a short label naming the campaign they belong to. When you import a play through one, that label is stored with the import and linked to your account, so we can tell which of our outreach brings people who actually rehearse. It names our campaign, not you or the site you came from; it is not shared with anyone and not used for advertising.

The website. repliq.to counts visits — which pages are opened, which site sent you, and roughly where in the world you are — using a provider that sets no cookie. These counts are aggregate: they hold no identifier for you, they are not joined to your account, and nothing is stored on your device that would let us recognise you on a later visit. If you arrive through one of our campaign links, the site keeps that campaign's label in your browser for up to 30 days, so that the App Store link you tap later still names the campaign; the label is the same for everyone who used that link, and it never leaves your browser except as part of that App Store link.

10. Age

Répliq is rated 13+ and is intended for people aged 13 and over. It is not directed to children under 13, and we do not knowingly collect personal information from them. We do not collect anyone's age.

If you are a parent or guardian and believe a child under 13 has an account with us, write to support@repliq.to and we will delete the account and its data.

11. How long we keep things

• Your account and scripts — until you delete them, or delete your account. For a device account left behind when the App is deleted without signing in, see section 3.
• Shared snapshots — a share code expires after 7 days; the snapshot behind it remains available to people who already imported it, so that their copy keeps working.
• Diagnostic copies of AI requests — until you delete your account.
• Cached copies of submitted text — up to 30 days from when the text was first submitted, then deleted automatically. This cache is keyed by the text itself, not by who sent it, so deleting a script or your account does not remove it early; it expires on the same schedule.
• Generated audio — kept indefinitely, whether it is attached to a script or held in the synthesis cache. The cache is keyed by the words and the voice, not by who asked, so the same line in the same voice is one recording for everyone; it holds nothing about you or your account. See section 12.
• Server logs — we do not archive them. They exist only in our hosting provider's recent-log stream and age out there.
• Crash and error reports — one year.
• Cost and billing records — kept indefinitely, as records of what the service cost to provide. They hold amounts and counts, never a word of your script text.

12. Deleting your account

You can delete your account from within the App, in Settings — Delete Account if you signed in, or Delete my data if you never did. Deleting removes your scripts and their text from our servers, revokes your Apple sign-in if you had one, and withdraws every share code you created, so no one can import from you again. You then choose what your device keeps: its copies of your scripts, which stay rehearsable there but no longer sync, or nothing, in which case the App deletes them and starts again as if newly installed.

Four things deliberately survive, and none of them identifies you:

• Copies of scripts you shared, kept for the people who already imported them, so that a cast does not lose its script mid-rehearsal. They no longer name you.
• Cost records, kept as an account of what the service spent.
• Generated audio files, because the same recording can be part of a script someone else imported. Once your account is gone, nothing links them to you.
• Cached copies of submitted text, for up to 30 days after they were first submitted (see section 11). They are keyed by the text, not by you, and expire on their own.

13. Your rights

You can ask us for a copy of the data we hold about you, ask us to correct it, ask us to delete it, or object to how we use it. Write to support@repliq.to and we will respond within 30 days.

We process your data because it is necessary to provide the service you asked for, because we have a legitimate interest in keeping the service working and free of abuse, and — for the records above that we must keep — because the law requires it. Depending on where you live, you may also have the right to complain to your local data protection authority.

14. Changes to this policy

We may update this policy. When we do, we will change the "Last updated" date above, and if the change affects what we collect or why, we will say so in the App before it takes effect.

15. Contact

Questions about this policy? Email us at support@repliq.to.