Local study and native purchases and restores do not require a StudyCert account. Account linking is optional for supported web access and study-record merging. The app does not include advertising. Detailed question progress, wrong answers, review notes, glossary recall, reminders, and theme settings are stored on the device.
For purchase and restore functions, and when aggregate study-metrics sharing is enabled, Apple and RevenueCat may process purchase status, an app user identifier, total active study time, total questions answered, total correct answers, and the last study activity time. These values are not used for advertising or cross-app tracking, and individual question text or answer selections are not transmitted as study metrics.
In versions that support StudyCert web linking, local study and platform-store purchases and restores do not require a StudyCert account. Linking is optional for supported web access and study-record merging. When you choose to link, the service processes your email address or Apple relay address, display name, login method, email-verification status, provider and StudyCert account identifiers, and connection or refresh information. Firebase Authentication and the selected Google or Apple sign-in service handle authentication; provider passwords and full payment-card details are not received or stored by StudyCert. Linked-account refresh information uses protected device storage.
Learning records are kept separately for each app and account. Linking merges supported question and glossary completion, wrong-answer and review flags, learning activity, and edited glossary text, including the term, explanation and study cues, with that account's server records. Records created before linking are imported only after you confirm import. This does not promise cloud backup of every device setting or mock-exam resume record. Unlinking does not erase that account's local records, and another account cannot open those records.
To distinguish devices writing learning records and authorize their requests, the app uses a random installation identifier and a protected device verification value. The server stores the account/app-linked identifier and a hash of the verification value, rather than the original value. Request-token validity is separate from the retention of these server records. Related server account records are removed when verified account deletion completes.
The platform store and RevenueCat process purchase/customer, product and transaction identifiers, purchase or refund status and entitlement information for access, restore, purchase management and purchase analytics. Connecting a verified native purchase to web access associates it with the first linked StudyCert account; another account cannot reuse the same purchase. Access on another platform depends on verified purchases and confirmed support for that platform.
When study-metrics sharing is enabled in a configured native app, total active study time, numbers of answered and correctly answered questions, last study time and the app identifier are associated with the RevenueCat customer identifier for learning-usage management and analytics. Individual answer selections and question or glossary text are not sent in these aggregate attributes. This limitation does not exclude edited glossary text from the separate linked-learning records described above. These features are not used for advertising profiles or cross-app ad tracking.
If Google supplies a profile image, its URL is used in the web login session and the browser requests that image address directly. The StudyCert account-profile database does not store the image URL or image file. The sign-in and image providers process their services under their own policies.
If you use StudyCert web support, the service processes your message, account or reply email, related page and submission time to handle your request and reply. Messages are stored in the Google inquiry channel and forwarded to the developer's Gmail. Browser conversation history is available for 30 days after the last message and then cleared progressively; Google-channel and Gmail records are managed separately, and you can request deletion through the contact channel on this page. This describes web support, not a native in-app feedback form. Do not send passwords or full card details.
Error and performance diagnostics and transformed IP-address values used for request-rate limits are processed for service operations and security. They are separate from aggregate visitor-count buckets. Server cleanup runs during request processing, so cleanup cutoff dates do not guarantee the actual deletion time. External operational logs and notification services follow their own retention policies.
Use supported learning-record controls to reset records, or the web account controls to request verified account deletion. Deleting a web account removes its related server records and web-billing RevenueCat customer information; it does not delete the separate native RevenueCat customer or that customer's study attributes, device learning records or native purchase entitlement. Native RevenueCat and store records are handled separately under their providers' policies. Unlinking an account and resetting study progress are separate actions, and neither is a promise to erase every historical storage entry.
For privacy questions, contact storkan2@gmail.com.
Effective: October 7, 2026