Your data in GoPlan
Updated 6 November 2026. This explains the current GoPlan pilot. The website supports personal accounts and cloud roadmap syncing.
University inquiries
The contact form saves your name, work email, organization, message and any selected package estimate for the GoPlan team to respond. A notification containing these inquiry details is sent through Resend to partnerships@planwithgoplan.com. Email copies are retained in the partnerships mailbox separately from the website’s inquiry records. Inquiries are retained for up to 180 days and removed on a later inquiry or owner review. They are not sent to the planning AI. Only authenticated GoPlan owners can read the inquiry list.
University pilot access
Contracted pilots can restrict access to a university-provided list of approved institutional emails. The access list stores hashes scoped to that university, rather than readable roster addresses. Removed students lose access on their next request, including during an existing session. Their saved work is retained under the account storage rules below. Pilot accounts are separate from university accounts. The public AUI demo accepts personal email accounts.
Your personal GoPlan account
Verify your email using a one-time code and provide your first and last name to create a GoPlan profile. Then create a password for future sign-ins. Supabase handles email verification and password storage; GoPlan does not store your password. Password recovery requires a new email code; GoPlan stores your account identifier and email. A secure sign-in cookie remembers your session for up to 30 days, unless you sign out or delete your GoPlan data. This identifies your account; it does not verify that you are an AUI student. After you agree to cloud saving, GoPlan stores your profile, questionnaire answers, roadmaps, course progress, grades and notes to restore your work across browsers and devices. Names are used for your welcome and account display, not academic recommendations.
Your account data remains until you delete it. In Account you can edit your name, download your account data, sign out or permanently delete your cloud profile and roadmaps. The owner dashboard lists registered names, emails, joining dates and last activity dates; it does not display your roadmap, grades or questionnaire. Authorized service operators may access stored data to maintain the service.
Device copies and shared computers
GoPlan keeps a local copy of your signed-in workspace, including unsynced edits, to recover interrupted saves. Wait for “Saved to your account” before switching devices. Conflicting edits are kept for your review instead of silently overwriting a plan. Sign out on a shared computer: GoPlan clears this account’s cached workspaces from that browser. Signing out does not erase separately downloaded backups or older device-only plans.
Existing device-only plans are attached to an account only when you choose to import them. Clearing browser storage removes local copies. The service includes one roadmap per account; you can edit that roadmap after saving.
When you ask the AI adviser
The adviser receives your questionnaire, academic choices and relevant change requests. Later changes also include course codes, statuses and semesters. The app excludes your name, sign-in email, exact GPA, grades and private progress notes from these requests. A yes/no indicator of accelerated-load eligibility may be included. Free text is sent as written. Avoid personal or sensitive information in free-text answers. GoPlan sends relevant, filtered planning context to TypeSafe’s Jev for routine choices, ranking and routing. GoPlan’s own code checks academic requirements and semester placement. Complex requests and fallback use OpenAI’s GPT-6.1 Sol. Explicit research requests use GPT-6 Luna for public-source search and extraction, and GoPlan reads consulted public source pages. Routine opportunity matching uses reviewed records and cached evidence. OpenAI requests set store to false. Research receives a smaller set of public-topic interests and change preferences, with email addresses and phone numbers removed; search instructions exclude identity, grades and private progress notes. Provider handling is described in OpenAI’s API data handling documentation. Recommendations need your review and do not confirm live course availability or AUI approval.
Request protection
Temporary server locks prevent overlapping paid adviser requests. They contain an opaque account/session hash, a random lock token and a short expiry, never your answers or roadmap. They are removed after the request or expire after the request deadline plus 30 seconds (currently 210 seconds), with expired locks cleaned on later requests.
Your service allowance
Each account includes one roadmap, two AI change prompts in each of five guided stages, and five global AI change prompts after saving. Unused stage prompts do not carry over. Submitted AI prompts use an allowance even if no change is accepted or a request fails. Requests recognized locally as unsupported do not use an AI change. Manual editing and Excel export remain available afterward. GoPlan stores per-account counters and private response receipts to enforce this allowance across devices and avoid charging twice for the same request. Receipts are removed when you delete your GoPlan data. A hashed account reference, used allowance counters and action identifiers remain to prevent allowance resets; they contain no email, name, answers or AI response text.
GoPlan’s first-party website analytics
GoPlan automatically measures visits to its public pages, active visible-page time and contact-button activity. There is no analytics consent dialog. Browser Do Not Track and Global Privacy Control signals are respected. A random browser identifier is kept on this browser for up to 90 days; a separate per-tab visit identifier resets after 30 minutes without activity. Clearing browser storage removes these identifiers. If browser storage is unavailable, temporary identifiers last only for the current page, which can increase visitor estimates.
GoPlan records an approved page label (home, demo, sign-in or privacy), the available sanitized referring URL, the visit entry link and its UTM source, medium, campaign, content, term and ID, broad traffic source, device category, coarse country code supplied by hosting, recently active visible-page time and counts of contact, demo, email and package-calculator actions. We store hashed random identifiers, never your raw IP address, form answers, account identity, questionnaire, grades or private roadmap. URL credentials and fragments, non-UTM query parameters and recognizable email, phone and token patterns are removed before transmission and checked again on the server. Some browsers supply only a referring domain or no referrer; GoPlan does not recover withheld information. Detailed attribution begins with this release, and earlier visits are not backfilled. Temporary hashed rate-limit records expire after an hour. Signed-in owners and known bots are excluded. These first-party records are separate from the Google tags described below.
After an inquiry is saved, we can count it as a conversion for the measured visit. The inquiry itself is still handled under University inquiries above, including when analytics is blocked or unavailable. Measurement records are kept for 90 days and removed on later collection or owner review; older visits cannot be recovered. Only signed-in GoPlan owners can view aggregate website analytics. Different devices, cleared storage, browser privacy settings and blockers affect the totals. Automatic collection began on 6 November 2026; earlier measurements, if present, used an opt-in tracker.
Google Tag Manager and Google Analytics
GoPlan also loads Google Tag Manager container GTM-KQJH88L5 on website pages, including sign-in, the demo and operations pages. This container is configured for Google Analytics measurement G-HPWJJGHLSR. Google’s configured tags can use cookies and process page views, referring URLs, browser and device information, network information and interactions according to the container settings. GoPlan’s installation code does not add names, email addresses, passwords, questionnaire answers, grades, contact-form values or private roadmap content to the Google data layer. Tags added or changed in the container are managed separately by GoPlan.
The exclusions and 90-day retention described for GoPlan’s first-party analytics do not automatically apply to Google’s separate measurement. In particular, operations-page and owner visits can appear in Google Analytics unless filtered there. Google data handling is described in Google’s Privacy Policy. Browser settings and blockers can affect delivery.
Small, private usage totals
GoPlan records daily counts of adviser operations, success and failure, response times, provider calls and reported token usage. It also counts plan saves, accepted updates and Excel requests. These aggregate counters contain no student identifiers, names, questionnaire answers, grades or plan contents. Local previews are excluded. Counters older than 90 days are deleted on the next measurement write. They cannot be traced back to a particular student, so there is no individual usage record to export or delete. Hosting and AI providers may separately process operational data under their own policies.
Earlier mistake reports
Mistake reporting has been removed from GoPlan. Earlier private reports and review history remain subject to their original 90-day retention period; expired corrections stop being used immediately. Removing the feature does not publish or delete earlier reports. For a request about an earlier report, contact the GoPlan teammate who invited you.
Who can access this information?
Device copies can be accessed by someone who controls your browser or unlocked device. Cloud roadmap requests require the signed-in account that owns them. The team’s online usage dashboard requires the owner’s authenticated account. The private operator terminal also supports a separate administrator credential. Review decisions record the reviewer and their explanation. For questions during this pilot, contact the GoPlan teammate who invited you. Account deletion does not delete earlier separate mistake reports. Contact the GoPlan teammate who invited you for help with an earlier report.
Sign-in service
Supabase and the configured email-delivery service process your email and authentication messages. Password setup uses a five-minute HttpOnly verification cookie and a single-use hashed verification record; completing setup or recovery revokes prior GoPlan sessions. GoPlan keeps a hashed session token and temporary hashed rate-limit records to operate sign-in. Session records expire after 30 days; expired sessions and rate-limit records are removed on a later sign-in operation. Signing out revokes that GoPlan session. Deleting your GoPlan data revokes all its sessions and removes the profile and cloud plans; the authentication provider may retain its separate account and operational records. Contact the GoPlan team for help with those records.