← Back to home
How Scrappy Kin handles your data
Scrappy Kin is designed to ask for as little of your data as possible. As much as possible, your information stays on your device or in your own email account. The full Gmail send-only commitments live in the Privacy Policy.
In practice this means:
- your personal profile stays on your device
- you send requests yourself from your own account
- billing goes through the App Store, so we do not need your billing details
- Gmail data does not touch Scrappy Kin servers; see the Gmail data section for full details
Scrappy Kin does not:
- read your inbox
- send data to us in the background
- run analytics or telemetry inside the app
- keep server-side copies of the personal data you are trying to remove
The Scrappy Kin codebase is public on GitHub, so you do not have to take our word for it. If something breaks, you can email us directly and read the full error report yourself. If you disconnect Gmail inside Scrappy Kin or via Google account settings, the token stored on your device is deleted immediately.
Gmail tokens stay on your device
When you connect Gmail, Google issues a token that lets Scrappy Kin send on your behalf. That token:
- is stored in your device's operating system secure storage (Keychain on iOS/macOS, Keystore on Android)
- is never synced to Scrappy Kin servers — we cannot act on your behalf without the copy on your device
- stays on a direct device-to-Google path: opt-out emails go from your device to Google via the Gmail API, not through our infrastructure
- is deleted immediately when you revoke access in-app or at Google account settings
Diagnostics are optional and local
Scrappy Kin does not collect background usage data. Specifically:
- no analytics SDKs, no third-party tracking tools, no automatic crash-reporting services are included in the app
- optional local diagnostics are off by default; you can turn them on in settings if you need to troubleshoot
- when enabled, diagnostic logs stay on your device and are only ever shared if you manually export and email them to us
- diagnostic logs record app state only — they are not a background pipeline and are not used to capture Gmail content