Last updated 2026-10-15
Privacy Policy
This policy covers papersync.ai, the Papersync mobile app and the Papersync plugin for Obsidian. Papersync has no server: your scans, notes, transcriptions and AI API keys never reach us. Everything we do collect is listed below.
Who is responsible for your data
Papersync is run by its independent developer ("we"), who is the controller responsible for the personal data described in this policy. For privacy questions or requests, email [email protected]. For product support, email [email protected].
Google user data
This section covers the Papersync mobile app (Android and iOS) and the Papersync plugin for Obsidian, which use the same Google sign-in. Signing in with Google is optional. You only do it if you choose Google Drive as the place where Papersync stores your notes. Papersync has no server: Google user data goes only between your device and Google, and is never sent to us.
| Google user data | Permission | What Papersync does with it |
|---|---|---|
| Your email address, name and profile photo | openid, email, profile | Shown in the app's Settings so you can see which Google account your notes are saved to. Nothing else. |
| Google Drive files that Papersync itself created | drive.file | Create a Papersync folder and save each transcribed note and its page photo into it; list, open and delete those files for the app's scan History; let the Obsidian plugin copy them into your vault. Papersync cannot see or change any other file in your Drive. |
How Papersync accesses and uses Google user data
Papersync accesses only the data in the table above and uses it only to provide the features described there: saving your notes to your own Google Drive, showing them back to you, and syncing them to your Obsidian vault.
Sharing and transfer
Papersync does not share, sell, transfer or disclose Google user data to anyone. Because Papersync has no server, the data never reaches us, and no person at Papersync can read it. Google user data is only used to provide the user-facing features above. It is never used for targeted, personalized, retargeted or interest-based advertising, never sold or given to data brokers or information resellers, never used to determine credit-worthiness or for lending, and never used to create databases. The photo of a page you scan is sent to the AI provider you chose so it can be transcribed; that photo comes from your camera, not from your Google account, and no Google user data is included.
AI and machine learning
Papersync does not use Google Workspace APIs (such as the Google Drive API) to develop, improve, or train generalized or non-personalized AI and/or ML models. Papersync does not use Google user data to train any AI or ML model, and does not transfer Google user data to any third party for that purpose.
Storage and protection
Your Google sign-in session is held by Google's own sign-in software in your device's protected app storage (on the computer, the plugin keeps its Drive token in your operating system's keychain). Neither is ever copied to a server. Every request between Papersync and Google is encrypted with HTTPS (TLS). Your notes stay in your own Google Drive.
Retention and deletion
Papersync keeps no copy of your Google user data on any server, so there is nothing for us to retain. The sign-in session stays on your device only while you use Google Drive with Papersync: signing out in Papersync's Settings, or uninstalling the app, deletes it from the device immediately. You can revoke Papersync's access at any time at myaccount.google.com/permissions. The files Papersync wrote to your Drive belong to you: delete them in Google Drive whenever you like. For any question or deletion request, email [email protected].
Limited Use. Papersync's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Your scans, notes and API keys
The first time you save an AI provider, the app explains that each page you scan is sent to that provider and asks you to agree. After that, each page (with the transcription instructions, plus your own instructions if you added any) goes directly from your device to the AI provider you chose, using your own API key. We do not see, log or relay this traffic. The provider's own privacy policy applies, and it may keep your pages under its terms, so review it before scanning sensitive material. To stop sending pages, remove your providers. Provider policies: Anthropic (Claude), OpenAI (ChatGPT), Google (Gemini), OpenRouter, xAI (Grok), Mistral, Groq, Hugging Face, Alibaba (Qwen), Together AI, Z.ai, Moonshot AI (Kimi), MiniMax, Meta, Xiaomi (MiMo), StepFun, BytePlus (ModelArk).
OpenRouter and Hugging Face are routers: they forward your page to the model host you pick, so that host's policy applies too. Meta, Xiaomi, StepFun and BytePlus are set up as custom endpoints, and a custom endpoint sends pages to the address you enter, including a server on your own network.
Your API keys stay in your device's secure storage (iOS Keychain, Android Keystore) and leave it only as the sign-in header of requests to the provider you chose. Your notes and page photos are saved to the storage you picked (a folder on your phone, iCloud Drive or Google Drive), never to us. App settings stay in the app's private storage.
What we collect
| Data | When | Who processes it, and why |
|---|---|---|
| Your email and the tool you picked | Only if you subscribe on papersync.ai | Kit (our email service), to send product updates. Based on your consent; every email has a one-click unsubscribe. |
| Page-view counts | When you visit papersync.ai | Cloudflare Web Analytics: cookieless, aggregate counts only, no profile and no cross-site tracking. |
| Usage events | Only if you turn on Share anonymous usage stats | PostHog (EU), to learn which features help. Based on your consent. |
| Crash reports | Always | PostHog (EU), to find and fix crashes. Based on our legitimate interest in a working app; you can object (see Your rights). |
| Supporter purchase status | Only if you open, buy or restore Supporter | Google Play (payment) and RevenueCat, to deliver and restore the purchase. Necessary to perform the purchase. |
| Update checks | When the app starts | Expo, to deliver app updates. |
Usage stats and crash reports
Usage events (only while usage stats are on): app opened, backgrounded, installed or updated; the names of the screens you open, never their contents; a few feature actions such as "settings opened"; and the app's own error events. They carry a random device ID that is created only when you turn usage stats on. Turning them off stops all future usage events.
Crash reports (always): the error message and stack trace. The app redacts anything that looks like a credential before sending and drops a report it cannot clean. Crashes in the native layer are reported directly by PostHog's own SDK, without that redaction; their messages are written by the operating system or a library and can name a file path. Crash reports use a separate channel and a temporary ID that changes every time the app starts, so they cannot be tied to your usage stats. On iOS, a native crash is reported on the next launch and can carry the previous launch's ID, and it lists the app's loaded code files with an install-folder name that stays the same until you reinstall. With usage stats off, the only requests the app makes to PostHog are this channel's settings downloads (no ID), the crash reports themselves, and a flag request carrying the temporary ID only if we ever switch on a feature flag, which the app does not use.
Both carry device details: app version, operating system, device model and maker, screen size, whether it is an emulator, language, region, time zone and a session ID; native crash reports also note Wi-Fi or mobile data and, on Android, the carrier and user agent. Neither ever contains your notes, photos, prompts, API keys, name, email, advertising ID or location. PostHog does not store your IP address and location lookup is off (events from before 2026-07-18 may carry an approximate location until they expire). There is no session replay, tap autocapture, heatmap or survey.
PostHog keeps this data for one year, then deletes it. Our project is hosted in the EU (Frankfurt); under PostHog's data processing agreement, PostHog and its subprocessors may also process it in the United States under the EU-US Data Privacy Framework and the EU Standard Contractual Clauses (with the UK addendum), and requests can pass through Cloudflare's network. We may also view crash reports from outside the EU, in a country without an EU adequacy decision, only to fix bugs. See posthog.com/privacy.
Supporter purchases
The app is free. The optional one-time Supporter purchase is paid through Google Play (or the App Store); we never receive your card, name, email or billing address. To check and restore it, the app uses RevenueCat under a random ID that RevenueCat creates on your device and that we do not link to your Google account or usage-stats ID. RevenueCat receives that ID, the store's purchase record (product, price, currency, date and purchase token), basic app and device details (app and OS version, language, store country) and, like any server, your IP address. The app contacts RevenueCat only when you open Settings, the Instructions screen or the retry sheet, or buy or restore, never at app start, and never sends your notes, photos, instructions or keys. RevenueCat processes this data in the United States as our processor; for EU, UK and Swiss users the transfer is covered by the EU Standard Contractual Clauses (with the UK addendum and Swiss amendments). See revenuecat.com/privacy.
App updates and connectivity
At launch the app asks Expo's update service (u.expo.dev)
for updates, sending the app and runtime version, the platform and a
per-install update ID, none of your content. To check connectivity it
may request papersync.ai/generate_204, which returns
nothing and stores nothing. At launch, and at most every few hours
while it is open, it also reads papersync.ai/app-config.json,
a small public file that tells very old app versions to update; that
request carries no identifier and none of your content.
Permissions
Camera: to photograph the page you scan. Frames stay on the device until you capture; only the captured photo leaves it, to your AI provider and to your storage. Storage (Android 12 and older only): for the older file-access path; newer Android uses the system folder picker instead. Both can be revoked in your system settings.
Security
Every request from the app and plugin uses TLS (HTTPS). The one exception is a self-hosted model on your own local network, which may use plain HTTP and never leaves your network. papersync.ai is served over HTTPS by Cloudflare Pages. The only server code we run is papersync.ai's subscribe form, which passes your email to Kit and stores nothing itself.
Children
Papersync is not directed to children under 13 (under 16 where local law requires, such as in the EEA). If you believe a child has given us personal data, email [email protected] and we will delete it.
Your rights
Outside your own device we hold very little: your email if you subscribed, pseudonymous PostHog data and, if you opened or bought Supporter, the pseudonymous RevenueCat purchase record. In the EU, UK and Switzerland (GDPR) you can access, correct, delete, restrict, port or object to processing of your data, and complain to your local data protection authority. In California (CCPA/CPRA) you can know, delete and correct your data; we do not sell or share personal information.
To use any of these rights, including objecting to crash reports, email [email protected] or [email protected]; no account or special wording is needed, and please don't send your notes or keys. We reply within one month. Because crash reports carry only a temporary ID, we can find yours only if you tell us roughly when the app crashed and on which device; reports we can match are deleted, the rest expire after one year. The app cannot yet stop crash reports for a single install, so if an objection is upheld before it can, our reply will explain your options.
To have your RevenueCat purchase record deleted, email us the Google Play order number (it starts with GPA.) or the App Store order ID from your receipt, so we can find it without knowing who you are. Deleting it does not refund or cancel the purchase; Restore Purchase recreates it later if you ask the app to.
There is no Papersync account to delete. Uninstalling the app removes your API keys, settings and consent record from the device. Your notes stay in your own storage until you delete them there. To leave the email list, use the unsubscribe link in any email.
Cookies
papersync.ai sets no cookies, and the app and plugin do not use cookies.
Changes and contact
If this policy changes materially, we will update the date at the top and tell email subscribers. Questions go to [email protected].