Privacy and locality controls should stay legible across the whole network.
This policy explains what DeadArk processes, how local discovery works, and how visibility choices relate to identity, participation, and safety. Last updated June 8, 2026.
Calm, readable policy pages inside the same system.
These pages should feel authoritative without dropping out of the DeadArk design language. The goal is clarity, not spectacle: stronger rhythm, stronger hierarchy, and direct explanation.
Information you provide
This can include your profile, interests, posts, projects, publications, messages, community memberships, and information you add for a business or institution.
Locality and location
Local discovery is optional. You can enter a place or allow a one-time device-location request to suggest an area. Permission can be denied or revoked. DeadArk does not publish your exact location, does not use background location tracking, and does not require locality to use public features. You can change or remove locality information at any time.
Account and security data
We process the information needed to operate passkey sign-in, authorize devices, protect accounts, prevent abuse, and recover access. Your recovery words should remain private and are not meant to be shared.
How information is used
We use information to operate the service, show relevant interests and local communities, enable communication, keep the platform safe, understand reliability, and comply with legal obligations.
Visibility and safety
You control what you publish and which locality you share. Other people may see public profile information and public activity. Avoid posting precise addresses or sensitive location details. Reporting and moderation may be used to address harmful behavior.
Sharing and service providers
We do not sell personal information. Information may be processed by infrastructure and security providers needed to run DeadArk, or disclosed when required by law or necessary to protect people and the service.
Your choices
You may update your profile, remove locality information, leave communities, export available account information, or request account deletion. Some records may be retained when required for safety, legal compliance, or system integrity.
Trust pages should still route people into the right DeadArk context.
These pages are not isolated legal dead ends. They should explain the rule or safeguard clearly, then point people toward the correct surface for access, security, recovery, or broader system understanding.
DeadArk App
Use the app for account controls, profile updates, and the broader identity context behind privacy choices.
Route here when the user needs to change account state or review what their identity exposes across the network
Communities
Use the community surface when shared locality and participation boundaries need a more focused social context.
Route here when privacy questions are tied to how community visibility and local belonging should behave
Docs
Use Docs when you need structured reference material about controls, safeguards, or supporting explanations.
Route here when the next step is reference and procedural clarity rather than app interaction
Privacy choices should map cleanly to user intent.
People should understand what is public, what is local, what stays private, and where to change those settings. The design goal is not just disclosure. It is a system where visibility and locality are understandable before a mistake happens.
Help should stay available in context.
When someone has a privacy question, the answer layer should respond from the user’s actual context: their active identity, their locality settings, and the focused surface they are using, while still linking back to the broader DeadArk account model.
Even trust and policy flows should make sense relative to the wider app, the user's active identity, and the focused surface they came from.