Privacy & safety · 14 October 2026

Your recovery information matters.

How Sponss handles information and the choices you have.

About this privacy policy.

This policy explains how Sponss handles your information and the choices available to you. An account is required before recovery setup. Cloud backup, AI processing and private sharing have separate permission controls. Updating this notice does not activate purchases or change tester access. Feature availability depends on your account, app version and the service configuration.

Private by default

On-device recovery data is encrypted. Cloud backup is optional and starts off.

Your choices

An account is required before recovery setup. Cloud backup, AI processing and sharing remain separate choices.

Operator · Information · AI chat · Subscriptions · Service providers · Retention · Your rights · 18+ initial release

01Who operates Sponss

Sponss is operated by Sponss Ltd, based in the United Kingdom.

For privacy questions or requests about information processed by the service, contact support@sponss.co.uk. Do not send passwords, recovery keys or sensitive journal entries by email.

Sponss is a native recovery companion, not medical treatment, a mental health service or emergency care. It is not affiliated with or endorsed by NA, AA or other fellowships.

02Information the app uses

The information you choose to save can include a name or nickname, recovery date, selected programmes, recovery preferences, journal and inventory entries, gratitude lists, routines and completion records, saved meetings, spending estimates, and trusted contacts' names and contact details.

The native app encrypts its saved recovery state on your device using AES-256-GCM. The key is kept in iOS Keychain or Android secure storage. A device-authentication lock is optional. A shared, unlocked or compromised device still creates risks.

An account is required before entering recovery details. Clerk processes account identifiers, email and any name or sign-in-provider details you supply, plus device/client identifiers and session information needed to secure sign-in. Any older guest journal remains separate; signing in does not import it automatically.

If you enable cloud backup, the app encrypts the saved recovery state before upload. This can include your profile, entries, contacts, routines and other saved app information—not just journal text. The backup service stores that encrypted payload, your account ownership identifier, a version and an update time. The native backup feature does not send your recovery key to the backup server.

Service operation can generate technical connection and security information, account activity, privacy-permission and eligibility records, and subscription records. Our application request logs record request identifiers, paths, response status and response timings, not journal bodies or authorization headers; hosting and authentication providers may also process network, device and security data.

03Why information is used

Saved information lets the app personalise your recovery space, keep your journal and routine, calculate recovery milestones and estimates, and make your selected contacts and meeting links available.

Account information supports sign-in and account ownership. Optional encrypted cloud storage lets you back up and restore your own recovery state. Support emails are used to answer the request you choose to send; technical information supports service operation and security.

Minimal usage records support AI limits, aggregate request/token/cost reporting and service reliability. RevenueCat provides subscription analytics using purchase records and account identifiers. Private journal and AI conversation content is not included in these usage or subscription analytics records.

The app does not include advertising trackers, sell recovery information or use journal content for marketing. It does not automatically send journal information to your sponsor, family, fellowship or support team.

04Sensitive information and processing conditions

Recovery dates, programme choices and journal content can reveal health or other sensitive information. Encryption is a security measure; it does not by itself remove data-protection responsibilities.

Account creation and subscription payment do not give blanket permission to process recovery information. Cloud backup, AI processing and private sharing have separate choices, described below. A technical permission record is not itself a statement of the UK GDPR lawful bases or any applicable special-category condition. Contact us if you need information about the legal basis for a particular use.

Separate backup permission: Cloud backup remains optional. A separate, unchecked choice must be saved for the signed-in account on this device before any manual or automatic upload. Signing in, an old backup switch or an imported/restored backup does not grant permission. After granting permission, choose to start backup; granting permission alone does not upload recovery information. The server rejects uploads missing the current account-bound permission receipt. This receipt records the permission choice; it is separate from your recovery key.

Declining backup permission does not block local recovery features. Withdrawing permission stops future uploads from this device and cancels pending requests where possible; an upload already delivered may remain. Existing cloud copies are not deleted by withdrawal. Other devices need their own permission choices. Reading/restoring a cloud copy and separately deleting it do not require upload permission. Restoring or importing recovery information clears this device's upload permission and pauses automatic backup.

You can withdraw optional permissions using the relevant controls. Withdrawal stops the future processing described for that feature; deletion of information already stored is a separate action.

05Optional Talk to Sponss AI chat

Talk to Sponss is an optional AI feature for approved, signed-in beta testers aged 18 and over who confirm they are in the United Kingdom. It is not a person, sponsor, clinician or emergency service. AI can make mistakes and does not provide medical advice. Urgent human-support information remains available whether chat is enabled or not.

Before sending AI messages, you must give separate processing permission in the app. Declining does not prevent use of the local journal. Signing in, accepting a TestFlight invitation or enabling cloud backup does not grant AI permission or automatically admit an account to the AI beta.

Sponss, Replit and OpenAI process your messages and relevant conversation context to create a reply. Unlike your encrypted journal, these services need to read that text; AI conversations are not end-to-end encrypted with a key only you hold. Share only what you feel comfortable sending to these services, and avoid identifying other people. Your journal, contacts and recovery profile are not uploaded automatically to AI. Text you paste or explicitly approve as memory is different.

Saving new chats and remembering approved text are separate choices, both initially off. When enabled, saved chats and approved memories are encrypted using server-held keys, tied to your account, and kept until you delete them. This is different from device-only journal encryption. When saving is off, new conversation text is not added to Sponss's saved chat history, but still passes through the AI providers. The cloud-backup inactivity-deletion plan does not automatically delete saved AI conversations.

In Talk's Privacy, History and Memory controls you can export or delete saved AI information and withdraw processing permission. Withdrawal stops future AI chat until you agree again; it does not delete existing saved chats or memories. Those deletion controls remain available while chat is disabled. Deleting AI data alone does not delete your journal, encrypted backup or account. The account-deletion action also erases saved AI chats, memories and permission records before deleting the account identity. A minimal content-free account-erasure marker remains to prevent old sessions or interrupted replies recreating deleted content. Account links are removed from AI usage/audit records while aggregate cost accounting remains. Exported or shared copies, provider-held information and infrastructure backups must be considered separately.

To operate and limit AI access, Sponss records minimal account-linked request identifiers, dates, usage/token counts, estimated cost, request status and safety flags, not chat text in usage records. Owner beta controls show settings and aggregate usage, not a chat-transcript viewer. Provider security-log and infrastructure-backup retention is separate from deletion of active Sponss records. Voice input remains off. Paid access is prepared separately from free tester access. Where paid mode applies, an eligible account also needs verified access to the plan that includes Talk. Payment does not grant admission, replace processing permission or remove daily/shared usage limits. Saved-data controls remain available when new replies are unavailable.

06Subscriptions and preserved tester access

Prepared UK monthly plans are £2.99 for the main app or £4.99 total for the main app plus Talk. A seven-day introductory trial is planned for each, subject to store configuration and individual eligibility. The store purchase sheet must show the applicable local price, trial and renewal terms before confirmation.

Eligible newcomers can choose to claim a one-time main-app allowance during their first 90 days of recovery. It excludes Talk. Sponss records the claim and its fixed expiry; later recovery-date changes do not restart or extend it. Reaching day 90 does not buy a subscription automatically. Subscriptions renew under the store terms after a purchase is confirmed; cancellation is managed in the store account.

In paid mode, Apple or Google processes the payment and RevenueCat verifies purchase history, product identifiers, subscription status and account-linked entitlements. Sponss does not receive card numbers or bank-account details through this purchase path. Our integration does not send recovery dates, journals, chat text, names or email addresses to RevenueCat.

The app checks approved UK-adult Talk eligibility and current processing permission before offering or starting a bundle purchase. A purchase does not itself authorise AI processing. Purchases or upgrades made directly in store settings cannot be vetoed by this in-app check. Main-plan access, restoration and cancellation do not require AI permission.

Existing testers retain their separately configured free-beta access. Preparing a paid-release build or updating this policy does not convert their installation into a paid build, charge them, erase their journals or grant new AI admission. This policy does not itself activate public billing.

07Service providers and other services

Replit: hosts the app services, encrypted backup database and separate protected feedback website, and routes optional AI requests. It processes stored service data and technical information needed to operate its infrastructure. See Replit's Privacy Policy and Terms of Service.

Replit's contractual scope: Replit Support has clarified that its Data Processing Agreement (DPA) applies to Pro and Enterprise subscriptions automatically when the subscription begins; no separate signature is required. Core accounts are governed by the Terms of Service and Privacy Policy and do not include that DPA. Pro is the minimum plan that includes it. This policy does not assert that Sponss has changed plans or obtained DPA coverage. The applicable agreement's scope for app-user information and international transfers must be assessed separately; a DPA is not a guarantee of UK-only processing.

Managed services and subprocessors: Talk uses Replit AI Integrations to route requests through Replit-managed credentials to OpenAI. OpenAI and Clerk appear on Replit's subprocessor list. A listing does not by itself establish which agreement covers Sponss or the retention and transfer safeguards for a particular service.

Clerk: provides required account authentication managed within the original Replit project. It processes account details, device/client and session identifiers, and sign-in/security information. It is not supplied with your plaintext recovery state by the backup feature. See Clerk's privacy information.

RevenueCat: verifies subscription access using account identifiers and purchase information, and provides subscription/customer reporting. Apple or Google handles the store payment. See RevenueCat's privacy information.

OpenAI: processes optional AI messages and conversation context to generate replies. The Sponss integration requests that generated responses are not stored by the provider's response-storage feature; this is not a guarantee of zero provider security-log retention or of processing only in the UK. See OpenAI's privacy information.

AI geography, retention and model improvement: Replit's Project geography setting does not apply to model requests. Choosing a hosting region therefore does not restrict where Talk messages are processed. Provider-specific settings are described in Replit's AI Integrations documentation; settings documented for another provider are not assurances about this OpenAI integration. Replit's use of content for model improvement is governed separately by the applicable plan, terms and settings described in its model-improvement documentation. This notice does not promise that all content is excluded from model improvement or that any particular opt-out has been enabled. It does not establish that app-user chat is used for training either. Specific retention or processing-region requirements need directly confirmed provider arrangements. Using an operator-owned API key is an available alternative for configuring a provider account directly, not the current Sponss setup or a guarantee of compliant settings.

Microsoft 365: hosts the operator's support and privacy mailbox. If you email us, your sender details, message and any attachments are handled by this email service. Email is outside the app's journal encryption. See Microsoft's privacy information.

Resend: delivers generic new-account notifications to the operator. These notifications do not include members' names, email addresses, recovery details or AI content. The internal notification outbox records an opaque event hash, creation time and sending state. Separately controlled backup-warning emails, if activated, use the verified recipient address, generic warning and opaque warning identifier, not journal content or recovery keys. See Resend's privacy information.

Sign-in providers, official reading/meeting websites, your email app, WhatsApp and SMS services process information under their own policies when you choose to use them. Opening an external site exposes connection information to that site; a location you deliberately submit may also be included.

Providers may process information outside the UK. Hosting location, AI processing location and the scope of provider agreements are distinct; the provider information above does not establish a particular international-transfer safeguard for every service. We do not claim all information stays in the UK. Contact us with questions about a particular provider or transfer.

08Permissions and deliberate sharing

Location is requested only for a chosen location lookup; the app does not continuously track you. Notifications are optional. Local reminders are handled by your device; optional private-sharing alerts pass through Expo's push service and Apple or Google. They may appear on a lock screen; choose preview settings appropriate for your circumstances. Device authentication uses the operating system; the app does not receive your biometric data.

You choose what to share and review it before another app sends it. Readable JSON, PDFs, image cards, messages, clipboard contents and files you export are outside the protection of the app's encrypted storage. Only include other people's contact details or information when you are entitled to do so.

Optional private sharing: Adults can separately turn on sharing, choose a nickname and connect using a private, single-use code that expires after 24 hours. The recipient must accept before either person can send selected content. Only the preview you confirm is uploaded as a snapshot; your whole journal is not uploaded. Sponss stores connection/account identifiers, nicknames, permission and notification settings, item timestamps and separately encrypted shared text. Shared text uses a server-held key, not end-to-end encryption: the service can decrypt it. Changes to your private original do not update a sent snapshot.

You can revoke a sent item, remove a received item, block a connection, or erase your sharing profile. Removing or blocking a connection deletes the shared copies between you from Sponss, not local originals. Erasing sharing or your full account deletes shared copies involving that account. Sharing-only withdrawal clears the nickname and keeps minimal blocked-relationship and keyed retry records to prevent evasion or recreation of deleted copies; full account erasure removes those records. Copies or screenshots already taken by recipients and notifications already delivered cannot be recalled.

Sharing notifications are off by default. If enabled, Expo and Apple or Google receive a device push token, routing identifiers and notification text. The default preview is discreet; sender nickname and entry type appear only when the recipient enables detailed previews. Entry text and personal entry titles are not sent to the push service. You can turn alerts off without stopping inbox access. Platform delivery is not guaranteed.

These public information pages add no advertising or analytics scripts, account forms or optional tracking cookies. Account sign-in and the protected feedback deployment may use authentication/access technologies; hosting providers still process connection and operational information.

09Retention and deletion

On-device recovery data remains until you use the app's deletion controls or remove the relevant device data. Exported files, sent messages, device backups and copies on other devices must be dealt with separately.

Shared snapshots remain until either participant removes the shared item, a connection is removed or blocked, or a sharing profile/account is erased. These controls remove the active Sponss copies; provider backups and already delivered notifications can have separate retention. Sharing permission can be withdrawn by erasing the sharing profile without deleting the private journal. Content-free account-retirement markers prevent stale sessions recreating deleted sharing records. Separate connection-attempt and send counters limit abuse.

The backup service holds the current encrypted vault for an account. You can request cloud-vault deletion through the signed-in app; local deletion and account deletion are separate choices. Deleting an active record does not recall information already shared or guarantee instant removal from infrastructure backups.

Planned inactive-backup deletion: After 12 months without signed-in account activity, the intended rule requires verified delivery of a warning and at least a 30-day warning period before the cloud backup is deleted. Returning to the account during that warning period will cancel scheduled deletion. This plan concerns the cloud copy only; it will not delete device-local journals. Losing the cloud copy may prevent recovery of that information after losing or replacing a phone.

Automatic inactivity-based deletion is separately controlled; this policy does not confirm that it is active. Do not rely on inactivity to erase your backup: use the cloud-deletion controls if you want to remove it. The planned rule depends on reliable activity tracking, signed warning-delivery verification without recovery details, cancellation, deletion behaviour and daily scheduled execution. It is not a legally mandated period or a current deletion guarantee.

Specific retention periods for infrastructure backups, security logs, account-provider and purchase records, AI usage/audit records, erasure markers, email-delivery records and support emails are not specified in this policy. Their retention is separate from the active-record deletion described above and can depend on provider terms, service security, accounting and legal obligations. No fixed deletion deadline or zero-retention guarantee is made for these categories. Contact us for information about a particular record or deletion request.

10Your choices and privacy rights

Sponss now requires an account before entering recovery details. Cloud backup stays optional: you can keep it off, decline optional permissions, export information and use the separate local/cloud/account deletion controls.

Creating an account is not permission for marketing, cloud uploads or AI processing. You can decline the optional features while retaining main-app access under the applicable tester, newcomer or subscription rules. Cancelling a subscription and deleting data are different actions; use the store to manage renewal and the app's separate data controls to delete records.

Where UK data-protection law applies, you may have rights to access, correct or erase information, restrict or object to processing, and receive portable information. These rights are subject to their legal conditions. Where consent is the basis, it must be possible to withdraw it.

Contact support@sponss.co.uk to make a request. Reasonable identity checks may be needed; never supply a password or recovery key as verification. You can also raise a concern with the UK Information Commissioner's Office at ico.org.uk.

11Adults-only initial release: aged 18 and over

The operator has selected an intended minimum age of 18 for the initial release, replacing the earlier 16+ plan. Younger users may be considered in a later release. It is not an Apple App Store age-rating decision, and this statement does not establish that age has been verified.

First-time 18+ self-declaration: First-time setup requires an unchecked confirmation that the user is 18 or over before the profile can be saved. The confirmation time is stored in the encrypted profile; no date of birth is requested. Support and privacy information remain accessible without confirmation. Existing saved profiles are not retroactively age-checked. This is self-declaration, not verified proof of age. This confirmation does not provide verified age assurance.

If you are under 18, do not submit personal recovery information to Sponss. Contact us about an accidental submission without including additional sensitive information.

12The protected browser feedback copy

The separate password-protected website is only a fictional-data feedback copy, not the native release. Its cloud backup is not connected. Browser storage does not provide the native app's Keychain/secure-storage protection. Do not enter real sensitive recovery information there.

The feedback website has not received the native service's account tenant, journal database or recovery keys. A shared website password is an access gate, not a substitute for journal encryption.

13Changes to this policy

We may update this policy when Sponss's features or data-handling arrangements change. Material changes will be explained in the policy and, where relevant, in the app. Publishing an update does not grant a new optional permission on your behalf.

The full policy is available here without signing in. The in-app summary is included with your installed app version, so an older installation may show earlier wording. Contact support@sponss.co.uk if you have questions about a change or your privacy choices.