GoBack Privacy Policy
Last updated: November 8, 2026
GoBack ("the app") helps GO Transit riders file Service Guarantee refund claims for delayed trips. This policy explains what we collect and how you can delete it. Your use of GoBack is also governed by our Terms of Service.
What we collect
- Account and contact information: your name, email address, optional phone number, account identifier and sign-in method (Apple, Google, Facebook or email/password). Google and Facebook sign-in use Supabase OAuth only if you choose them. For Apple sign-in, we temporarily process the authorization code and store an encrypted Apple refresh token to revoke authorization when you delete your account, when available. Supabase sends email-confirmation and password-reset links. Email/password accounts must confirm their email before logging in; you can request a new confirmation in the app. We use account details to manage your account and provide contact details for claims.
- Consent records: the Terms and Privacy Policy versions you accept, acceptance times, filing authorization and confirmation that you are at least 18.
- Payment details and preferences: your home and work GO stations, notification preferences and payment method type. If you add a PRESTO card, we store its full number encrypted using AES-256-GCM to file claims. Card last-four digits are not stored in our backend or cached on your phone. Guest Sign-In uses no PRESTO data. Debit/credit fare confirmation details you provide are used to submit the claim, not saved as payment-card records.
- Station events: We never track your live location. Your phone only tells us when you enter and leave a GO station. Raw location fixes stay on your phone. We receive station ENTER/EXIT events with the station and time, a location-accuracy estimate and a low-battery flag to identify trips and handle interrupted detection. Our server also measures upload delay.
- Subscription status: purchase and entitlement information via RevenueCat, linked to your account, to enable your subscription. We do not receive the payment-card number used to buy your subscription.
- Trips and claims: stations, train, journey date and times, detection confidence, delays, fare/refund amounts, corrections and claim references, statuses and errors. We use these to assess, submit and track refunds. We also use public GO schedule and train-operation data, including ServiceUpdate cancellation records. We do not collect or scrape GO service alerts or weather advisories; GO decides eligibility, including its weather and special-schedule exclusions. Phone station times are read from recent events, not saved in trip snapshots. After expiry, trip history explains: Your phone's station data was deleted after 30 days under our retention policy; the times shown are GO's official schedule and real-time data.
- AI assistant chats: messages, recent conversation history, screenshots you attach and relevant trip, claim or saved-route details are processed to answer questions and help with claims. Screenshots may contain personal or payment information; share only what is needed. Assistant conversations, including extracted details, are held in memory only and are not stored on your device. Screenshots are not saved to on-device history. The assistant is covered by the Terms you accept during onboarding, not a separate opt-in. See the AI assistant section of our Terms.
- Push tokens and operational records: device push tokens and notification preferences let us notify you about trips and claims. Notification logs, failure alerts and request metadata help us secure and troubleshoot the service. Failure emails to our operator can include your email and trip details.
What we do not do
- We do not sell your data or share it with advertisers.
- We do not store continuous location history on our servers.
- We do not read your inbox or access your transit account. We use the contact and payment details you explicitly provide for claim filing.
Third parties
- Supabase: account authentication and database storage.
- Railway: hosts and runs our backend and processes requests.
- Anthropic: powers the AI assistant, including statement-image extraction. We send conversation content and relevant tool results; Anthropic says it deletes API inputs and outputs “within 30 days of receipt or generation”, except for services with longer retention, different agreements, Usage Policy enforcement or legal requirements. If content is flagged as violating its Usage Policy, Anthropic retains inputs and outputs up to 2 years and trust and safety classification scores up to 7 years. See its commercial API retention policy.
- 2Captcha: solves the GO claim form's CAPTCHA. It receives the CAPTCHA site key and GO page URL, not rider personal data or claim-form fields.
- Apple Push Notification service: push-notification delivery. The iOS app uses this service directly; its push tokens and notification content are sent to Apple.
- RevenueCat and Apple: subscription purchases and entitlements.
- Resend: sends operational and failure alerts to our operator.
- Apple: Sign in with Apple, if you choose it.
- Google: Google sign-in through Supabase OAuth, only if you choose it.
- Meta: Facebook sign-in through Supabase OAuth, only if you choose it.
- GO Transit / Metrolinx: receives the journey, contact and payment details needed to submit your claim and check its status. GO handles submitted claims under its own policies.
How long we keep data
Our retention policy is:
- Anonymous aggregates: daily per-train analytics kept indefinitely, without rider identifiers or individual journeys. Rider and claim counts below five are suppressed (stored as null); all counters and averages are suppressed for rider cohorts below five, and refund totals require at least five accepted claims.
- Trips and claims: while your account exists, including public GO stop-time snapshots, never per-station phone times.
- Granular phone station data: station events expire after 30 days by event time; all trip sessions expire 30 days after their last event. The daily 03:00 Toronto sweep can lag the cutoff by up to 24 hours. Uploads older than 30 days are ignored.
- GO API data: latest-state data and cancellation records for 30 service days; raw delay archives for 7 days by poll time. Public station reference data is kept indefinitely. The latest static schedule snapshot is replaced after each successful daily refresh; its feed hash and generation time are stored with it.
- Database notification logs and admin alerts: 90 days by creation time, or earlier account deletion for user-linked rows. Hosting logs, provider logs and operational emails are vendor-controlled, not covered by this database period.
- Rate-limit records: until expiry, with expired records removed by hourly and daily jobs.
Account details, saved PRESTO cards, preferences, subscription status and referral records are kept while your account exists, or until earlier removal where supported. Assistant chats, screenshots and extracted details are held in memory only; they are not saved to an on-device chat store or a server chat database. Our providers keep their copies according to their own retention policies.
Station events stored on your phone are deleted after 30 days; cleanup runs the next time the app opens, so a phone where GoBack is never opened again keeps older events until then. If your sign-in expires mid-commute, queued station events are kept on the phone so the trip isn't lost. Signing out, signing in as someone else, or deleting the account clears them.
Subscription purchase records are also held by Apple and RevenueCat; when you request account deletion, we request deletion from RevenueCat.
Data deletion
In the app, go to You → Account → Delete account → Delete everything. When deletion succeeds, we immediately hard-delete your account data from our application database, including your profile, saved cards, consent records, station events, trip sessions, trips, claims, referrals, user-linked alerts, notifications, public GO stop-time snapshots and push token, together with your Supabase sign-in account. Successful deletion requires Supabase Auth erasure; if that fails, the app shows an error and does not confirm deletion. We attempt to revoke stored Apple authorization before deleting an Apple sign-in account; a provider failure does not prevent deletion of your GoBack data.
Anonymous daily train analytics are not deleted with your account; public GO train-operation data remains under its retention periods. Deletion does not withdraw claims already sent to GO or erase copies held by our providers, operational logs and emails, or backups, if any; those expire under their applicable retention policies rather than being erased immediately. For instructions and help requesting deletion, see Delete account. You can also contact us to request access to or correction of your data.
Contact
Questions about this policy: support@gobackapp.ca. See also our Terms of Service.