Privacy
Your study data is yours.
This policy explains what Smort processes, why it is needed, and what happens when you delete your Smort account.
Last updated: August 22, 2026
What Smort collects
Smort may process account identifiers and the sign-in information you choose to use, such as an email address, phone number, or Apple or Google account identifier. Smort does not receive your Apple ID password or payment card details. A permanent Smort account is required after your first card and review. Signing in does not enable Cloud Sync.
Your decks, items, answers, review history, settings, and related study content are stored on your device. If you enable Cloud Sync, the content you choose to sync is also stored in our Supabase cloud service so it can be restored and kept consistent across your devices.
If you join the launch waitlist, Smort stores the email address you provide only to send one launch notification. It is not added to a marketing newsletter or linked to a Smort account. We keep it until that notification is sent or you ask us to delete it.
AI processing
Smort AI sends the text needed to create material or grade an answer, and the one image you choose when you import a screenshot, through Smort's authenticated cloud gateway to OpenRouter and the selected model provider. For your first card and review, Smort uses a temporary anonymous authentication credential so you can experience the product before creating an account. Smort records limited operational data such as a pseudonymous account value, request type, status, latency, token counts, estimated cost, and safe error code. We do not put prompts, answers, account contact details, access tokens, or provider keys in our application logs.
Screenshot import is a Plus and Pro feature. Before an image leaves your device, Smort asks for a separate image permission in addition to the Smort AI permission. You can withdraw either permission in Settings, and withdrawing the Smort AI permission also withdraws the image permission. Before the upload, Smort removes location data and other metadata, such as EXIF, GPS, timestamps, and filenames, from the image on your device, and scales large images down.
Smort does not keep the image. It is not stored on Smort's servers, is not written to our logs, and Smort does not hold it after the request completes. If the connection drops, the prepared image stays only in your device's memory so you can retry; it is released when the import succeeds and when you cancel, pick another image, withdraw the permission, or leave the app. Smort denies provider data collection and uses zero-data-retention routing for the request. For an image request, Smort records the same operational data plus the image size and dimensions as ranges. It never records the picture, the filename, or location. To make retries safe, Smort keeps the generated candidate cards in a short-lived server cache; a scheduled cleanup deletes them automatically, usually within about twenty minutes. The cards you review and choose to keep are stored like the other cards you create.
If the optional personal OpenRouter-key feature is available and you choose to use it, the key is stored on your device and sent only for the request you initiate. It is not stored in Smort's database.
Temporary first-review authentication and associated AI result and accounting records are deleted after 35 days, except while a request is still being reconciled. They are not linked or merged into the permanent account you may create afterward.
Speech and audio
When you grant microphone permission and use Learn dictation or spoken Practice answers, Smort streams live microphone audio and, during Practice, relevant card terms directly to Soniox using a short-lived, single-use credential issued by our authenticated cloud gateway. Soniox processes that content to return partial and final transcripts under its own terms and data-processing policies. Smort does not store the microphone recording.
If you enable Studio Voice, the text Smort needs to speak is sent through our authenticated cloud gateway to ElevenLabs. ElevenLabs generates the Alice voice for English and Mandarin Chinese. Smort asks ElevenLabs not to log each synthesis request where our provider account supports that setting, but ElevenLabs processes data under its own terms and the retention settings available for our account.
Smort stores completed Studio Voice audio in a private, account-scoped Supabase cache so the same text does not need to be generated again. An evictable copy is also kept in the app's cache on your device for instant replay. The app falls back to Apple voice when Studio Voice is unavailable, your plan does not include it, or your monthly allowance is used.
Community Decks
Private Decks remain on your device and, only when you enable Cloud Sync, in account-scoped Cloud storage. If you confirm a public publication, Smort stores a separate Community copy containing the displayed Deck title, description, category, item fields, and supported item metadata. The generation prompt is not included as a separate Community field, although generated text can contain information supplied in that prompt. Public Decks are associated with an internal publisher account identifier; your email address or phone number is not displayed in the catalog.
Before publication, the public copy is sent through our authenticated moderation gateway and an AI model used for safety classification. We retain limited event data such as a pseudonymous actor, Deck and version identifiers, outcome, and timestamps. If a member reports a Deck, we retain an immutable snapshot of the reported version, report category, optional report detail, and reporter and publisher identifiers so we can investigate even if the live Deck changes. We do not put Deck text in application logs.
Making a Deck private purges the live Community package and catalog text. Moderation, abuse-prevention, security, and report evidence may be retained for as long as needed to resolve reports, prevent repeat abuse, meet legal obligations, and protect users. Smort cannot delete copies another member downloaded before a Deck became private.
Subscriptions and usage
Apple processes purchases and billing. Smort receives signed transaction information, product and subscription status, renewal state, expiration dates, and an account-binding token so we can verify your plan and restore it to the correct Smort account. Smort records monthly AI usage and short-lived reservations to enforce the allowance shown in the app.
Product analytics
Smort sends selected product-usage events to PostHog so we can understand whether onboarding and practice are working. These events describe actions and categories such as an onboarding step, practice mode, result, hint use, item state, counts, response time, and app or device context. They do not include Deck or card text, prompts, answers, transcripts, feedback, names, email addresses, or phone numbers. Session replay, automatic screen and control capture, and IP-based location enrichment are disabled.
Before you sign in, PostHog assigns the app installation a random identifier. When you sign in, Smort associates that installation's earlier events with your internal Smort account identifier so we can measure the onboarding journey. We do not send PostHog your account contact details. Smort resets the device analytics identity when you sign out or switch accounts. We use this data to improve Smort, not for advertising or tracking you across other companies' apps or websites.
Optional performance diagnostics
Apple may deliver MetricKit reports to the app containing crash call stacks, hang, launch, CPU, disk-write, memory, and aggregated performance information. These reports do not include your decks, items, answers, or transcripts. Smort keeps the reports on your device by default. Signpost fields are removed before a report is stored.
If you explicitly enable Share Performance Diagnostics while signed in, future reports are sent to Smort's authenticated, account-scoped Supabase service for reliability analysis. They are linked to your Smort account, are not used for tracking or advertising, and are retained for up to 30 days. Turning sharing off stops future reports from being queued. Clear Performance Diagnostics removes local reports and requests deletion of reports stored for the signed-in account.
Service providers
Smort relies on Apple for app distribution, purchases, speech, and optional Apple sign-in; Supabase for authentication, database, and server functions; OpenRouter and model providers for requested AI operations; ElevenLabs for Studio Voice synthesis only when you enable it; PostHog for privacy-limited product analytics; Google only if you choose Google sign-in; and email or SMS delivery providers only if those sign-in methods are enabled. Providers process data under their own terms and privacy policies.
Retention and deletion
You can delete your Smort account from the app. Account-owned cloud learning data, synced study data, Studio Voice cloud audio, performance diagnostics, consent records, and AI usage metadata are deleted with the account, except information we must retain for security, fraud prevention, legal obligations, or transaction integrity. For App Store purchases, Smort retains a minimal, account-detached transaction record so the same purchase cannot be claimed by multiple accounts. Account deletion also unlists and purges live Community Deck packages owned by that account, subject to the report, safety, and legal retention described above. Signing out or deleting the Smort account clears that account's Studio Voice device cache. Learning stored on your device remains after you sign out or delete the Smort account, until you reset app data in Smort or remove the app.
Deleting a Smort account resets analytics identity on the device but does not automatically erase historical PostHog events. You can ask us at the address below to delete analytics associated with your internal Smort account identifier. Anonymous events that were never associated with an account may not be identifiable as yours.
Deleting a Smort account does not cancel an Apple subscription. Cancel or manage it in the app's Plan & Usage screen or in your App Store subscription settings.
Security and choices
Smort uses authenticated, account-scoped APIs, encrypted network transport, restricted server credentials, and server-side authorization. No system can guarantee absolute security. Smort AI is part of the product and requires an internet connection. You can experience the first card and review before providing a permanent account identity, deny microphone or speech access, sign out of your Smort account, or delete your Smort account.
Children, changes, and contact
Smort is not directed to children under 13. We may update this policy as the product changes and will revise the date above. Questions or privacy requests can be sent to support@getsmort.app.