TRANSIT · FREE ACCESS & EXISTING PURCHASES
Your information
How information is handled in local career tools and the separate professional workspace
Optional interview and workplace voice practice
The interview tool and workplace scenarios can record a spoken answer or reply only after you choose Record my answer or Record my reply and grant your browser microphone permission. Audio is held temporarily in this page for replay. Recording alone does not upload or save it to your account. Leaving the practice, changing the main question or situation, closing the panel, replacing a draft or leaving the page clears local takes. Saved account copies remain until you separately delete them.
Interview questions, follow-ups and workplace partner lines are authored practice prompts. They do not listen to or judge your answers. Optional question and partner playback uses an available local English browser voice. These tools do not transcribe recordings, send them to AI, identify a speaker or grade their speech. Record your own practice response and leave other people’s private conversations out.
When you save a voice recording
Saving audio is a separate choice from saving a written career draft. Choose Save this recording, review the signed-in email and recording title, then confirm. Transit uploads that completed take to its private Cloudflare database with its title, authored question or situation, chosen practice move when applicable, turn, file type, size, checksum, account ID and creation time. Saved recordings are private to your account. Retaking an answer makes a separate recording; it never replaces audio that was already shared.
An account can keep up to 30 recordings and 24 MiB of audio, with a 1.5 MiB limit per saved take. A browser may create a larger local recording; if it is too large to save, it remains in this page so you can replay it or make a shorter take. No recording is silently removed to make room. My Transit lets you play, download or delete your saved recordings. Ordinary career JSON drafts and account-detail JSON exports contain no audio bytes; download recording files separately to keep audio copies.
When you share chosen voice recordings
Every voice-recording selection starts unchecked. Choose the saved recordings and one recipient email, review the exact list and confirm. Transit stores the selected recording IDs, recipient email, owner ID, consent version and sharing times and state. No email or notification is sent. The recipient must sign in with that verified email and accept; acceptance binds access to their internal account ID. Pending requests show only a generic recording count, whether a reflection is included, and time, not your titles, questions, reflection text or audio.
Accepted recipients can read only the reflection snapshot you chose to share and play or download only the selected recordings, with their titles and authored practice context. A reflection-only selection grants no audio access. Recipients may leave short written feedback on selected original recordings and respond to the exact shared reflection and goal. They cannot edit the reflection or goal. Sharing voice does not share written drafts, future takes, your account or the professional workspace. Professional and checklist-team roles never grant automatic recording access. You can revoke a share or delete a recording to end future website access to that audio. Audio already loaded, downloaded, recorded or otherwise kept by someone cannot be recalled. Your source recording stays private when you revoke a share.
Saved recordings remain until you delete them or request removal while Transit operates. Deletion removes the active audio and its grants; sharing history, provider backups and copies outside Transit can remain under their retention practices. Clearing a practice page does not delete saved recordings or revoke a share.
Compare saved attempts privately
My Transit can play an original recording and a later saved attempt of the same authored practice prompt, move and turn for your own comparison. Playback uses the existing account-protected audio reads. Transit does not analyze, transcribe or score the recordings. The comparison choices themselves are temporary and are not a separate saved account record. Saving a reflection and goal is an additional deliberate choice, described below. The recordings and their existing feedback stay attached to their original saved takes.
Comparison starts with neither take selected for sharing. Choosing an original, a later attempt or both only prepares your selection for the recipient review and confirmation. An optional saved reflection has its own unchecked sharing choice. Nothing is shared automatically, and an existing share never expands to include a new take or reflection. Close or refresh the page to clear the temporary comparison; this does not delete saved recordings or a reflection already saved to your account.
Saved reflections and next-attempt goals
After comparing two saved takes, you may deliberately save a reflection of up to 600 characters and a goal of up to 240 characters. Either may be blank, but at least one must contain something to save. An account can keep up to 30 saved comparison reflections. Transit stores the text, goal, the two recording IDs, your account ID, a revision, and creation/update times in its private database. The reflection is private to your account. Reopening that pair can restore it; writing or choosing a goal alone does not save, share, analyze or score anything. These notes are not sent to AI.
Sharing the saved reflection is a separate unchecked choice. You may share it alone or with the recordings you choose from its comparison. Review the exact text, selected audio and one recipient before confirming. Transit stores a snapshot of the saved reflection revision, its authored practice context, its source reflection and share IDs, and the sharing time. A recipient must accept with the chosen verified account before reading it. Pending selections reveal only generic recording counts, whether a reflection is included, and sharing times. They do not reveal your reflection, goal, recording titles or comparison IDs. Sharing sends no email or notification and grants no access to other reflections or recordings.
Saving edits to your private reflection leaves earlier shared snapshots unchanged. You can revoke a selection to end the recipient’s future access to its reflection and audio. Deleting the saved reflection, or either of the two compared recordings, removes the active private reflection and its attached shared reflection copies; any remaining separately selected audio stays shared until revoked or deleted. Your account-detail JSON includes your saved reflections, outgoing snapshots and received responses with their original snapshot context, including responses retained after revocation. It includes received snapshots and your own authored responses only while their originating accepted access remains active. Outside copies cannot be recalled, and provider backups may retain copies under their retention practices.
Feedback on shared voice practice
After accepting a recording selection, the chosen recipient can deliberately post written feedback of up to 1,000 characters on a selected recording. Transit stores the comment, original recording and share IDs, student account ID, author account ID and verified email, and creation time in its private database. Each recording can have up to 20 comments and an account can hold 200 comments. No email or notification is sent, and feedback is not sent to AI.
The student sees all feedback on their own recording and can remove any comment. Each recipient sees only their own comments while the originating selection is still shared with their accepted account; other support people’s names and comments are not revealed to them. The author can remove their own comment while that access is active. Revoking sharing ends the recipient’s future feedback access, while received comments stay available to the student. Deleting the recording removes its active feedback too. Account-detail JSON exports include feedback within those same access boundaries. Copies already viewed, exported or otherwise kept cannot be recalled; provider backups may retain copies under their retention practices.
Practice again opens the authored question or situation; it does not copy feedback or audio into a URL or automatically share a new take. Feedback remains attached to the original recording. Use ordinary constructive practice notes and leave confidential school, medical and employer records out.
Responses to shared reflections and goals
After accepting a selection that includes a reflection, the chosen recipient may deliberately post a response of up to 1,000 characters to that exact shared reflection and goal. A shared snapshot can have up to 20 responses and a student account can hold 200 reflection responses, separate from recording feedback. Transit stores the response, originating share and student account IDs, author account ID and verified email, and creation time in its private database. The original snapshot supplies the context; responses are not sent to AI, scored or emailed.
The student can review all responses to their own reflection, including responses to older shared versions, alongside the exact text and goal the author read. They may remove any response. Each recipient sees and can remove only their own responses while the originating selection remains accepted, active and bound to their account. Other support people’s names and responses are not revealed. Sharing a later copy does not restore access to responses on a revoked selection.
Saving private edits does not change an earlier snapshot or move its responses onto the new text. A response never automatically changes the student’s goal. The student chooses whether to edit, save or share a next goal and whether to save a new practice attempt. Revocation ends the recipient’s future response access; received responses stay with their original snapshot for the student until removed. Deleting the private reflection or either compared recording removes its active shared reflection copies and their responses. Account-detail JSON follows these same access boundaries and includes the original snapshot context with exported responses. Copies already kept cannot be recalled; provider backups may retain copies under their retention practices.
Connecting a recording to a goal and response
If you choose to connect a later saved recording, Transit stores the connected and source recording IDs, private reflection ID and saved revision, exact reflection and goal text, optional chosen reflection-response ID and text with its creation time, authored practice context, account owner and connection time. The later recording must be a newer attempt of the same question, move and turn. You may keep one immutable connection per recording, up to 30 per account. Changes to the current private goal do not rewrite this saved connection. It is a student-chosen practice record, not an assessment or automatic measure of improvement.
The connection starts private. You may separately include it with its connected recording in a reviewed share. The recipient sees only the selected audio, saved goal and reflection, optional response text you chose, authored question and connection time. They do not get private comparison identifiers, unselected recording titles or the response author’s account identity fields through the connection. No new work is added to an older share automatically. Pending shares reveal only generic sharing metadata, and accepted access remains bound to the chosen verified account. Revocation ends future recipient reads and account-export access; it does not delete the student’s own connection.
You can remove a connection without deleting its recordings or private reflection. Removing the chosen response, private reflection or any source or connected recording also removes the connection and its active shared attachments. Independently selected audio remains under its existing controls. Account-detail JSON includes owned connections and only currently accepted, active shared connection content within these same boundaries; audio remains a separate download. Connections and feedback are not sent to AI, scored, transcribed or emailed. Copies someone already kept cannot be recalled; provider backups may retain copies under their own practices.
Your private practice progress timeline
Opening the timeline reads your own saved recording metadata and private practice connections to display them together in date order. Audio is fetched through the existing protected playback controls only when you choose to play it. The timeline shows a connected goal and only the response you selected for that connection; it does not collect other people’s comments into a new shared view. Opening the timeline creates no new saved timeline record, browser-storage copy, automatic evaluation or external service call.
Sharing a progress collection is a separate choice. Check two to six entries, review the exact recordings and any saved connection text from earlier to later, choose one recipient and confirm. Choices start unchecked. Transit stores the selected recording IDs, their order, whether each entry included a connection, any still-available selected connection ID, consent version and existing sharing account, recipient and status information. Earlier takes, other entries and future practice are never added automatically. Existing one-entry sharing remains available.
The recipient receives only the confirmed entries after accepting with their verified account. Connected text includes the saved reflection and goal and only the response you chose. It excludes private comparison identifiers, unselected recording details, other responses and response author account identity fields. A pending collection reveals generic metadata and the number of selected entries. A collection is accepted or revoked together; revocation ends future opening, playback, feedback and received account-export access.
Removing a selected connection, its private reflection, chosen response or a source recording clears the affected entry’s connected goal and response; independently selected audio remains available. Deleting a selected recording removes that entry, leaving the others. Recreating a goal, response, recording or connection does not restore the removed attachment or add work to an existing collection. Owner account-detail JSON includes their collection selections; received JSON includes only active, accepted selections and available connected text, without private source identifiers. Audio remains a separate protected download. Copies already kept cannot be recalled; provider backups may retain copies under their own practices. Closing, backgrounding or leaving the page clears the open timeline and temporary choices without deleting saved work.
Collection feedback and private next-practice plans
An accepted recipient can deliberately submit a written collection comment, up to 1,000 characters. Transit stores the comment ID and text, originating collection and owner, author account ID and verified email, creation time, the reviewed public collection’s content fingerprint and its entry count. It stores no copied recording, connected goal, reflection or response context with that comment. Fingerprints identify content changes; they are not grades, speech analysis or a measure of growth. The limits are 20 comments per collection and 200 received collection comments per student account.
A new comment must match the exact collection view reviewed by the author. Atomic source, selected-membership and active acceptance checks reject changed or unavailable work. Retry uses the same comment ID, body and reviewed fingerprint to avoid duplicate sends. Removing a comment clears its text and retains a small removed-record marker, so an uncertain send cannot bring the words back under that ID. A comment based on earlier content is marked when selected entries or connections change. Revocation alone ends recipient access without deleting the student’s received comment. Removing a connected goal never restores its text through this feedback view.
The collection owner can review and remove received comments even after revocation or removal of all selected entries. Recipients can read and remove only their own comments while their originating collection remains accepted, active and available to that verified account. Other recipients’ comments and account identities are not exposed. An old audio-only or reflection share does not gain collection commenting permission. Deleting the collection removes its comments; previously kept copies and provider backups may remain under their existing practices.
The student may separately save one private next-practice plan per owned collection, up to 30 plans per account. Transit stores its ID, collection and owner, optional reflection up to 600 characters, required goal up to 240 characters, revision and creation/update times. Only the owner may read, save or remove it. Reading feedback or choosing Plan my next practice does not copy suggestions, save words or alter a goal. Revision checks prevent a stale save from silently replacing a newer plan. A plan remains private after collection revocation or removal of its entries; the recipient response contains no plan or plan count, and existing shares never gain it automatically. Removing a plan clears its reflection and goal and retains its removed ID so a stale retry cannot restore them. You can deliberately create a new plan under a new ID.
Account-detail JSON includes the owner’s retained collection comments and private plans. It includes only a recipient’s own authored collection comments while the original collection is accepted, active and available, without any other person’s private plan or source context. Audio remains a separate download. Removed comments and plans are omitted from account-detail JSON. Complete database backups include active records and cleared removal markers under the existing private-backup rules; earlier backup copies follow the provider’s retention practices. Closing, backgrounding, printing or leaving clears copied collection views; unsaved plan and feedback words use deliberate discard controls where a handoff would remove them. Practice links include only the selected entry’s authored destination, never private plan or comment text. These features send no email and use no AI, transcription or scoring.
Collection-plan recording connections you control
The student may separately connect a later saved recording to one exact saved collection-plan revision and an optional received collection comment. Transit stores the owner and connection ID; target/source recording IDs, checksums and saved times; originating collection and plan IDs; plan revision/save time; copied reflection and goal; optional chosen comment ID, text, creation time, reviewed-entry count and whether it referred to earlier collection content; authored question context; reviewed collection fingerprint; connection and removal times. No unselected comments, source audio bytes or response author identity fields are copied into this connection.
The student chooses a source entry from the plan’s collection and a later take of that same authored question, move and turn, made after the selected goal and optional feedback were saved. Exact metadata, current collection fingerprint, plan revision and source/feedback checks are repeated atomically before saving. Each target can have one practice connection across comparison-based and collection-plan types. Up to 30 active collection-plan connections and 300 rows including cleared removal markers may be kept per account. The connection is private and immutable; it is a student-chosen practice record, not an assessment or a claim of measured improvement.
Sharing the connection is separate. New single selections use their own collection-connection consent; selected progress collections have an explicit new-type attachment for only the chosen target. A recipient must accept with the chosen verified account. Public connection text contains the selected target ID, exact copied reflection/goal, plan revision/save time, optional chosen response text/time/reviewed-entry count/context-change flag, authored context and connection time. It excludes source collection, plan, earlier recording, connection and comment identifiers and response author identity. It grants no editable plan, source-collection, other-comment or future-practice access. Previous audio-only and comparison shares never gain these attachments automatically.
Old comparison connection fields and old collection fingerprints remain unchanged. A progress entry gains collection-plan fields only when that attachment was deliberately included. After removal, its marker can show that the connected words are unavailable while the separately selected target audio remains. Revocation ends future recipient reads, audio and received account-export access to the new selection; it does not remove the student’s private connection. An earlier source collection may remain revoked while the student separately chooses a new reviewed share.
Removing a connection clears its copied reflection, goal, feedback and context while retaining a removed ID so uncertain retries cannot restore the words. Removing its private plan or chosen comment atomically clears dependent connection snapshots, deletes their single-share text attachments and nulls progress pointers. Source-plan edits and revocation do not rewrite saved connections. Deleting the source selected entry, source recording or target recording follows their ownership-bound foreign-key removal rules. Independently selected audio retains its existing controls. Already kept copies and earlier provider backups cannot be recalled.
Owner account-detail JSON includes active private collection-plan connections and owned selection links. Received connection JSON includes only active, accepted, correctly consented attachments with selected target membership, using the same public fields and no private source identifiers. Removed snapshots are excluded and unavailable progress markers carry no copied text. Complete private backups include all 40 application tables and both migration-history tables, cleared removal markers, attachment foreign keys and source-removal triggers; restore checks cover recursive-trigger settings both off and on. These controls use no AI, speech analysis, email or automatic sharing.
After-attempt reflections and explicit sharing choices
A student may save a separate reflection and next goal for the exact earlier-reference and connected-target pair. A comparison connection uses its previous newer recording and target; a collection-plan connection uses its selected source recording and target. These ordinary saved pair reflections remain separate from the immutable goal worked on and the originating collection plan. The student deliberately keeps the worked-on goal or writes a changed next goal; saving does not update the source collection plan or rewrite a connection.
The dedicated save verifies the active owned connection, exact recording pair and saved version, current goal-choice request and optimistic reflection revision together. Keep derives the goal from the immutable connection rather than trusting supplied replacement text. Update requires the student’s changed next-goal text. Each connection keeps a private after_reflection_id marker so a late new structured save cannot silently recreate a hard-deleted pair reflection. Markers are owner-only continuity metadata and do not enter public connection projections or existing collection fingerprints.
New connected-reflection shares store a private opaque selection hash for exact retry checks and use voice-share-connected-reflection-v1 with independent choices for reflection text, next-goal text, worked-on context and zero to two recordings from this exact pair. Worked-on context requires the target audio selection. Reflection-only and next-goal-only choices do not authorize audio. The shared reflection snapshot leaves unselected body or goal fields empty; its context contains only the authored question. Optional worked-on context uses the appropriate existing comparison or collection-plan attachment with the selected target. Exact pair, connection, snapshot revision, recipient, choice masks and consent are checked before sharing. Earlier sharing grants never gain this content automatically.
The accepted public result includes only the masked reflection and next-goal text, selected audio and any explicitly selected worked-on goal/feedback context. Private connection markers, source-plan and reflection identifiers, unrelated recordings, other comments, editable account resources and response author identity fields are excluded. The student’s private pair reflection can contain more than its shared snapshot. A later private edit does not change that snapshot. Progress-collection entries retain their existing shapes; new after-attempt reflection text is never added to a bulk timeline selection implicitly.
The pair reflection and next goal are first-class approved student work. Removing a source plan or old practice connection leaves them in place. Deleting that reflection or either paired recording removes its active shared reflection snapshots and responses; selected audio or separately approved worked-on context follow their own controls. Connection markers remain private after reflection deletion to reject a stale structured creation. Revocation ends future recipient reads and received account-export access while the student retains private work. Previously kept copies and earlier provider backups cannot be recalled.
Owner account-detail JSON can include the private connection markers and complete owned pair reflections. Received JSON includes only the currently accepted masked reflection fields and optional correctly consented selected-target context, without marker or private source IDs. Complete backups retain both nullable marker columns and their values after a referenced reflection is removed, plus the private share-selection hash; no new tables are added. The selection hash is not exposed in recipient responses or account-detail JSON. Existing complete 42-table backup, migration histories, query/value limits and trigger restore checks remain. These features use no AI, speech analysis, scoring, email or automatic sharing.
Integrated connected-attempt comparison
The comparison view reads the exact owned earlier reference and connected target together. It anchors a comparison connection to its newer reference and target, or a collection-plan connection to its chosen source recording and target. Canonical authored context and chronological pair checks reject unrelated or replaced metadata. Opening or playing the comparison does not write a reflection, change a goal or choose sharing.
The worked-on feedback shown with the pair is only the immutable response already selected for that connection. Other private comments and replies to later shared reflection versions are not assembled into a new worked-on context. A student may type a reflection about how they used the feedback; the prompt does not prefill, transcribe, analyze, score or copy a response into the student’s words. The comparison creates no new stored resource, table, provider call or recording permission.
Private pair reflections and next-goal saves, optimistic revision and marker checks, five explicit sharing masks, exact recipient review and revocation continue under their existing controls. Received account exports remain limited to the selected snapshot and audio/context grant; private markers, source identifiers, unselected words and other authors’ responses stay excluded. Closing, account changes, backgrounding, printing and page exit clear derived comparison content and playback, and late callbacks cannot restore an old private view.
Whole-comparison feedback and private pair goals
Whole-comparison feedback uses a separate action for an accepted voice-share-connected-reflection-v1 selection containing exactly two current recordings that form a supported chronological question/turn pair. Ordinary audio shares, singleton selections, reflection-only shares and progress collections do not gain this action. Public proof uses only selected recordings and masked reflection or worked-on context; it does not expose private source IDs, connection markers, author identity from another feedback context or unselected words.
The existing bounded share-owned feedback table stores the comment, an opaque fingerprint and a reviewed count of two, without copying a goal, private reflection or deleted source context. Recipient read, create, retry and removal require their accepted active exact-pair grant. Author deletion and student removal clear comment words and keep the retry ID as a tombstone, preventing removed comments from being recreated by a stale request. The student retains active received comments after revocation or partial/all selected-audio loss; a missing current pair yields no current fingerprint or goal editor. Comments report context changes instead of recreating removed content.
The student’s private next-goal editor reuses the exact pair’s existing reflection record and revision checks. It preserves the saved reflection text and saves a new goal only after an explicit student action; no support response, worked-on goal or source collection plan is automatically changed or copied. Recipients receive no private goal editor, private reflection record or private goal count. Account JSON has distinct whole-comparison comment keys: the student’s retained active received comments and the recipient’s own comments only while the dedicated comparison remains accepted, active and intact. Internal pair-proof columns are removed before export. Full private database backup preserves all application and migration-history rows, including cleared retry tombstones.
Responses to shared attempt reflections and next goals
The existing reflection-response controls also apply to connected-attempt selections, including reflection-only and next-goal-only snapshots. A response belongs to its exact immutable selected snapshot and originating acceptance, never the student’s full private pair reflection. The server checks the current selected snapshot text, version, context and creation time together with active acceptance and the verified recipient account when adding or retrying a response. There is no broader support-team permission.
The student can review received responses alongside each selected snapshot and its version, including revoked selections. A recipient can read, export or remove only their own responses while originating acceptance is active and bound to their account. Unselected reflection or goal words remain empty in that shared context. A later private goal edit does not expand the old snapshot or move its responses onto the new text. Reading feedback or choosing a planning action does not update the private goal, save, score, record, share or send anything automatically.
Source-plan or old-connection removal leaves the separately approved pair reflection, its shared snapshots and received responses in place. Deleting that reflection or either paired recording removes its snapshots and responses under the existing foreign keys. The student may remove a received response. Revocation ends future recipient reads, writes, removals and authored-response export access; the student’s received copy stays with its original selected context until removed. Copies already kept and earlier provider backups cannot be recalled.
Account-detail JSON follows these same boundaries: complete owned received-response context, or only an author’s currently accepted active response and exact masked snapshot. Private markers, source IDs and unselected private words are excluded from recipient exports. Full backup and restore preserves the existing response rows and deletion relations; no new table, schema column, recording permission or provider integration is required.
New comparison-based practice connections require the target recording to be strictly later than the current saved reflection update and any chosen response. Exact source, goal, response and target timestamps are guarded atomically so intervening edits or replacements cannot reuse an earlier recording as new practice. Existing immutable connections and their exact retries retain their original approved goal and response. The student’s ordinary private goal controls remain separate from feedback.
Career work you control
The free career tools, career explorer, education and training search, workplace scenarios and facilitation tools can be used without signing in. Your entries and opened files start in the page’s temporary memory. There is no automatic saving, browser-storage backup or sharing. These tools do not send your work to AI. Optional interview and workplace voice practice ask for microphone permission only after you choose Record my answer or Record my reply. Other career activities do not record your voice or request microphone access.
Download or print before leaving to keep a local copy. Optional read-aloud uses a local English browser voice when available. Work photos stay in the open page; they are excluded from account drafts, shared account snapshots and JSON downloads. A printed visual résumé can include your selected photos.
When you save to an account
Choosing Save to account sends that tool’s completed draft to Transit’s private database: résumé and contact fields, interview answers, added opportunities and next-step notes; career-interest answers and kept careers; selected education options and comparison notes; or facilitation session, employer and added-action notes. Search settings and print choices in the draft are included. Unfinished opportunity and action forms are excluded. Review the signed-in email before saving.
Transit stores the draft title, tool type, content, internal account ID, revision and creation/update times. Saved drafts are private to that account. Saving does not share with an existing checklist team or paid-workspace team. A professional has no automatic access to a student’s drafts. You may reopen, update or delete your drafts; stale saves are rejected so another version is not silently overwritten.
When you choose to share
Every sharing section starts unchecked. Choose a recipient email and only the sections you want to include, review the snapshot and confirm. Contact details and support notes have separate choices. Transit stores the selected snapshot, selection choices, recipient email, sender account ID, source revision, consent version and sharing times/status. Shared snapshots are read-only and do not update when your private draft changes.
The recipient must sign in with the matching verified email and deliberately accept. Pending requests show the tool type and time, not your private title or draft. Acceptance binds access to that verified account ID. Sharing sends no email, notification or employer referral. Tell your chosen person to check Shared with me in My Transit.
You can revoke a share at any time. Revocation prevents further opening through Transit; deleting the source draft revokes its shares too. Copies a recipient has already viewed, downloaded, printed or captured cannot be recalled. A shared snapshot does not grant access to other drafts, checklist records, billing or paid professional tools.
Files and deletion
Downloaded JSON files contain the complete entered draft for their tool, including sections not selected for a printed summary or account share. Keep them private and open each file in its corresponding tool. Re-add photos after opening a draft. Your device, browser, printer and backup services handle copies under their own settings.
Saved career drafts remain while Transit operates until you delete them or request removal. Deletion removes the active draft and its sharing records; provider backups, security records and copies outside Transit may remain under their retention practices. Contact Transit support for account export, correction or removal. Clearing the open page does not delete an account draft or a downloaded file.
Hosting and sign-in
Cloudflare provides the migrated website and private database. Supabase provides email-code authentication, and Resend delivers the requested sign-in email. These services process account email, authentication and technical connection information for those purposes. An existing account connection preserves its original Transit ID only after you verify both sign-ins and explicitly approve it. Email similarity alone never merges accounts.
Page visits still involve connection information such as IP addresses and request times. Transit’s application has no advertising pixels or career-entry analytics. Providers may retain service and security records under their own practices. Following an external school, employer or search link takes you to that service’s privacy practices.
Record only what you are authorized to use
Your own ordinary résumé, interview, interest and job-search information, and authorized nonconfidential facilitation notes made with the student’s involvement, are permitted. Leave confidential school or student records, IEPs, diagnoses, medical records, confidential employer information and another person’s private information out. The separate professional workspace retains its own account access and data-use limits.
Saved professional tools use generic details
The account-based professional tools remain limited to fictional or generic placements. Do not enter student names, identifying records, diagnoses, IEPs, medical information or confidential employer information in those tools. Transit is not a student-record system. The account storage, AI, reporting and retention descriptions below apply to the professional workspace, not to the local career-tool material described above.
What the service handles
| Information | How it is used |
|---|---|
| Team invitations and permissions | Transit stores the invited email, role, assigned checklist, signed-in account ID after acceptance, invitation expiry, and acceptance, approval and revocation times. The account owner and assigned worker can review access changes. Invitation secrets are stored as hashes. Removing access blocks future shared access and unsubmitted emails to removed recipients; it does not recall delivered emails. |
| Sign-in information | Transit’s verified email sign-in provides the account identity and verified email used to recognize your account and control access. Existing linked account IDs remain in place. |
| Saved plans | When you choose Save, Transit stores the plan name, placement fields, edited packet documents, ownership and revision information. Saving is explicit; unsaved work can be lost when the page closes. |
| Worker checklists and reports | Transit stores the creator’s account ID, worker label, workplace, task list, boss and coordinator emails, time zone, daily checkbox progress, notes, completion time and email submission status. Progress saves as the worker checks tasks. Private links use a secret token; only its hash is stored. |
| Access and payment records | Transit stores order references, payment and refund status, the offer version, access dates, and your welcome choices and acknowledgments. Stripe collects and processes card details; Transit does not store your full card number. |
| AI usage | Transit records attempt time, model, result status, duration and token counts when available to enforce limits and investigate failures. It does not store the AI prompt or response in that usage record. |
| Early-access signup | Your email, optional role, signup time, consent version and a removal-token hash are saved to manage the list. A daily network-derived hash limits repeated signups. |
| Support and service records | Your messages and ordinary connection or error information help us answer requests, maintain the service and investigate problems. Hosting and sign-in providers may process their own technical logs. |
What happens when you ask AI for help
AI is optional. If you request a draft, Transit sends the workplace, role, schedule, tasks, goal, measurement criteria, supports, safety context and AI notes you supplied to OpenAI’s API. The dedicated learner-label and help-contact fields are excluded, but identifying information typed elsewhere is not automatically removed.
We request that generated responses not be stored as retrievable API responses. That is not a zero-retention guarantee: OpenAI’s default safety logs may retain prompts and responses for up to 30 days, and longer in specified legal or safety circumstances; other technical processing can apply. Read OpenAI’s API data controls for details.
Suggestions stay on your page until you choose what to apply. If you then save the plan, the applied text becomes part of that saved plan. AI notes and unapplied suggestions are not part of the saved plan.
Transportation and continuation plans
Transit stores the plan name, fields, owner, revision and save times. Transportation plans can also store a link to a checklist you own. Plans are private to the account unless you explicitly share a ride plan with a worker checklist. Private-link checklists allow anyone with the link to read it. Signed-in checklists limit shared rides to the assigned worker and approved coordinators and coaches; employers do not receive ride-plan access. These plan fields are not sent to AI, ride providers or email recipients.
Unshare a ride plan by choosing “Keep in my account only” and saving. Delete a saved plan to remove it from the active database; printed copies, hosting backups and logs may remain. Deleting a checklist removes its connection to a ride plan; the private saved plan stays in your account until you delete it.
Daily email reports
When connected, Resend receives the sender and recipient addresses and the completion report to send email. The report includes the worker label, workplace, work date, completion time, checked tasks and optional note. The account owner or an approved coordinator chooses the recipients. On signed-in checklists, the recipients must be the owner or approved team members. Changes to team addresses apply to future completions; confirmed reports retain their original recipients. Email sending does not use the AI drafting service. Transit stores delivery-event identifiers and status so your team can see delays or failures. A delivery event confirms reporting from a recipient mail server, not that someone read the message. Minimal recipient suppression records may be kept after a bounce or complaint to prevent further sending; contact support about correction or removal.
Anyone with a private worker link can see that checklist and its team addresses and submit work under its label. The link does not verify the person’s identity. Share it carefully and replace or pause it if needed. Recipients may retain or forward the email independently of Transit.
Who helps provide Transit
Cloudflare provides the migrated website and database. Supabase provides email-code sign-in and Resend delivers requested sign-in emails. The original OpenAI Sites account connection is used only when you deliberately connect existing Transit work. OpenAI provides optional API drafting in the separate professional workspace. Stripe processes checkout, payment and refund information. These services handle information for their roles under their applicable terms and privacy practices.
The Transit operator can access service records when needed to operate Transit or respond to a request. Transit does not sell your saved plans or use them for advertising. The application does not include advertising pixels. Hosting, sign-in and payment services may use cookies or similar technology needed for their services.
Keeping and removing information
Saved plans stay in your account while the service operates until you delete them or request removal. They are not automatically deleted when the 60-day access period ends. Deleting a plan removes it from the active application database; downloaded or printed copies remain wherever you saved or shared them.
Checklists and daily records remain until the purchaser deletes the checklist or requests removal. Deleting a checklist removes its daily records, team invitations, memberships and access-change history from the active database and disables its link; it cannot recall emailed reports. Sending-service logs follow that provider’s retention practices.
Early-access records remain until you use the removal link provided at signup or request removal. Daily signup-limit records are cleared on a later signup after their day has passed. Payment, acknowledgment, access and operational records may remain as needed for transaction records, dispute handling, security or applicable obligations. Provider backups and logs follow the provider’s retention practices; we do not promise immediate erasure from every backup.
For account information, a correction, a copy or a removal request, email support@transitforwork.com. We may ask you to verify account ownership. We will explain any information that must be retained and why. Removing Transit data does not delete your separate sign-in-provider or Stripe account.
Your choices
- Build manually without requesting AI
- Review and edit suggestions before applying them
- Save only the fictional or generic plans you want to keep
- Download your account data from My Transit, delete saved work in its tools, and keep your own copies
- Leave the early-access list using your removal link
Contact and updates
Transit is an independent service operated by Chris McDonald. Email support@transitforwork.com with a privacy question or concern. Material changes to how Transit uses information will be described here before they apply; changes that require a new choice will not be treated as automatic consent.
