What Atween Collects
This list was compiled from the Atween source code and database schema, not from a template. It states what the software actually collects today. It becomes effective together with the Privacy Policy.
Nothing here is collected unless you use the feature it belongs to. Refusing an optional permission or declining to provide optional information does not cut you off from recording, deletion, export, closing your account, complaints, or safety resources.
1. What we collect
| When | What | Why | How it reaches us |
|---|---|---|---|
| Signing in | An irreversible keyed hash of your email address; account identifier; sign-in time; device session; the security records needed to spot a stolen account | To create and protect the account | You type the address; we hash it and discard the address. Your email address itself is not stored. |
| Writing a record | The text you write; the time; your corrections; the understanding derived from it; source references; the retention you chose; the deletion watermark | To record, to review, and to reduce how often you have to explain the same thing twice | You write it; you confirm whether it is kept or for this session only |
| Speaking | The transcript text, after you have seen and accepted it; how long you spoke; and the identity, version and checksum of the on-device model that produced it | To turn speech into a record you can edit and keep | Transcribed on your device. The audio itself is never sent to us. Your words are sent as text. |
| Confirming delivery to the other person | The item you confirmed; the relationship identifier; delivery and withdrawal status | To deliver exactly what you confirmed, and nothing else | You confirm it, item by item |
| Managing long-term understanding | Whether it is switched on; understanding fragments; source references; versions; your corrections; deletion records | To keep understanding viewable, correctable and deletable by you | You switch it on; you confirm what is kept |
| Consent | What you consented to, the version, the time, any withdrawal, and the receipt number | To be able to show what you agreed to and when | You accept or withdraw |
| Exercising your rights | Request type and scope; submission time; task status; export-package status; deletion watermark; failure reason; receipt number | To carry out the request and give you a receipt | You submit it; status is generated by the system |
| Buying | Order identifier; product identifier; purchase and refund status; the store's receipt or purchase token; entitlement status | To grant, verify and refund the purchase | Returned by the App Store or Google Play. We never see your card or bank details. |
| Sending feedback or a complaint | What you describe; account identifier; where in the product you were; the time; ticket record; outcome | To handle the problem and let you appeal | You provide it |
| Throughout | Application version; network status; rate-limiting records keyed on a hash of your IP address | To keep the service running and to stop abuse | Automatic. Your IP address is not stored as an IP address. |
2. What we do not collect
These are stated because their absence is checkable, not because the list has to be long.
- Your photographs. Pictures you take or select are handled on your phone. This version has no path that sends an image to the service; what it saves is the text you write.
- Your voice recordings. Speech is transcribed on the phone; what reaches the service is the transcript you accept.
- Your email address in readable form. Only an irreversible keyed hash is stored.
- Your phone number. Atween does not use phone numbers and has no field to store one.
- Third-party account information. There is no sign-in with Apple, Google or any other account, so there is no open identifier, nickname or avatar to collect.
- Location. No location permission is requested on either platform.
- Contacts, calendar, health data, Bluetooth or call logs. None are requested.
- Advertising or tracking identifiers. There is no advertising SDK, no attribution SDK, and no cross-app tracking.
- Crash logs and performance telemetry. There is no crash-reporting or analytics SDK in the application.
- Push notification identifiers. Atween sends no push notifications and integrates no push service.
- Biometric data. Atween does not use Face ID, Touch ID or Android biometric unlock.
- Your date of birth or your age. You affirm that you are an adult; we do not ask how old you are.
3. What the other person can see
Only the items you have confirmed for delivery, one by one. This is enforced in the data model: an item is visible to them if and only if you set delivery confirmation on it. Your originals, drafts, transcripts and derived understanding are not visible to them, and we do not tell them when you opened something, whether you read it, or whether you are online.