PLAYER POLICY
Privacy Policy
How VEILFALL collects, uses, protects, and retains player information.
1. Scope and operator
This policy applies to VEILFALL RPG and veilfallrpg.in. The service operator is currently identified as: Owner legal/business name — owner action required.
2. Information VEILFALL processes
Account information
We process the login username, normalized email, immutable internal account ID, policy acceptance records, account state, email-verification and recovery-token records, and server-authoritative sessions. Passwords are not stored in readable form. The service stores a salted, one-way PBKDF2-SHA-256 password derivation; raw session, reset, and verification tokens are not stored in the database.
Gameplay information
We save character and profile data, race, level, rank, EXP, combat attributes and pools, training, releases and release abilities, inventory and field kits, Kan, Shards, faction and allegiance, map position, PvE/PvP records, battle state and history, Daily Directive progress, achievements, and related persistent progress.
Community information
Signal posts, mentions, memes or reactions, Inbox messages, journals, profile content, and other content players submit are stored to operate those features. Inbox messages are intended for the sender and recipient, but may be accessed when reasonably necessary for safety, abuse investigation, security, or legal compliance.
Security and technical information
The application processes session cookies and request security information. For login abuse prevention it derives non-reversible rate-limit keys from the request network address and attempted identifier; it does not store the raw address in the game database. Hosting infrastructure may process ordinary request, browser, error, and security logs. VEILFALL does not currently use advertising or marketing-tracking cookies and does not create a separate device fingerprint.
3. Why information is used
Information is used to create and authenticate accounts, preserve game progress, provide account recovery, run multiplayer and social systems, deliver player-requested features, prevent cheating and abuse, moderate community areas, investigate security incidents, maintain reliability, and comply with legitimate legal obligations.
4. Service providers and transfers
VEILFALL is deployed through OpenAI Sites infrastructure. Application database and object storage functions use the underlying Cloudflare D1 and R2 services. Those providers may process data to host, secure, and deliver the service under their own applicable terms. An email-delivery integration is prepared but is not currently configured; this policy will identify the provider before email delivery is enabled. VEILFALL does not sell player personal information.
5. Retention
Account, gameplay, and community records may remain while an account is active. After an account or privacy request, some records may be retained where reasonably necessary for security, moderation history, fraud or dispute prevention, backups, database integrity, or legal obligations. Expired sessions and one-time tokens may be retained briefly for security auditing before cleanup.
6. Player requests and deletion
Signed-in players can open Profile → Account security & privacy to request access, correction, or account deletion. A deletion request is reviewed rather than executed instantly because gameplay, battle, and community records are linked. The request can only be submitted for the authenticated account. If you cannot sign in, use the contact route below.
7. Security
VEILFALL uses server-authoritative identity checks, hashed credentials and tokens, secure cookies in production, request-origin checks, rate limits, and scoped account lookups. No online service can promise absolute security. Players should use a unique password and report suspected account compromise.
8. Age and eligibility
You must be legally permitted to use an online account service where you live. The final minimum age and any parent or guardian consent requirement must be set by the owner after jurisdiction-specific review and will be maintained as one central policy setting.
9. Policy updates
Material changes will be published with a new effective date and revision. Where appropriate, renewed acceptance may be requested before continued account use.
10. Contact
Public privacy/support contact: Public support/privacy email — owner action required. Signed-in players may use the privacy-request controls in Profile while this public contact is being finalized.