TrueRussia covers travel across Russia—places and routes in the catalog, map and trip planner views, plus account-based features such as favorites, saved routes, collections, traveler stories, comments, and moderation. This page explains—in plain language—what data may be involved. It does not replace personal legal counsel; applicable law overrides any conflicting wording here.
What this policy covers
These rules apply to the TrueRussia web app across catalog, map, and planner surfaces. Editorial catalog content may appear alongside community material; profile data you provide and media you publish are described below.
Information you may provide
When you register or sign in, you may use email and password where enabled, or sign in through GitHub if it is configured. We receive and store identifiers for your user record and whatever profile fields you submit—email used for authentication and transactional messages, display name and optional biography or location-style fields where offered, plus an avatar image you upload. When you edit collections (“guide collections”), traveler stories, comments, catalog proposals, or uploads, your text and photo files pass to our servers. Guide-status requests may include your first and last name, phone number, and a link to your public social profile when you voluntarily submit those details.
Technical signals from your device
Cookies and sessions keep sign-in functioning. Locally, the browser may store favorites in localStorage, planner draft route shapes and helper flags in sessionStorage, and a random session id for first-party aggregated analytics on the home page stored in sessionStorage (we do not ship classic third-party advertising analytics alongside the core app). Hosting and CDN tiers typically collect request metadata—such as IP address, user-agent strings, timestamps—to keep the platform reliable, troubleshoot issues, and limit abuse.
Why we use this information
We process account and community data so that features operate, uploads reach storage, moderator queues work, moderation and security safeguards run, admins can investigate issues, aggregated usage statistics help us improve product quality, and we can reply when you contact us through email or the Contact page.
On-device drafts, synced favorites, and saved routes
Some experiences mix offline and synced modes: favorites may persist only inside your browser, or synchronize with your account when the deployment enables the cloud favorites path; otherwise it stays confined to one browser profile. Planner draft segments may stay in volatile browser storage until you choose to persist them—saved journeys tied to your account sit on servers and stay available once you authenticate.
Partners and subprocessors
Authentication may involve GitHub OAuth for users who choose that path alongside our email/password flow. Embedded maps rely on Yandex Maps API; Yandex publishes its terms and privacy documents separately from ours. CDN, hosting stacks, backup routines, object storage buckets for images, and outbound email relays also receive related traffic as ordinary infrastructure subprocessors—the site operators configure whichever providers run production.
When posts become visible to others
Collections, traveler stories, and comments carry moderation states and visibility settings. Content you publish openly can be reachable to site visitors or search engines depending on indexing settings. Draft, private, or restricted items are not aimed at broadcast audiences—hidden listings should remain inaccessible to anonymous visitors.
Moderation and account limits
Trusted moderators can review flagged material, withhold content from view, throttle features after rule violations, and coordinate with admins on editorial knobs. Sensitive admin actions tied to moderator tickets may be recorded in structured audit trails for accountability, safety, or legal escalation.
Security realities and exercising your requests
We work to safeguard data responsibly, but networked services inherit residual risks and we cannot truthfully promise perfect security or zero incidents. Reach out through Contact for corrections, removals, privacy questions, or profile issues; you can also rely on controls inside your Account area when they exist for specific artifacts. Fully automated account erasure pipelines may not be available—we still review manual requests pragmatically.
Policy revisions and outreach
Expect occasional updates reflecting product changes; continued browsing after edits means you accept the latest online version. Prefer the Contact hub for nuanced questions alongside on-site account tools when available.
Last updated: May 7, 2026