Privacy policy

1. Who is responsible and what this policy covers

The operator identified above is the controller for personal information processed to operate the World of Apostles website, accounts and game. This policy describes the current service, including registration, saved progress, support, security, optional email updates and optional website analytics. It does not make an external social platform or payment provider part of our service.

Use the published contact above for privacy questions and rights requests. The operator’s full legal identity, postal address, working contact and the operational details shown below must be completed before public launch. Where a data protection officer or local representative is legally required, the operator must also publish their applicable contact details. We do not invent these details or assume a provider or processing location from the software framework.

2. Account information and sources

You provide your account name, email address, password and optional communication choices. We store a password hash rather than a recoverable account password, account identifiers, creation and update timestamps, email-verification status, authentication and password-reset tokens where needed, and the latest time and version of terms acceptance and privacy acknowledgement. We store the time of your declaration that you are at least 18; we do not ask for a full date of birth or an identity document in the current signup form.

Names may be nicknames. Account details are not a public player directory in the current implementation. We receive information directly from you, from your interactions with the game and automatically from requests made by your browser. The currently disabled Google and Facebook buttons do not obtain a social profile or social-login token.

3. Saved gameplay and fictional character records

The server stores the character linked to your account, including appearance choices, location and position, travel, level, skills, talents, inventory, equipment, virtual currency, quests, achievements, interactions, in-game property and other state needed for continuity. Combat, hunting, injuries, pursuit and fictional wrongdoing or restitution can also produce saved gameplay records and timestamps.

These records describe a fictional character. In-game crime or standing is not a real criminal record; biblical story progress is not proof of your religion. We do not use these game statistics to decide your creditworthiness, employment, insurance or real-world legal status. Game rules automatically determine fictional outcomes, but the current service does not use that scoring to make decisions with legal or similarly significant effects on you.

4. Technical, security and support information

Serving requests can involve your IP address, browser or user-agent information, requested route, request time, session identifiers and diagnostic or error details. Database-backed sessions can contain an account identifier, IP address, user agent and session payload. Hosting, proxy and email infrastructure may maintain their own operational records. The exact providers, locations and retention arrangements must be confirmed in the operational details below.

If you contact us, we process the correspondence, account reference and any attachments or troubleshooting information you choose to provide. Please omit passwords, identity documents and unnecessary sensitive information. Authorized administrators can inspect account and character information and use support or impersonation tools to diagnose issues; that access must be limited to legitimate operational needs.

5. Purposes and legal bases

Where the GDPR applies, account creation, authentication, email verification, password recovery and saving the game you request rely on performance of our agreement or steps you request before it (Article 6(1)(b)). Required fields are necessary to provide an account; if you do not provide them, registration or recovery cannot be completed. Basic public pages remain available without an account.

Protecting accounts, preventing abuse, troubleshooting, handling support and preserving necessary evidence of agreement rely on our legitimate interests in operating a secure and reliable service and resolving disputes (Article 6(1)(f)), balanced against your rights. The age declaration supports the adult eligibility rule; we do not automatically label it a legal obligation. Where a specific law requires processing, including a binding legal request or applicable accounting duty, we rely on that obligation (Article 6(1)(c)).

Optional analytics and opted-in promotional email rely on consent (Article 6(1)(a)); applicable device-storage and electronic-marketing laws also apply. Optional notification preferences are recorded when you request them. Accepting the terms or acknowledging this notice does not itself consent to analytics, marketing, sensitive-data processing or future unrelated uses. We will identify a new purpose and its lawful basis before using information incompatibly with the original purpose.

6. Adults only and age assurance

Accounts and play are restricted to people aged 18 or older. Signup and renewed acceptance include a self-declaration, stated beside the button that creates the account or confirms the terms. We record the declaration, not verified proof of age. The current flow does not perform identity-document checks, facial age estimation or biometric age analysis. We will not describe this declaration as guaranteed prevention of access by minors.

A parent’s permission does not override the service’s 18+ rule. If you believe a minor has supplied account information or is using an account, contact us with enough information to identify the concern without sending unnecessary details about the child. We will investigate and restrict access and delete or otherwise handle information as required by law. If stronger assurance becomes necessary, its purpose, method, data, retention and applicable legal basis must be assessed and explained before deployment.

7. Email, notifications and consent choices

News by email and optional notifications start unchecked. We record the opt-in time and allow you to switch these choices off in your account. News emails include an unsubscribe route. Withdrawal stops future consent-based communications; it does not make earlier lawful processing unlawful. A limited suppression record may be necessary to respect an opt-out and prevent accidental re-subscription.

Necessary service messages, such as address verification, password recovery and important security or legal notices, are distinct from marketing and may still be sent on an appropriate legal basis. A notification preference alone does not mean that the website requests browser push permission or collects a push subscription: those features are not implemented in the current account flow.

8. Cookies and local browser storage

Essential storage supports the session, persistent sign-in, protection against forged requests, language selection and functional game settings. Local storage can keep audio, graphics, accessibility and control choices, belt layout, quest guidance, waypoints and help-tip state. Tab session storage can keep travel or loading information. Your analytics choice is stored as j12.consent.v1 for up to 180 days.

The Cookie Policy explains storage categories and choices. Rejecting analytics does not prevent registration or play. Browser controls let you clear storage; doing so can sign you out or reset local settings but does not delete your server-side account or saved character. Essential storage is used to provide requested functionality and is not permission to track you for advertising.

9. Optional Google Analytics

Only when a valid measurement ID is configured and you separately accept analytics do we load Google’s analytics tag. Google can then receive website interaction and technical information such as visited page paths, device and browser characteristics, identifiers and network information. The integration removes query strings and fragments from the page and referrer values it supplies, disables Google signals and advertising-personalization signals, and leaves advertising consent denied. We do not intentionally send your name, email, password or saved game to Analytics.

Automatic analytics measurements may still include interactions and technical information collected by the Google runtime. We do not claim that every analytics record is anonymous or that we control every step of Google’s processing. Read Google’s linked privacy information. You can withdraw consent through Cookie settings; the implementation disables tracking, removes accessible first-party Analytics cookies and reloads a page when needed to stop the loaded runtime. Withdrawal does not recall data already lawfully received by Google. Cookie lifetime is requested as 180 days; analytics event retention is a separate provider setting that must be confirmed.

10. Who receives information

Access is limited to authorized people working for the operator and service providers needed for hosting, databases, backups, security and email delivery. Providers receive only information relevant to their role and must be subject to appropriate confidentiality, security and contractual arrangements where required. The operational details below must identify the actual hosting and email arrangements rather than every integration the framework could support.

We may disclose necessary information to professional advisers, authorities or courts when a lawful obligation or a properly assessed legitimate interest requires it, and to protect rights or investigate abuse with proportionate safeguards. A proposed organizational transfer must respect applicable law, appropriate confidentiality and transparency. We do not currently sell personal information, run targeted advertising or disclose account data to data brokers. Ordinary external links do not automatically authorize a transfer of your full account to their destination.

11. Donations and payment information

The current donation endpoint does not create a payment checkout, collect card details, charge money or store a donation payment record. Stripe is mentioned as a planned checkout provider; it is not an active payment flow in the current code. Submitting the donation form currently returns a notice that donations are closed.

Before payments are enabled, this notice and checkout must describe the actual payment provider, the information exchanged, controller roles, payment and transaction records, applicable legal bases, transfers and accounting retention. We will not infer permission to share data or charge a card from account acceptance. A third-party provider’s privacy policy does not replace our duty to explain our own processing.

12. International processing and transfers

The software alone does not establish the location of production servers, backups, email processing or provider support access. Those locations and the applicable transfer arrangements must be confirmed below. Optional Google Analytics can involve processing outside your country and outside the EEA. Do not assume that a European website name guarantees that every recipient remains in Europe.

Where GDPR Chapter V applies, restricted transfers require an applicable safeguard, such as a valid adequacy decision covering the actual recipient or appropriate contractual safeguards with any necessary supplementary measures. We do not claim that a particular provider is covered without checking its entity, role and current arrangement. You may request information about relevant safeguards and how to obtain a copy, subject to lawful redactions. Analytics consent is not treated as a blanket waiver of transfer requirements.

13. Retention and account deletion

Account and gameplay information is kept while needed to provide your account and saved progress. On a verified closure or erasure request, information must be deleted or anonymized unless a specific lawful reason requires limited continued retention. We do not promise automatic deletion after inactivity because the current service has no such scheduled policy. Character deletion alone does not delete the account or every operational record.

Security records, support correspondence, consent and acceptance evidence, unsubscribe suppression records and legal-dispute records should be retained only as long as their purpose, an applicable limitation period or a legal obligation justifies. Backup copies may persist until their documented replacement cycle; restored data must remain subject to relevant deletion instructions. Log periods, backup cycles, provider-specific retention and any justified legal holds must be finalized in the operational details below. We do not claim a fixed deletion deadline or accounting period that has not been established.

The browser analytics-choice record expires after 180 days. Optional Analytics cookies are configured to request a 180-day lifetime. These device-storage periods do not set the retention of account data or Google’s server-side analytics events. You can ask for the retention criteria applying to a particular category.

14. Your privacy rights

Where applicable, you may request access and a copy of your personal information; correction; erasure; restriction; and portability of information you supplied where processing is automated and based on consent or contract. You may object to processing based on legitimate interests for reasons relating to your situation, and you may object to direct marketing at any time. You may withdraw consent as easily as giving it through the available settings or by contacting us.

These rights have legal conditions and exceptions. We may need to retain specific information to meet a legal duty or establish, exercise or defend legal claims; we will explain a refusal or limitation where required. You are not required to consent to optional analytics or marketing to exercise a right, and we do not penalize you for exercising one. If a request removes information needed to provide an account, continued account use may no longer be possible.

15. How to make a request or complain

Contact the operator above, preferably from your registered email, and describe the request. We may ask for proportionate information to verify account control; do not send a passport or other sensitive document unsolicited. There is currently no automated data-export or account-erasure screen, so requests are handled through the operator. Access, account preferences, public policies and contacting us must remain available even if you choose not to accept updated game terms.

Where the GDPR applies, we normally respond within one month of receiving a rights request. A necessary extension of up to two further months for complexity or number of requests must be explained within the first month. Requests are normally free; fees or refusals apply only where the law permits. You may complain to a competent supervisory authority, including the authority where you live, work or believe an infringement occurred. For processing under Latvian supervision, this is the Data State Inspectorate (Datu valsts inspekcija), linked below. You need not complain to us first.

16. Security and incident handling

The implementation uses password hashing, session authentication, authorization controls, request-forgery protection and request limits. These controls do not establish that every hosting or operational safeguard is configured correctly. The operator must maintain appropriate access controls, transport security, updates, backup protection, provider oversight and incident procedures. No internet service can guarantee absolute security.

Do not reuse passwords or share session links. Report suspected account compromise or exposed personal information promptly through the operator contact. If a personal-data breach occurs, the operator must assess it and notify the competent authority and affected people when the applicable legal thresholds require, including applicable GDPR notification deadlines. Acknowledging this policy does not release the operator from security obligations.

17. Sensitive information and automated decisions

We do not ask you to disclose health information, real criminal history, political views, religion, biometric data or other special-category information to play. The game’s subject matter does not establish that you hold a particular faith. Avoid providing sensitive details in names, feedback and support attachments. If handling such information becomes necessary, we must identify an applicable additional legal condition and safeguards.

The current service does not conduct biometric identification, infer your beliefs for advertising or make solely automated decisions producing legal or similarly significant effects on you. Security and gameplay automation still process ordinary technical and game information for the purposes described above. A future materially different use requires assessment and an updated notice before it starts.

18. Updates and further information

The date and version identify this notice. We will publish updates when practices change and provide additional notice of material changes where appropriate or required. A later notice does not retrospectively authorize an incompatible use of data. Where a new activity needs consent, we will request a separate choice before it begins.

Account records hold the latest terms acceptance, age-declaration time and acknowledged privacy version. Shared demo eligibility is recorded in the visitor’s session rather than treated as proof that every visitor using that account is an adult. Keep a copy of the notice if you want a personal record and contact us for questions about the practices or safeguards described here.