Privacy Policy

Who we are and what this policy covers

PlanGoLive is the travel and everyday planning application developed by Vardhan Raju. This policy covers Trip Planner, LifeOS, HealthFit and the official website at plangolive.in.

The information used depends on the features you choose, whether you use a guest or signed-in session, and whether cloud services are available. Offline-first does not mean that every feature or every record stays on your device.

Information you provide

We use the information you enter to provide the planning, collaboration and wellbeing features you choose.

• Account: display name, email address, authentication information and an optional profile image. Email/password authentication and Google sign-in are supported. Authentication credentials and sessions are handled by the applicable authentication service.
• Trip Planner: trip titles, destinations, dates, itineraries, notes, checklists, saved travel information and templates.
• Shared travel content: memberships, invitations, itinerary proposals, votes, activity records and other contributions you make to a group.
• Expenses: descriptions, amounts, currency, payers, split shares and settlement information. These records organize costs; PlanGoLive does not process the actual payments.
• LifeOS: tasks, priorities, schedules, goals, habits, check-ins, focus sessions, notes and any client or business transaction details you choose to enter.
• HealthFit: fitness preferences and goals, available equipment, routines, workout and exercise records, walking duration, distance and steps, hydration entries and daily summaries. Optional weight records and targets may be stored locally; do not assume every local record is synchronized.

Device information, permissions and diagnostics

Notification registration can send a push token, installation identifier, platform, operating-system details and app version to the backend. Guest installations can also register for general announcements. Signing out can unlink a token from an account without removing the installation registration.

The app and its online providers may process request metadata and operational errors when providing services. The app includes diagnostic logging and backend AI request/quota records; it does not establish a single retention period for all provider logs.

• Location is used for nearby discovery, directions and GPS-assisted walking features when selected.
• Activity recognition and step sensors support walking and activity tracking. The Android health foreground service can keep step collection running while the screen is off.
• Usage Access is optional and must be granted in Android Settings for screen-time features. Per-app usage information and monitored-app preferences are processed locally in the current implementation; the cloud summary payloads do not include per-app usage logs.
• Microphone access supports voice features. Speech recognition may use the device’s configured speech provider and can require internet.
• Notifications and alarm permissions support reminders and announcements. You can manage permissions in Android Settings; denying a permission can limit the corresponding feature.

AI-assisted planning and Google Gemini

When you submit an AI Trip Planner request, your prompt and travel preferences are sent to a Supabase backend function, which calls Google Gemini. Follow-up requests can include recent conversation messages and relevant details from your active itinerary, such as the destination, duration, traveller count, target budget and stop names.

Request identifiers, account identifiers, quota usage, status and error information can be processed to authenticate requests, manage access and diagnose failures. Do not put passwords, payment credentials, private health details or other information you do not want sent to an AI provider into a prompt.

We do not publish a specific Google-side retention period, training exclusion or paid-service data setting here. Those practices depend on the configured Google service and its applicable terms; we do not promise that AI requests are never retained or used by a provider.

AI output is a planning suggestion, not a confirmed booking or authoritative travel or safety advice.

Local storage and cloud storage

The app stores local drafts, preferences, cached content and offline queues on your device. Guest content can remain local, but online features such as AI, imagery, maps and notification registration still contact service providers.

Signed-in Trip Planner information can synchronize with its Supabase service. LifeOS and HealthFit use a separate Supabase account/session and cloud store. These sessions and identifiers are not necessarily interchangeable.

Cloud synchronization can include LifeOS planning records and supported HealthFit profiles, workout/exercise logs, walks, hydration and daily totals. Some information, including local-only preferences and records, may not be part of cloud synchronization. Clearing a local cache, signing out or uninstalling the app does not by itself request cloud-account deletion.

How information is used and shared

Information is used to provide authentication, planning, synchronization, group collaboration, notifications, AI suggestions and technical operation of the selected features.

People in a shared trip can see the content made available to that group. Consider what you put into shared notes and financial descriptions. Copies already exported, printed or received by other people are outside the app’s direct deletion controls.

Service providers receive the information needed to handle their features. The current app does not include an advertising SDK or data-broker integration. This is not a promise that providers process no operational metadata.

If disclosure is required by applicable law or needed to investigate a security issue, any retained or disclosed information must be limited to that purpose. This policy does not represent that a specific legal hold or fixed security-retention schedule is currently in operation.

Service providers and content sources

Supabase provides authentication, databases, storage and backend functions. Google Gemini processes AI planning requests. Google sign-in and Firebase Cloud Messaging support account access and notifications. Google ML Kit supports on-device translation after supported language models are downloaded.

Device speech and text-to-speech providers can process voice input or spoken output according to their own settings. Mapping, nearby place and destination-image features can contact OpenStreetMap-related services and Wikimedia Commons. Provider request metadata may include your IP address and the search or location information required for the feature.

The app includes exercise content attributed to RepDB and map attribution to OpenStreetMap contributors. This website does not embed the app’s map tiles or RepDB exercise illustrations. Providers’ privacy notices and applicable service settings also govern their processing.

Supabase privacyGoogle privacyGemini API termsOpenStreetMap attributionRepDB

Security and international processing

Cloud operations use authentication and database access controls, and configured online service endpoints use HTTPS. These measures do not make local storage end-to-end encrypted or guarantee that every component is free of security issues.

Cloud providers may process information outside your country according to the service region and provider arrangements. We do not claim a particular data-residency location or international-transfer mechanism without confirming the production configuration.

Keep your device and credentials secure. Never send your password, sign-in token or one-time code in a support email.

Data retention

Account-linked cloud records remain until removed by the applicable deletion operations or other supported data controls. Local information remains until cleared by the relevant controls or device storage management. Unsynced changes can be lost if local storage is cleared.

Shared trip records may remain for other members after your account is deleted. The deletion code attempts to transfer group ownership and remove or unlink selected account references; names or other information written into shared text are not guaranteed to be erased.

No verified fixed retention period is available for all infrastructure logs, backups, AI-provider records or manual support correspondence. Deleting application records does not establish that every provider backup or log is immediately purged. Contact support for the applicable handling of a specific request.

Account deletion and your choices

In the app, open Profile → Privacy & Local Data Controls → Delete Account & Cloud Data and review the confirmation. The request requires an authenticated account and connectivity.

The app has separate deletion operations for Trip Planner and LifeOS/HealthFit. LifeOS/HealthFit cloud deletion is attempted only when its session is authenticated. A partial failure or an inactive session can leave data in one service; complete deletion across both services is not guaranteed by the current client flow.

You can request help outside the app through the email process on the Delete Account page, including if you have uninstalled PlanGoLive. No anonymous automatic deletion form is offered. Ownership must be verified before a manual deletion is carried out.

Access, correction and privacy rights

You can edit supported records in the app, export supported travel data, manage device permissions and request help with access, correction or deletion. Rights to a copy, restriction, objection or portability may apply depending on where you live and the circumstances.

Send a privacy request from your account email where possible. Additional ownership verification may be needed, and some requests may have legal limitations. No universal response deadline is promised on this page.

Children’s privacy

The app’s published audience statement is for people aged 13 and older, or 16 and older in the European Economic Area. The current app does not include an age-verification or parental-consent workflow.

If you believe a child has provided personal information without appropriate authorization, contact support so the account and request can be reviewed.

This website

The website serves product information, artwork and self-hosted fonts. It has no account registration or email-subscription backend and no automatic account-deletion endpoint. Opening an email link uses your own email application; you choose whether to send the message.

No network analytics integration is configured in this project. Optional install-click events remain in the browser unless a separate integration is added. The hosting provider can process connection metadata and request logs; its production logging and retention settings need to be confirmed at deployment.

Changes and contact

We may update this policy as the product or its processing changes. The effective and last-updated dates identify this version. Review this page for the current description before using newly introduced services.

Use the contact details below for privacy questions, account deletion problems and requests about your information.