GoBag privacy Request account deletion
Data summary
In short, GoBag handles: your account email and sign-in provider; your display name; circle membership, messages and statuses; an optional profile photo; an optional one-time location check-in you choose to send to a circle; rounded location or a chosen city for weather; and the support or bug reports you choose to send. GoBag does not track you across other companies' apps or websites, shows no ads and has no analytics or advertising libraries.
Who operates GoBag
GoBag is operated by Jerrick Karsten Xavier Madrigal, under the brand The Xavier App. Contact us at thexavierapp@gmail.com for privacy, access, correction or deletion requests. We aim to acknowledge requests within 7 days and explain verification and next steps. Some requests can take longer to complete.
This notice describes GoBag for Android and iOS (the versions available on Google Play and the App Store). It is for adults aged 18 or older.
What stays on your device
My GoBag checklists, notes, diary entries and recordings are stored locally. Language, theme and private nicknames you assign to contacts are device settings. Signing out or deleting your cloud account does not erase these local items. Remove unwanted items using the app controls and keep a backup before removing anything important.
Exports, recordings and backups remain wherever you save or share them. Android or device backup services may copy app data according to the device's settings. We have not configured an explicit app-wide exclusion for all such backups.
Dictation uses the device's speech-recognition service; processing and availability depend on that service. Do not assume speech recognition always works offline. Microphone access is used when you choose recording or dictation.
Accounts, circles and conversations
Google Firebase Authentication processes account identifiers, sign-in email and provider information to authenticate accounts. GoBag supports email, Google and (on iPhone) Sign in with Apple. If you use Sign in with Apple you may choose to hide your email; Apple then gives us a private relay address. Phone-number sign-in is not available.
Circle membership, shared names, optional custom photo thumbnails or Google-photo links, statuses and chat messages are stored in Firebase Firestore. Accepted circle members can see information shared with the circle. Direct chats are restricted to their participants. Chats are not end-to-end encrypted. Recipients can keep screenshots or other copies.
You can report a chat message from the message menu and block a person. Reports go to the operator (see below); blocking hides that person's messages for you. The operator can remove content or accounts that break the rules. Photo sharing requires an explicit action. Loading a shared Google photo can contact Google. A private contact nickname stays on the setter's device and does not rename that person for everyone else.
Location, discovery and weather
Circle location sharing is a one-time action, including coordinates, accuracy and a timestamp. It is not continuous background tracking. Check-ins stop being visible after one hour, but the stored record can remain until replaced, stopped or removed through membership/account cleanup.
Optional Nearby discovery is not offered in the current app versions. If it is offered in a later version, it stores a coarse location cell, display name and expiry information, and this notice will be updated first.
Nearby invitations can copy the sender's display name, circle name and invitation code into the recipient's inbox. Block lists contain account references. The current v2 account-deletion cleanup removes that account's outgoing Nearby invitations and block references in other accounts, as well as its stored discovery entries. Hiding from discovery alone does not recall an invitation already sent. Older completed or legacy deletion jobs need separate support review; they are not automatically reopened.
Weather is available to signed-in accounts with a verified email. It can use a chosen city or, after consent, rounded location coordinates. Requests pass through Cloudflare to WeatherAPI, with Google checking sign-in. This is separate from sharing a circle check-in. The app remembers the weather choice and may show a valid cached forecast. The current server cache lasts 15 minutes; device caching follows forecast expiry.
Google Maps provides the embedded map and external directions. Map use and external links can send network, device and request information to the relevant provider.
Notifications, support and illustrated guides
Optional background notifications are available on Android only; iPhone notifications are not available yet. They use Google Firebase Cloud Messaging and a Cloudflare server. Device registration tokens, account IDs and notification-routing metadata are stored to deliver and retry notifications. Notification permissions and app opt-in control enrollment on eligible accounts.
Notification jobs can store recipient account references and device-registration identifiers for retry and deduplication. Current v2 account deletion removes the departing account's saved targets from other senders' jobs while preserving other recipients' delivery state. Delivery also checks current account and membership status. Historical legacy/completed deletion jobs may need separate support review.
When you consent and submit a bug report, the entered text and selected app details pass through Cloudflare to the operator's Telegram support channel. Email requests use the email app you choose. Avoid including passwords, verification codes, private conversations or unnecessary personal information. Account deletion does not automatically recall Telegram or email copies.
Illustrated guides load online from Cloudflare. The App tutorials list opens short tutorial videos on YouTube only when you tap one (in your browser or the YouTube app); GoBag sends no account details to YouTube, but YouTube and Google receive your IP address and technical request data under their own policies. External services may receive IP addresses and technical request data when you use them.
Providers, storage and safeguards
Google/Firebase provides authentication, circle data storage, maps and notifications. Cloudflare hosts server functions and illustrated guides. WeatherAPI provides forecasts. Telegram and your chosen email service handle support messages.
Firestore is configured in Singapore. This does not mean every provider processes every type of information only in Singapore. Provider-operated systems may process data in other countries under their own terms and privacy policies.
Provider-operated logs and backups have their own retention schedules. For example, Firebase describes retaining authentication IP logs for a few weeks and removing other deleted authentication information from its live and backup systems within 180 days after customer-initiated deletion. A successful GoBag deletion screen is not a claim of immediate erasure from every provider log or backup.
Cloud access uses account and membership checks. Sharing photos, location, discovery information and notifications requires the related user action or consent. Revoking device permissions can limit a feature. These safeguards do not prevent a recipient from retaining a copy of shared content.
The apps do not include advertising or subscription SDKs. The Android app disables Firebase Analytics collection and automatic FCM initialization in its manifest. That does not mean the app or its providers collect no data. The iPhone app contains no analytics, crash-reporting, advertising or tracking library, uses no advertising ID and does not track you across other companies' apps. Apple separately gives the developer anonymous App Store and TestFlight statistics, which are Apple's own and not collected by the app.
Retention and deletion
Cloud conversations and shared profiles do not currently have a general automatic retention deadline. Retention depends on feature controls, membership and account cleanup.
- Operator-controlled support-report copies are to be removed within 30 days after the case closes. Verified deletion requests are considered separately; that period is not a required waiting time. Older Telegram copies need manual handling.
- Minimal privacy/deletion request-handling records, such as the request date, verification status and outcome, are to be removed within 30 days after the request closes. If a record must be kept longer for a justified reason, we will explain the reason and applicable retention to the requester. This is separate from server deletion/recovery receipts.
- Completed notification jobs older than 24 hours and device registrations older than 30 days are eligible for bounded scheduled cleanup. These are eligibility thresholds, not guaranteed deletion times.
- Minimal deletion/recovery receipts are reviewed after at least 30 days. They can remain longer when completion cannot be confirmed.
- Cloud account deletion does not erase local notes, recordings, exports, device backups or copies held by other people.
Every account can delete itself inside GoBag (Settings, delete account): sign in again, confirm, and keep the app open while it finishes; this normally takes a few minutes. Signing in with Apple is also revoked with Apple on deletion. You can also email support to request deletion, even if you have uninstalled the app. Circle owners must transfer ownership of circles with other members first; publishing/admin roles need a support handover.
The tested current v2 cleanup removes account access and associated cloud records. It removes sent group messages and direct conversations, including replies for both participants; other members' group messages remain. It also removes stored discovery entries, outgoing Nearby invitations, block references and notification-routing targets for that account. Support-provider copies and historical legacy/completed deletion records need separate handling. We will explain outstanding actions rather than claiming an incomplete request is finished.
Adults, choices and requests
GoBag is intended for adults 18 or older. Guardian-linked child accounts and parental sharing controls are not implemented. Do not create an account for a child.
You can choose whether to share photos or location, enable nearby discovery or notifications, and grant device permissions. You can contact support to request access, correction or deletion. Identity verification may be needed, but never send passwords, one-time codes, access tokens or identity documents in an ordinary support email.
Changes to this notice
This notice was updated on 12 November 2026. Future changes will describe the actual service at that time; planned features are not covered as though they already exist.