── DAYCHIEF DATA MANAGEMENT
Data Management and Account Deletion
Pre-release Status
DayChief is not yet generally available. Its comprehensive account-deletion workflow is an approved production control that is still being implemented and verified. Current test builds should not be treated as proof that every related top-level application record or external processor record has been removed. This page will be updated when the complete workflow has been released and verified.
Disconnect a Service
Open DayChief Settings, choose the connected provider, and select Disconnect. For Google, DayChief deletes the stored OAuth token and cached connector metadata and attempts provider-side revocation. You can also revoke DayChief from your Google Account permissions. Disconnecting does not remove an email draft, sent message, calendar event, or other data already written to the provider, and it does not remove provider content already included in a DayChief conversation or approval record.
Delete a DayChief Account
Use Delete Account in DayChief Settings and complete any requested recent sign-in confirmation. The approved production workflow will promptly delete identifying account data, stored connector credentials and metadata, conversations, prompts, transcripts, assistant responses, approval and tool records, Google Workspace content or derived excerpts, voice-session records, local tasks, and notification links. It will request applicable provider deletion or revocation, then delete the Firebase authentication identity after required cleanup steps succeed.
Deletion does not remove content already written to an external account, such as a Gmail draft or Google Calendar event. Delete those items in the provider's own service if desired.
What May Remain
- Broad de-identified totals: Minimum non-Workspace billing and service-usage information may be irreversibly de-identified and combined into broad monthly company-wide totals for financial reporting, capacity planning, and service-integrity purposes. These totals may remain for no longer than three years from the underlying transaction or usage period. They exclude Google Workspace content and derived data, prompts, transcripts, free text, user or provider identifiers, precise timestamps, and small or distinctive cohorts.
- Subscription-event suppression marker: A keyed cryptographic marker may remain solely to prevent a delayed RevenueCat subscription event from recreating the deleted account. It is restricted pseudonymous security data, not an analytics profile, and contains no raw user ID, email, receipt, product, transaction, prompt, or Google Workspace content. It expires three years after the most recent verified matching RevenueCat lifecycle event. A later verified matching event restarts that period only so the marker can continue to suppress recreation.
- Backups: Protected Firestore point-in-time recovery and scheduled backup copies may age out for up to seven days. They are not available through the ordinary app. Restore procedures must reapply deleted-account suppression before restored data is exposed.
- External providers: Provider-side deletion or revocation requests may complete asynchronously under the provider's process and retention rules.
Apple Subscription
Deleting a DayChief account does not cancel an Apple subscription or stop Apple billing. If you no longer want the subscription, cancel it separately through Apple's subscription-management controls. An eligible purchase may be restorable if you later create a new DayChief account, subject to Apple's and RevenueCat's restore rules.
Need Help?
For privacy questions, access requests, or deletion help, email FXA Digital Solutions LLC at [email protected]. Do not email passwords, OAuth tokens, message contents, file contents, or other sensitive account data. Include only the minimum information needed to identify the request.