Who we are
MetaDev.World operates MetaDev World Passport and this website. This policy explains the information processed when you create or use a passport, visit the website, receive notifications, share a profile, or request account deletion. Contact privacy@metadev.world about this policy or your information.
01 / What we process and why
Passport and profile information
Our backend stores your username, public key, key algorithm and fingerprint, account status, and creation/update times. If you complete a profile, it stores the first name, last name and citizenship information you provide. We use these records to provide your passport, verify signed requests, and display your profile.
Activity, sharing and invitations
We store account activity and its read status. If you create a share link, we store a token hash and a profile snapshot; anyone you give a valid link to may see that shared profile. Share links expire after 15 minutes. An invitation request can include an email address; invitation records are separate from your username-based passport account.
Notifications and device information
When notifications are enabled, we process a push token, device identifier, platform, app version and device model, together with the account association. We store notification content, delivery status and provider error information to deliver messages and diagnose failures.
Security and website requests
Our services and hosting infrastructure process network information such as IP addresses, request times and security/error logs. Signed requests include a timestamp, nonce and signature to help prevent impersonation and replay. Android builds use Google Play Integrity checks to assess app/device integrity. This website does not add advertising trackers or an analytics SDK.
02 / Your private key stays with you
The app keeps your private key on your device and uses it to sign requests. It can create an encrypted recovery export that you control. The glyph/PIN protection, local preferences and cached profile data are stored on your device.
On our account-deletion page, the private key you enter is used locally by Javelle's cryptographic signing plugin. The page sends a signed proof to our backend, not the private key. It does not save the key to browser storage. Never email us a private key or recovery file.
Protect your device and recovery exports. Losing the private key can prevent you from proving ownership; possessing the key allows someone to authorize account actions.
03 / Where information goes
We use hosting and infrastructure services to operate the website and backend. Google Firebase Cloud Messaging processes push tokens, delivery information and the notification payload needed to deliver notifications. Google Play Integrity processes information for its app/device verification service. These providers may process information in countries other than your own.
We may disclose information when necessary to comply with applicable law, respond to a valid legal request, or protect users and the service from abuse. We do not sell personal information or use it for targeted advertising. Information you deliberately share with other people is available to those recipients.
04 / Retention and account deletion
Active account records remain while your account is in use. You can request deletion on our Delete account page with your username and private key, without reinstalling the app. After successful verification, the backend removes the passport identity, profile, account activity, share records, and associated notification/device and delivery records from the active database. The page shows success only after this deletion commits.
Anonymous request nonce hashes are retained to prevent replay. Their expiry is five minutes after the signed timestamp, which can be up to ten minutes after receipt; expired records are cleaned up during later signed requests. Operational security logs rotate by storage volume rather than a fixed number of days. Limited information may remain where needed for security, resolving disputes or legal obligations. Operational backup copies may remain until the hosting backup lifecycle removes them. Contact us for details about retained records and applicable deletion requests.
Account deletion does not erase app data on your device, recovery files you exported, or copies already shared with another person. Clear app storage and remove recovery exports if you no longer need them. Invitation email records cannot automatically be linked to a username; contact us separately if you want an invitation email removed.
05 / Your choices and requests
You can manage notification permission in your device settings, control what profile information you provide and share, and request access, correction or deletion by contacting us. Depending on your location, you may also have rights to restrict or object to processing, receive a copy of your information, withdraw consent, or complain to your local data-protection authority. We may need to verify your ownership before acting on a request.
If you cannot access your private key, contact us for assistance. Do not send the key by email. We will explain what ownership evidence is needed and what we can do; a request without adequate verification does not automatically delete an account.
06 / Children and policy changes
MetaDev World Passport is intended for people who can understand and manage a cryptographic identity. If you believe a child has provided personal information without appropriate authorization, contact us so we can investigate. We update this page when our practices change and revise the effective date above. Material changes will be communicated through an appropriate service channel.
07 / Talk to a human
Privacy and data requests: privacy@metadev.world
Product questions: hello@metadev.world