LAST UPDATED / 2026-11-15
Privacy notice
How this website handles information when you explore Veyra or join its community.
Who is responsible
The game owner and website operator are identified below.
Information used by the website
- Browsing: a random session identifier, anti-forgery token, temporary authentication counters and a random visitor identifier. Saved wiki and journal entries are associated with that visitor identifier.
- Accounts: username, a one-way password hash, selected game avatar, optional biography and cover, and creation/activity timestamps. Registration does not currently request an email address, date of birth or payment details.
- Community: discussions, replies, reactions, view counts, private-message threads and their participants, and moderation reports. Profiles and public posts can be viewed by other visitors. Messages are shown to their participants and are not end-to-end encrypted.
- Hosting: connection information, including IP addresses, is needed to deliver requests. The deployment provider may keep server logs. Providers, hosting location and log retention must be confirmed before launch.
- Administration: a separate private account stores the owner email, username, password hash, role and security timestamps. Optional authenticator secrets are encrypted; recovery codes are stored as one-way hashes. Public community registration does not create administrator access.
- Aggregate page counts: successful public page requests are counted by day and route. These counts do not store IP addresses, user agents, visitor identifiers or analytics cookies, and do not measure unique visitors. Administrators can disable them.
Purposes and legal grounds
Session data supports navigation, saved pages, sign-in and security. Account and community records support the features you choose to use. Security counters and reports help prevent abuse and investigate reported content.
Visibility, providers and transfers
Do not post credentials or sensitive information in public discussions. A private message is shared with its recipients and stored by the operator; authorised administrators may require access for security, support or legal obligations.
Retention
The session cookie normally lasts for the browser session, subject to browser restoration and server session cleanup. Accounts, posts, messages, saved-page lists and moderation records currently have no automated retention schedule in this development build.
The operator must define retention periods or criteria, backup expiry and account-deletion handling before public launch. Closing the browser does not delete server-side records. This draft does not promise automatic erasure that has not been implemented.
Aggregate page counts use a configurable 30 to 365 day retention period, with 90 days as the default. Expired daily records are removed during routine counted requests. Administrative security logs and content versions are kept privately and size or version bounded.
Your choices and rights
You can browse without registering, edit available profile fields, remove saved pages, sign out and clear the session cookie. Clearing it may disconnect the saved-page list associated with the old visitor session and requires signing in again.
Depending on your location and applicable law, you may request access, correction, deletion, a copy or portability, restriction, objection or withdrawal of consent. Identity verification and legal exceptions may apply. A working contact for these requests must be supplied before public launch; check the operator details below.
EEA and UK visitors may complain to their competent data-protection authority. US state rights, including California rights to know, correct, delete, non-discrimination and opt out of sale or sharing, apply where the statute covers the operator and processing. This build has no sale/sharing integrations or targeted advertising. A Global Privacy Control signal does not enable optional processing; there is currently no advertising processing to switch off.
Visitors elsewhere retain mandatory rights under their local law. This draft does not claim that one notice establishes compliance in every country.
Young visitors and changes
The operator must determine the intended audience, applicable age requirements and any parental-consent process before public launch. Registration currently has no age or parental-consent verification. Do not submit children's personal information through this development build.
Material changes to data use require updating this notice and providing any notice or consent required by law. The date above identifies this draft.
Optional analytics
Google Tag Manager loads only after you accept analytics. Advertising consent stays denied. Change your choice using Cookie settings.
Google may receive page and device information when analytics is enabled. The tags published in the container determine which analytics cookies and retention settings apply.
Your analytics choice is stored for 180 days in the first-party blockrok_analytics cookie. Rejecting analytics keeps Google Tag Manager blocked.
Fonts, artwork, video and 3D files stay local. This integration does not add account details to the data layer.
Game ownership
- Project
- BlockRök
- Legal operator
- WEAREHEARTIZE, S.L.
- Country of establishment
- Spain
- Postal address
- C/ Arquitecto Ramón Cañas Del Rio 7, 24007, Leon, España (Spain)
- Registration details
- NIF: B72428709
Reference information
- GDPR: transparency and individual rights
- AEPD: Guide on the use of cookies
- California Attorney General: CCPA
- FTC: Children's Online Privacy Protection Rule
These sources inform the draft. They do not certify compliance or replace the operator's deployment assessment.