Privacy Policy

Bodkas (bodkas.com) is an educational service operated by:

Privacy contact: [email protected]

Depending on the features you use, Bodkas may process:

• Account identifiers such as email address, display name and authentication-provider identifiers
• Session and security information needed to authenticate and protect access
• Learner-profile information such as nickname, avatar reference and account/profile relationships
• Learning progress, review history and other data needed to provide progress and recall features
• Product-access, entitlement and subscription state
• Technical logs needed for reliability, abuse prevention and security
• Information you send when contacting support

Bodkas supports email/password authentication and may offer Google or Apple sign-in when those providers are configured. Password-based accounts store a one-way password hash rather than the plaintext password. Third-party sign-in does not give Bodkas the password used with that provider.

A Family learner profile is not a separate billing account. The current learner-profile model can contain a nickname, avatar reference, access state and learning progress. A separate personal email address is not required for the learner profile itself.

Family access is account-scoped. A family code by itself is not treated as proof that a person owns or may administer a Family account.

Processing may be necessary to provide and secure the service, maintain learning progress, administer access, respond to support requests and comply with applicable legal obligations.

Bodkas uses browser storage for product state such as session context, preferences and learning state. Some learning and account data can also be synchronised with Bodkas servers when authenticated or Family features are used. Clearing browser storage may remove local state but does not necessarily delete data already stored on the server.

Bodkas may rely on third-party infrastructure or service providers for functions such as hosting, authentication, email delivery and payments when those functions are enabled.

Personal data should be kept only for as long as needed for the relevant operational, security or legal purpose. Different categories may require different retention periods.

Depending on the law that applies to you, you may have rights relating to access, correction, deletion, restriction, objection, portability, withdrawal of consent and complaints to a competent supervisory authority.

Requests can be sent to [email protected]. Identity or account ownership may need to be verified before a request is fulfilled.

Where paid checkout is enabled, payment processing may be handled by a third-party payment provider. The final provider, merchant-of-record arrangement, invoicing and tax treatment must match the provider that is actually enabled in production. Bodkas should not present or retain full card details unless a future reviewed payment architecture explicitly requires it.

For privacy questions or data-rights requests: [email protected]