Scrivo Privacy Policy
Effective date: July 3, 2026
Scrivo (“the app”) is a voice transcription app developed and published by Squaretech (“we”, “us”). Scrivo is built to be private by design: your recordings are transcribed on your device, and your audio and transcripts are stored only on your device. We do not operate any server that receives, stores, or processes your recordings or transcripts.
This policy explains what data the app handles, what (little) leaves your device, and the choices you have. It applies to the Scrivo mobile app distributed through the Apple App Store and Google Play.
- Your audio and transcripts never leave your device, unless you choose to send them somewhere (via the share sheet or a webhook destination you configure).
- Speech recognition and AI features run entirely on-device using Apple and Google system frameworks and a locally downloaded language model.
- We collect anonymous usage and diagnostic events (no content, no names, no location) through PostHog, hosted in the European Union. You can turn this off at any time in the app’s settings.
- We have no user accounts, show no ads, use no tracking across apps or websites, and never sell data.
1. Data that stays on your device
The following data is created and stored locally on your device, in the app’s private storage. It is never transmitted to us:
- Audio recordings you make with the microphone, and audio files you import or share into the app.
- Transcripts produced from that audio, including titles, edits, timestamps, detected language, and search indexes.
- Tags you create or accept, including tag suggestions produced by the on-device AI model.
- App settings and preferences, including your analytics choice.
- Webhook destination credentials (optional authorization header values), which are stored in the operating system’s secure storage (iOS Keychain / Android Keystore), not in the app database.
You can delete individual recordings and transcripts inside the app at any time. Deleting the app removes your recordings, transcripts, and settings from your device.
2. On-device speech recognition and AI
- iOS: transcription uses Apple’s Speech framework in its on-device mode (SpeechTranscriber / DictationTranscriber). Audio is processed locally and is not sent to Apple by the app. Language model assets for your chosen language are downloaded and managed by the operating system (Apple’s asset service).
- Android: transcription uses Google’s ML Kit GenAI on-device speech recognition. Audio is processed locally. Speech model assets are downloaded and managed by Google Play services on your device.
- Tag suggestions: an optional on-device language model (Gemma, in LiteRT format) can suggest tags for a finished recording. Suggestions are never applied unless you accept them. The model file is downloaded once from Hugging Face’s content delivery network (huggingface.co).
Downloading these model files is a normal internet request: the service you download from (Apple, Google, or Hugging Face) sees your IP address and standard request metadata. No recordings, transcripts, or other personal content are ever included in these requests. Those services’ own privacy policies govern their handling of such requests.
3. Anonymous analytics and diagnostics (optional)
To understand which features are used and to catch crashes, the app sends a small set of anonymous events to PostHog, an analytics service, at servers hosted in the European Union (eu.i.posthog.com).
What is sent:
- Basic app lifecycle events: app opened, app backgrounded.
- A “transcription completed” event containing only metadata: the source (microphone or file), language tag, transcription engine used, audio duration, word count, number of tags, and whether audio was kept. Never the transcript text, titles, tags’ names, or audio.
- Sanitized error reports containing only the error type (e.g. “TypeError”), an internal error code, whether it was fatal, and the screen name. Raw error messages and stack traces are deliberately discarded before anything is sent, so file paths or content fragments cannot leak.
- Standard technical context attached by the analytics library: device model, operating system and version, app version, system language, and time zone.
How it is kept anonymous:
- Events are keyed to a random identifier created for your installation. It is not your name, email, phone number, or advertising ID — we have no accounts and no way to link it to you.
- IP-based location lookup is disabled. We do not derive or store your location. (Your IP address is technically visible to the receiving server during transmission, as with any internet request, but it is not used to locate you and is not stored as part of your events.)
- We never create user profiles, never use session recording or screen capture, and never track you across other apps or websites.
Your choice: analytics can be switched off at any time in the app’s settings (Analytics toggle). The choice takes effect immediately and is remembered across launches. The app works identically with analytics off.
PostHog processes this data on our behalf as a data processor. See PostHog’s privacy documentation at posthog.com/privacy.
4. Webhooks — sending transcripts where you choose (optional)
You can optionally configure webhook destinations: URLs (for example your own server, Home Assistant, Zapier, Make, or n8n) to which the app delivers finished transcripts.
- Webhook payloads include the full transcript text, title, language, tags, timestamps, and related metadata.
- Deliveries are sent directly from your device to the URL you configured. We are not in the path and never receive a copy.
- You are responsible for the destinations you configure. If you point a webhook at a third-party service, that service’s privacy terms apply to what it receives.
- Optional authorization header values you enter are stored in the iOS Keychain / Android Keystore, and are removed when you delete the destination.
- The app allows unencrypted
http://destinations for trusted local-network use and warns you when you configure one; transcripts sent to anhttp://URL are not encrypted in transit. Usehttps://destinations for anything outside your own network.
Webhooks are off unless you add a destination. You can remove destinations at any time in settings.
5. Sharing and exporting
You can share or export recordings and transcripts using your device’s standard share sheet. Anything you share goes to the app or destination you pick, under that recipient’s terms. This happens only on your explicit action.
6. What we do NOT do
- No user accounts, sign-in, or registration.
- No advertising, and no advertising SDKs.
- No sale of personal data, and no sharing of personal data for advertising or marketing.
- No tracking across other companies’ apps or websites (as defined by Apple’s App Tracking Transparency); the app never asks for tracking permission.
- No collection of your location, contacts, photos, calendar, or browsing history.
- No remote (push) server notifications — the only notifications are generated locally on your device.
7. Permissions the app requests
- Microphone — to record audio for transcription. Requested the first time you record.
- Speech recognition (iOS) — required by iOS for on-device transcription. Speech is transcribed on the device; audio never leaves it.
- Notifications (iOS, optional) — to notify you locally when a long transcription finishes in the background. You can decline; the app still works.
The app never requests location, camera, contacts, or photo library access.
8. Data retention and deletion
- Content (audio, transcripts, tags, settings): stored only on your device, retained until you delete it in the app or uninstall the app. We cannot access or delete it for you because we never have it.
- Anonymous analytics events: retained by PostHog on our behalf. Because events are anonymous and not linked to any account, we generally cannot identify which events belong to you and therefore cannot selectively delete them; turning off analytics in settings stops any further events immediately.
- Webhook deliveries: retention at your configured destination is governed by that destination, which you control.
9. Security
Your content is stored in the app’s private, OS-protected storage on your device. Webhook credentials are kept in the operating system’s secure enclave-backed keychain/keystore. Analytics traffic is sent over HTTPS (TLS). The security of webhook traffic depends on the destination URL you choose (https:// is encrypted; http:// is not). We also recommend protecting your device with a passcode, since anyone with access to your unlocked device can open the app.
10. Children
Scrivo is not directed at children under 13 (or the equivalent minimum age in your jurisdiction), and we do not knowingly collect personal information from children. Since all content stays on the device and analytics are anonymous, the app does not create profiles of any user, child or adult.
11. Your rights (EU/EEA, UK, and similar jurisdictions)
For the limited data described above, the data controller is Squaretech (contact below).
- The legal basis for anonymous usage and diagnostics analytics is our legitimate interest in understanding feature usage and fixing defects, balanced by the strictly anonymous, content-free design — and you can object at any time with the in-app toggle.
- Optional features (webhooks, sharing, model download for tag suggestions) run at your request.
- You have the rights of access, rectification, erasure, restriction, portability, and objection, and the right to lodge a complaint with your supervisory authority. Note that because analytics events are anonymous, we may be unable to link any stored event to you in order to fulfil an access or erasure request (Art. 11 GDPR); everything else lives on your device, under your direct control.
For all users, everywhere: we do not sell or “share” (in the sense of US state privacy laws) personal information.
12. Changes to this policy
If we change what the app does with data, we will update this policy, revise the effective date at the top, and — for material changes — note it in the app’s release notes before the change takes effect.
13. Contact
Questions or requests about privacy:
Squaretech
Email: info@squaretech.nl