Optional Gmail connection & Limited Use
Limited Use (affirmative statement)
The use of information received from Google Workspace APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Wording follows Google’s documented affirmative Limited Use disclosure pattern for Workspace / restricted scopes. Sources: API Services User Data Policy — Additional requirements · Workspace User Data and Developer Policy — Limited use.
Scope
If you connect Gmail, Simpy requests only https://www.googleapis.com/auth/gmail.readonly. Simpy does not request send, modify, or delete permissions for Gmail.
What happens (delivered product)
- OAuth — you grant read-only access; our servers store encrypted OAuth tokens.
- Watch / Pub/Sub — mailbox change notices can reach Simpy’s servers.
- Server processing — messages may be read transiently to detect supporting-document requests and extract structured fields (subject, piece list, short context when explicit).
- Persisted structured data — opaque ids, subject, pieces, context fields, watch/sync technical state — not a full mailbox archive.
- App — you see the dossier in Simpy.
- Local match — after vault unlock, you match or add documents on device.
- Export & reply — you export files yourself; reply text is local/editable; Simpy does not create Gmail drafts or send mail for you.
What we do not do
- Sell Gmail data or use it for advertising or credit scoring.
- Use Gmail message content to train a general AI/ML model.
- Call remote AI for Gmail document-request extraction in the current configuration.
- Claim a completed CASA / third-party security assessment letter.
Human access
Ordinary operations are designed so staff do not read your Gmail content. Human access would only be considered under Google Limited Use exceptions (security/abuse, legal obligation, or your explicit agreement for support about a specific item).
Sharing
Derived dossier fields are shown to you in the app. Infrastructure providers process operational or encrypted data under our instructions. Google processes API/Pub/Sub calls under your grant. We do not share Gmail-derived content with other users or Family unless you export or share documents yourself.
Disconnect & deletion
- Disconnect in Simpy — stops the Gmail connection (Google revoke when possible) and new processing. Dossiers already extracted stay in Simpy. A later reconnect is possible.
- Google Account — you may also remove Simpy under Google’s third-party access settings.
- Delete my Gmail data from Simpy — a separate action. It disconnects Gmail and deletes the Gmail data Simpy keeps for that connection: connection tokens, extracted requests, observed messages, and sync technical state. Your Simpy account, plan, vault, and Family space stay. No message is deleted in the Gmail mailbox. A later reconnect is possible: it starts a new cycle and does not restore Gmail data already deleted.
- Limits of that deletion — server backups outside this action may still contain the data. Work already in memory may finish once it observes the deletion. No time limit is stated. This is not absolute erasure of every copy.
- Simpy cloud account deletion — general cloud account deletion is operational (backend + web form). Processing is deferred: acceptance records a request; it is not immediate total wipe. Local vault data stays on the device. Technical copies, logs, ledger rows, or processor copies may remain under retention limits. No confirmation e-mail is promised. The Gmail data action above does not replace it. Request page: /en/account-deletion-request.html · FR: /legal/suppression-compte.html.
Other current product facts (aligned with FR policy)
- Push tokens — APNs / FCM device tokens may be stored to reach the device; some automatic Family alerts can be disarmed in the product configuration.
- Anthropic — when off-device AI is authorized: model provider under Commercial Terms / DPA · observed default retention 30 days · no ZDR ·
web_searchmay reach third-party sites · no invented “no training” promise. - Billing — no active in-app purchases today; Silver / Gold on the site are target offers / rights, not a live subscription history. Purchase history for store billing is planned only after billing is validated and enabled.
- Age — personal account minimum remains 16. Family access for under-16 remains an option under consideration — no threshold or flow change here.
Advertising on the free offer
Current state. People using Simpy today do not see ads. In the prepared iOS candidate, commercial delivery is off (ADS_DELIVERY_MODE=test, COMMERCIAL_ADS_ARMED=false) and in-app billing stays off (billingLive=false). The following describes the next version. It does not describe ads already shown to users.
Planned scope. One interstitial, and no banner, is planned only for the free offer when a session exists and rights confirm that offer. Essential, Silver, Gold, and their trials do not start an ad request. A missing session or unknown rights do not start one either.
Ad choices. The candidate asks Google User Messaging Platform (UMP) whether the AdMob choice message must be shown, then presents it when it is required. Settings include a way to review those choices when UMP says that entry point is required. canRequestAds allows an ad request. It is not, by itself, explicit consent or approval of personalized ads. Refusing in the message does not, by itself, mean that no ad can ever be served.
What Simpy sends. Simpy does not send the vault, account, document, or fact identifier, vault content, a keyword, a content URL, or a Simpy-chosen advertising identifier. The prepared request asks for non-personalized ads, turns publisher personalization off, and does not enable the publisher first-party id. Those settings do not mean that non-personalized ads collect no data.
What the SDKs may collect. The privacy manifests shipped in the candidate declare technical and advertising categories. Google Mobile Ads 13.10.0 declares a device identifier, advertising data, product interaction, diagnostics, performance data, crash data, and coarse location. UMP 3.1.0 declares coarse location, performance data, and product interaction. The app component is react-native-google-mobile-ads 17.4.0. Simpy does not promise the absence of a device identifier, an IP address, or other technical data. Coarse location may be derived from an IP address. Simpy does not request Apple’s location permission for this advertising, and the candidate does not turn off the SDK’s coarse-location collection.
Google. Google provides the ad service and the choice form. See Google’s privacy policy and the iOS SDK data disclosure. That disclosure page describes SDK practices as of version 13.12.0, which is newer than the integrated 13.10.0. Google’s advertising retention period and processing location are not taken from the AWS, Supabase, or Anthropic rules, and they are not set in this notice. The full French policy is /legal/confidentialite.html.
Still undecided (explicit)
- Numeric retention TTL for derived Gmail rows — not published.
- Legal basis wording for Gmail in the FR table — proposed, not lawyer/PO-validated.
- VAT number / share capital / D-U-N-S — not invented (D-U-N-S requested, not yet assigned).
- When to engage a Google-empanelled CASA assessor — after Google initiates / separate decision.
- Advertising: commercial delivery is not active. Google’s ad-processing location and retention, and Apple’s tracking qualification for the AdMob SDKs, remain open.