Used for login, course access, profile support, and account-level requests.
Legal
Privacy policy
How ExaMold may collect, use, store, and protect personal and learning-related information.
This policy should be reviewed against your final product, legal, and compliance requirements before production use.
Privacy overview
The policy focuses on data needed to operate the learning service.
ExaMold should keep public privacy information aligned with the fields used by the app, landing APIs, backend support tools, billing flows, and course activity.
Used to preserve study state, saved material, revision, and practice history.
Used to route contact messages, ticket details, and issue follow-up.
Used to protect accounts, sessions, payments, and service reliability.
Use only relevant landing dataPublic landing APIs should return only the fields needed to display courses, FAQs, pricing, insights, and contact responses.
Separate public and admin accessAdministrative metadata, internal notes, audit fields, and sensitive records should stay behind protected backend access.
Keep learning context usefulProgress, saved notes, and practice activity should help learners continue without exposing unnecessary account detail.
Explain material changesWhen data use changes meaningfully, the privacy page and relevant app notices should be updated together.
Information we collect
ExaMold may collect account registration information, contact details, subscription records, device metadata, support communications, and learner activity needed to provide and improve the service.
How we use information
We use collected information to authenticate accounts, deliver learning content, maintain subscriptions, respond to support requests, improve product experience, and keep the service secure.
Content and learning activity
When learners save notes, access chapters, attempt tests, or manage profile preferences, ExaMold may process that activity to personalize access, preserve progress, and improve relevance.
Payments and subscriptions
Billing information may be processed through trusted payment partners. ExaMold stores only the information necessary for membership management, invoice history, and support resolution.
Website inquiries
When someone uses the public contact form, ExaMold records the supplied name, email, optional mobile number, inquiry category, subject, and message so staff can route and respond to the request.
Service providers
ExaMold may use carefully selected providers for hosting, email delivery, authentication, analytics, payments, and operational support. Providers should receive only the information required to perform their service.
Cookies and local storage
The website and apps may use cookies or local device storage for security, preferences, sessions, and reliable product operation. Browser and device controls can be used to manage supported storage choices.
Security and retention
We apply reasonable safeguards to protect user information and retain data only as long as needed for service delivery, compliance, dispute handling, or legitimate business needs.
User choices
Users may request profile updates, password resets, support corrections, or account-related assistance through official ExaMold contact channels.
Contact about privacy
Questions about this policy, personal information, or data requests can be sent through the official ExaMold contact page. Identity verification may be required before completing account-level requests.
Request flow
Privacy questions should move through a clear support process.
Submit the request
Use official contact channels and include the account email or course context needed to identify the issue.
Verify the account
Account-level privacy requests may require identity checks before any data is changed or disclosed.
Review the affected records
The support or admin team can inspect the relevant account, contact, billing, or learning records.
Respond with the outcome
The response should explain what was updated, what could not be changed, and any next step.
Account access
Users should keep credentials private and use password reset flows when account access is uncertain.
Device storage
Cached content, preferences, and local app data may be controlled through supported device or app settings.
Communication details
Email and optional mobile contact details should be kept current so support can respond correctly.
Policy updates
Privacy information should evolve with the product.
Material changes should be reflected on this page and, where appropriate, communicated through the app or account contact details.