In short. Capture and Think stay on this device. Cloud AI runs only when you tap Fix text (글 바로잡기), and then we send that note text — not your whole library. Optional My GitHub upload sends Markdown to your repository.
1. Who we are · contact
Serendipity (“the app”, “we”). Questions or account deletion: lism60987@gmail.com
2. What stays on your device
By default the following stay local (e.g. on-device SQLite):
- Notes, topics, thoughts, and (if present) the link graph
- Photo attachment paths; text after speech-to-text
- Settings, theme, language
- GitHub repo name and write token (PAT) in on-device secure storage — not sent to our servers
Capture and Think work without signing in. Your local notes do not require an account.
3. Cloud AI — Fix text (this build)
In this store build, the cloud generative AI you can run is Fix text (글 바로잡기): optional cleanup after dictation or OCR. Nothing is sent until you tap it.
- When: you explicitly run Fix text
- What: the note text you asked to fix — not photo originals or a bulk library upload
- Why: app functionality — to produce the correction you requested
- Path: device → our proxy (Cloudflare Workers) → an LLM provider (currently DashScope / Qwen). Providers may change; we will update this policy when they do
- Limit: a free daily cap. Google sign-in is required to carry that cap across reinstalls
- Logging: the proxy is designed not to retain message bodies. Technical metadata for quotas and reliability may be stored
If you never run Fix text, this transmission does not happen. Typing notes still works offline.
4. Jump (hidden in this build)
Jump (reading-order suggestions) remains in the codebase but is off the screens in this store build. If a later update turns Jump on, running it will send a small cited card packet over the same proxy path. We will update this policy and Play Data Safety in that same release.
5. Account · limits
Cloud AI daily/monthly limits need Google sign-in (Supabase Auth) so they survive reinstalls. Capture and Think still work without an account. Sign-in does not upload your note library.
- Examples: email, account id, auth tokens, free-use counts on the server
- Purposes: account management, AI caps, abuse prevention (e.g. request IP)
- This version has no in-app purchases or subscriptions
- Account deletion: in-app “Request account deletion” or lism60987@gmail.com. Local notes must be deleted on-device by you
6. My GitHub (optional)
If you save a repo and token in Settings, tapping “Upload now” sends Markdown to your GitHub repository. It does not pass through our servers. The token stays on the device. GitHub’s policies apply to what you put there.
7. Device permissions
- Camera: take a photo for a note
- Photos: pick attachments. On Android we prefer the system photo picker (no broad gallery access)
- Microphone · speech recognition: dictation. Platform speech services may process audio
You can deny permissions and still type notes. Photo binaries are not part of the default cloud-AI request.
8. Product improvement
We do not collect memo or thought bodies for analytics or model training.
- Optional crash reporting when configured: stack and short message only; no memo bodies
- Broader product-event telemetry remains default OFF until an opt-in ships with a policy update
- Not for: ads, sale of notes, or publishing your notes as open training data
9. Third parties · service providers
- Cloudflare — AI proxy and hosting for this page
- LLM provider — Fix text generation (currently DashScope / Qwen)
- Supabase — optional authentication
- Google — optional OAuth sign-in
- GitHub — only if you connect it; Markdown upload to your repo
- On-device embedding model CDN — model file download, not note upload
These process data to run the product and infrastructure. We do not sell your notes for advertising profiles.
10. Retention · deletion
- Local data: uninstall, device reset, or in-app delete / export
- AI requests: processed to fulfill the tap; we do not mirror your full library on our servers
- Account: in-app request or lism60987@gmail.com
11. International transfer · security
Cloud services may process data outside your country. We use HTTPS and similar industry practices in transit. No method is perfectly secure.
12. Children
The app is not directed at children. We do not knowingly collect personal information from children.
13. Changes
When practices change, we update the date and version on this page. Material changes may also be noted in the app or store listing. Turning Jump back on, or adding Play billing, will ship with a policy and Data Safety update in the same release.
14. Contact
Privacy questions and deletion requests: lism60987@gmail.com