Privacy Policy
Leo Vegas: Self Companion
This policy explains how this application handles information and how to contact us about privacy.
Information we process
Leo Vegas: Self Companion stores your display name, local avatar, preferences, saved and visited places, private place notes, trips, itinerary events, addresses, bookings and ticket files, expenses and participant splits, proposals and votes, and journal photos, text, dates, ratings and sharing choices. The avatar, saved-place lists, place notes and preferences remain on your device. Trip content, participant names, events, attachments, expenses, proposals and memories are stored locally for offline access and synchronized to our backend. An automatically generated installation identifier and secret provide access without an account. The secret is kept in the device Keychain; the server stores its cryptographic hash. The backend also stores hashed invitation codes and operation identifiers to process joins and avoid duplicate changes. Requests to the service and public policy expose network information, such as IP address, request time and technical request metadata, to Railway infrastructure. We do not operate an analytics or advertising SDK.
How we use information
We process this information to save your travel plans and memories, make them available offline, synchronize changes, authorize installation-specific access, invite trip participants, support voting, calculate expense balances and honor deletion requests. Camera access is used only when you choose to take a photo. Selected library photos are used for journal entries or your local avatar. Optional notifications remind you about events on your device; no push notification provider is used. Technical infrastructure information supports delivery and security of the hosted service. Your information is not used for advertising or sold.
Service providers and sharing
The backend is hosted on Railway, which processes service requests and stores the application database on a persistent volume. Railway and its infrastructure providers can process technical delivery and hosting logs. We do not send trip content to analytics, email, advertising or external image-processing services. Participants who join a trip can see its itinerary, tickets, expenses, member names, proposals, votes and memories marked as shared. A private memory is returned only to the installation that authored it, including when another participant is the organizer. Anyone who receives a valid invitation code can join its trip, so share codes carefully. Opening an official website or sharing a text address invokes an external service or app you select, subject to its own privacy practices.
Data retention
Local records remain until you delete them or remove the app, subject to device storage and backup settings. Keychain items may persist separately from the app. Server records remain while needed for the trips you keep, until the relevant trip or installation is deleted; there is no automatic trip expiry. Invitations expire after seven days. The application does not configure a fixed Railway log or backup retention period, and we cannot promise a specific infrastructure retention duration. Deletion removes live database records and attempts to clear SQLite journal pages; provider backups, device backups or files already copied by participants can remain according to their own lifecycle and settings.
Deleting your information
Use Settings to delete all installation data while connected. The backend deletes trips you organize, removes your membership and authored content from other trips, removes related invitation and operation records, adjusts remaining expense shares, and invalidates your installation secret. After confirmation, the app removes local records and resets the Keychain secret. Organizers can delete individual trips; participants can leave trips, which removes their related content. You can delete your own journal entries and expenses. Shared copies already saved outside the service cannot be recalled. Contact ellery1cavendish@icloud.com about deletion questions. There is no account recovery; losing the installation key can prevent us from verifying access to stored trip records.
Permissions and your choices
The app asks for camera permission only when you take a photo and requests optional local-notification permission when you enable a reminder. The system photo picker lets you choose specific images without granting unrestricted library access. Denying permission leaves other planning features available. You can change camera and notification permissions in iOS Settings, remove a selected photo from its entry, or turn off individual reminders. The app does not request location, contacts or tracking permission and contains no embedded geographic map. Sharing a photo intentionally sends the selected journal content to the backend as part of synchronization.
Your privacy rights
Depending on your location, you may have rights to access, correct, delete or restrict processing of your information, and to raise concerns with a relevant privacy authority. You can inspect and edit trip content in the app and use its deletion controls. Send privacy requests to ellery1cavendish@icloud.com. We may need information sufficient to verify your installation's access without asking you to disclose its secret by email. The contact address is for privacy questions; the app does not create an email account, send email or require an email address to function.
Security
The app uses HTTPS for deployed requests, a random per-installation secret stored in Keychain with device-only accessibility, and server-side membership and role checks. Only hashes of access secrets and invitation codes are stored on the server. Local records use iOS file protection. The application database is not separately encrypted by application code; hosting storage protection is managed by Railway. Server code avoids logging authorization headers and request bodies. These measures reduce risk but cannot guarantee absolute security. Keep your device and invitation codes secure, and never share your installation secret.
Children’s privacy
This companion is designed for adult independent travelers and small travel groups, rather than children. It has no public social feed or gambling functionality. We do not knowingly seek personal information from children. If you believe a child has provided information that should be removed, contact ellery1cavendish@icloud.com so we can assess the request and available verification options.
Changes to this policy
We may update this policy when the app's processing or hosting practices change. The effective date above identifies this version. The current policy is available from Settings and the public privacy page. Material processing changes will be reflected in the policy and, where appropriate, communicated through the app. Contact ellery1cavendish@icloud.com with questions about these practices.