Relicvale privacy notice

Updated 29 October 2026. This notice describes the hosted Relicvale iPhone beta operated by Roman Vei. Contact: roman.dev.tech@gmail.com.

Account and sign-in information

For Apple or Google sign-in, Relicvale receives a provider-specific account identifier and, when supplied, your name and verified email address. The server verifies the provider's identity token and creates a Relicvale session. Relicvale does not receive your Apple or Google password. Optional email accounts use an email address and a password stored as a salted password hash.

Game progress and friends

The service stores the information needed for your traveller, cards, journal, rewards, journeys, collection display, friendships and expedition membership. Shared clues, reactions and virtual map markers are stored for your expedition. Friends and current expedition members can see the collection and shared activity allowed by the game's controls.

Traveller and marker positions refer to the fictional game map. The app does not request your device's physical location.

Service providers

Cloudflare hosts the game services, private expedition storage and map delivery. Apple and Google process sign-in under their own privacy terms; the Google sign-in SDK communicates with Google's authentication services. Network providers may process IP addresses and technical request/error information needed to deliver, operate and protect these services. Relicvale does not use advertising trackers or sell player information.

Your choices

You can sign out in Settings, leave an expedition and manage your shared activity in the game. Settings also provides Delete account and collection, which removes your account and associated records from the active account store. Technical security logs and provider-managed records have separate lifetimes; contact support with a data request or question. You can also manage or revoke sign-in access in your Apple or Google account settings.

Beta environments

The current expedition beta and earlier production beta can use separate account databases. Signing in to one does not automatically transfer progress from the other. Beta features and this notice may change; updates will be published here.