Last updated 25 September 2026 · Applies to the Sipra app for iOS, and to getsipra.app
You practise difficult conversations in this app, out loud, in your own voice. That is personal material. This policy is written to be read rather than to protect me — if any part of it is unclear, write to me and I will fix the wording.
Sipra is published by ChantSolutions LLC, a single‑member management consulting and professional training company in Murfreesboro, Tennessee, United States. Siprachanh Chanthaphaychith is its sole member, and the person who answers when you write to support@getsipra.app.
Your recordings, your practice history and your progress are all stored on your device. There is no Sipra database holding them. Three things leave your phone: your account identity — your name and email address — so that signing in works; a request for a practice drill, which says which kind of drill you want and proves you are a signed‑in Sipra user; and, if you subscribe, the record of that purchase, so the app knows what you have paid for.
This is not a promise about how carefully your practice is guarded on a server. No server holds it. Sipra does have one small server function — it writes a fresh drill and hands it back — but it stores nothing and is told nothing about you. That is a design decision, and it is the reason most of the table below says “never collected.”
Recording happens only when you tap record. There is no background listening and no always‑on microphone. Decline the microphone permission and every drill still works — you simply cannot record or play back.
Recordings are written to your device’s own storage, with sensitive values held in the platform’s encrypted store — the Keychain on iOS, the Keystore on Android. They are not uploaded, not backed up to my systems, not analysed remotely, and not sent to any AI service. I cannot hear them, and neither can anyone else.
Delete an individual take, or every recording at once, from the Account screen. Because they live on your phone, uninstalling the app removes them too.
“Collected” here means what Apple and Google mean by it: data that leaves your device and is kept.
| What | Why | Where it lives |
|---|---|---|
| Your name, email address and account identifier | Sign‑in is handled by Google or by Apple through Firebase Authentication, so your practice belongs to your account. Sipra never sees or stores your Google or Apple password. | Collected. Held by Firebase Authentication until you delete your account. |
| Sign‑in technical data | Firebase Authentication records the ordinary details of a sign‑in — a timestamp, the IP address at that moment. Used to keep sign‑in working and to stop abuse. | Collected by Google, per Firebase’s own retention — a short operational window. |
| A request for a drill | When the app needs a fresh drill it asks Sipra’s server for one, sending a single word — “story,” “strategy” or “decision” — together with the sign‑in token that proves you have a Sipra account. The token is there so that strangers cannot run up the bill on an open endpoint. No audio, and nothing you have written, ever travels with it. | Not kept. The request is answered and discarded. Google logs the calling IP address for a short operational window, as it does for any web request. |
| Your subscription status | If you subscribe to Sipra Pro, Apple handles the payment and RevenueCat records what you bought so the app knows to unlock it — on this phone and on any other you sign in to. RevenueCat receives the transaction, your Sipra account identifier, and ordinary device details such as model, operating system version and country. | Collected. Held by RevenueCat and by Apple while the subscription exists. Sipra never sees your card, and Apple never gives it to me. |
| Your subscription status | If you subscribe to Sipra Pro, Apple handles the payment and RevenueCat records what you bought so the app knows to unlock it — on this phone and on any other you sign in to. RevenueCat receives the transaction, your Sipra account identifier, and ordinary device details such as model, operating system version and country. | Collected. Held by RevenueCat and by Apple while the subscription exists. Sipra never sees your card, and Apple never gives it to me. |
| Your voice recordings | So you can hear yourself and compare over time. | Never collected. On your device only. |
| Your practice activity, streak and progress | So the app can pick up where you left off. | Never collected. On your device only. |
Sipra asks an AI model to write your practice drills. The model is told nothing about you. Anthropic receives one word — which kind of drill is wanted. Your audio, your answers, your name, your email address and your account identifier are never part of it.
Mechanically: the app calls a small server function published by ChantSolutions LLC, which asks Anthropic’s Claude to write a drill and passes the result back. The instructions Claude receives are written in advance and stored on the server. Nothing you type, say or record is added to them — which means the request Anthropic sees could have come from any Sipra user, because there is nothing in it that tells one apart from another.
The app’s request to that function does carry your sign‑in token, so the server knows a real Sipra account is asking. That is where it stops: the token is checked and discarded, and it is never forwarded to Anthropic. Without it the endpoint would be open to anyone who guessed the address.
Nothing is stored along the way. The function keeps no record of what it generated or who asked for it, and there is no database behind it. If the request fails, the app falls back to drills written by hand and you carry on without noticing.
If this ever changes — a different provider, or a request that carries something of yours — the date at the top of this page changes and the app tells you before it happens, not after.
| Service | What it does |
|---|---|
| Google Firebase Authentication | Sign‑in only. Sipra uses no Firebase database. |
| Google Sign‑In and Sign in with Apple | Account creation, whichever you choose. |
| Google Cloud Functions | Runs the small ChantSolutions function that fetches a drill. It stores nothing. Google logs the calling IP address briefly, as it would for any web request. |
| Anthropic | Writes the practice drills, from fixed instructions that contain nothing about you. Anthropic receives no audio, no words of yours and no account identity. |
| RevenueCat | Records your Sipra Pro subscription so the app knows what to unlock, and so it follows you to a new phone. Receives the transaction, your account identifier and ordinary device details. Receives no audio, no practice history and no recordings. |
| Apple (App Store payments) | Takes the payment if you subscribe. Sipra never sees your card or billing details. Apple’s handling of them is governed by Apple’s policy, not this one. |
| Apple and Google | Distribute the app. What they collect through the App Store and Google Play is governed by their policies, not this one. |
Nobody else. No analytics vendor, no mailing‑list service, no CRM, no marketing pixel, no advertising network.
If you have already uninstalled Sipra, or you cannot sign in, use the account deletion page and I will remove your sign‑in record for you.
If you are somewhere with statutory data‑protection rights — the GDPR in the EU and UK, the CCPA in California — these controls are how you exercise them. You can also write to me directly and I will handle it by hand. Because the only thing held off your device is your account identity, a request for a copy of your data is a short answer.
Microphone. Requested only so you can record your practice answers, and used only while you are actively recording. Decline it and the rest of the app works normally.
Sipra is built for adults handling adult situations — workplace conflict, negotiations, difficult conversations at home. It is not directed at children under 13, and I do not knowingly collect data from them. If you believe a child has created an account, write to me and I will delete it.
Sipra is a one‑person operation in Tennessee. California’s CCPA/CPRA and Tennessee’s TIPA both apply above revenue and volume thresholds far larger than this, so neither currently binds it. The design above exists because it is the right way to handle what people put into an app like this, not because a regulator is asking.
If that changes — if Sipra grows into those thresholds, or reaches users in the EU or UK where the GDPR applies regardless of size — this policy will be updated before it does, not after.
If this policy changes in a way that affects what is collected or who receives it, the date at the top changes and the app tells you the next time you open it. Cosmetic corrections will not.
support@getsipra.app
ChantSolutions LLC · Murfreesboro, Tennessee, United States