Scrappy Kin Privacy Policy

Effective date: March 16, 2026
Applies to: Scrappy Kin mobile app, connected Gmail sending flows, and related support touchpoints.

This policy explains how Scrappy Kin handles personal data and Google user data for the current Gmail permission flow. It reflects Scrappy Kin's zero-trust design, Google's gmail.send permission (send email only), and Google API Services User Data Policy commitments.

1. Who we are

Scrappy Kin Inc. ("Scrappy Kin", "we", "us") is a Canadian company that builds tools letting people trigger verified opt-out requests without handing over inbox access.

2. What this policy covers

It does not cover future Gmail scopes, enterprise deployments, or non-Google integrations.

3. Data we access

Data category Source Purpose Storage / retention
Contact details you choose to provide (e.g., when you email support) Collected directly from you Support and privacy/compliance communication Used only to respond to you, maintain support records, and meet legal obligations; never used for ads
Gmail OAuth token Granted by you through Google's consent screen Allows Scrappy Kin to send opt-out emails that you initiate Stored only on your device inside the operating system's secure storage; encrypted at rest; cleared automatically if you disconnect in-app or via Google Security settings
Message drafts and recipients you type in Scrappy Kin Entered by you when you build and review a batch Used to create and send the batch of emails you review and approve Persisted on your device only, not uploaded to Scrappy Kin servers; cleared after the batch is sent
Broker-response evidence you choose to attach Optional upload from you Lets you track outcomes and document broker behavior Stored locally on your device; if you email us for help we only receive what you send
Support correspondence Emails between you and Scrappy Kin Troubleshooting and compliance follow-up Stored in our support systems as reasonably needed to respond, comply with law, and protect the service

4. Data we do not access

5. How Gmail data flows

  1. You tap Connect Gmail and Google shows the OAuth consent screen.
  2. We request only gmail.send so Scrappy Kin can deliver the batch of opt-out emails you have reviewed and chosen to send.
  3. After you approve the scope, Scrappy Kin stores the token locally on your device and uses it only when you approve and dispatch a batch.
  4. No Gmail content is copied to Scrappy Kin servers. The message goes directly from your device to Google via the Gmail API.
  5. When you revoke access in Scrappy Kin or at https://myaccount.google.com/permissions, we delete the local token and cannot send on your behalf until you reconnect.

6. Token, cache, and log handling

7. Limited Use compliance

Scrappy Kin complies with the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

8. How we share data

We only share Gmail data in these cases:

Because Scrappy Kin is designed to keep Gmail content, tokens, and opt-out data on your device, we generally do not hold the underlying personal information you are sending to brokers. If we receive a legal request, the main user-specific information we may actually have is whatever you directly sent us through support or privacy correspondence.

We do not sell personal data or license Gmail data to partners.

9. Security posture

Scrappy Kin follows a zero-trust model: assume infrastructure fails, minimize the blast radius, and keep sensitive data on the user's device whenever possible. We design the product so we do not possess Gmail content that could be compelled from us; if our servers are compromised, attackers still cannot read your Gmail.

10. Your choices

11. Children's data

Scrappy Kin is not directed to children under 13 (or the minimum age in your jurisdiction). We do not knowingly collect data from children and will delete it if we discover we have done so.

12. Changes to this policy

We will post future updates at scrappykin.com/privacy.html with a clear effective date and summarize material changes in-product. We will also update the reviewer packet shared with Google.

13. Contact us