Privacy Policy
Effective and last updated: 26 October 2026
Locus helps teachers annotate documents, record lessons and save them to their own Google Drive. This policy explains what information Locus handles and the choices you have.
Locus is operated by Dennis Chia in Singapore. For privacy questions or requests, contact Locus support.
1. Information we access and why
- Locus sign-in. When you sign in with Google or Apple, Locus verifies the provider's identity token and stores a provider-specific account identifier and verified email address, which may be an Apple private relay address. An essential, HttpOnly cookie keeps you signed in for up to seven days; its server session expires automatically or is removed when you sign out. One-time sign-in challenges expire after ten minutes. Signing in does not grant Google Drive access: you connect Drive separately. Apple and Google identities are not automatically merged by email. Existing Pro access remains associated with the Google Drive account used for subscription checkout.
- Native sign-in SDK information. The iOS app uses Google's Sign-In SDK. Google may process account/profile information, a user identifier and IP-derived approximate location for authentication and fraud prevention, plus device and usage information described in its SDK privacy disclosures. Locus does not request device location or an advertising identifier. Its account server stores only the verified email and provider-specific identifier described above, not Google profile phone numbers.
- Google account and Drive information. When you connect Google Drive, Locus accesses your email address, a Google account identifier, storage quota and metadata for files it is allowed to access. We use these to display your connection, identify your Locus account, check space, open teaching materials, save recordings and manage your lesson library and sharing.
- Teaching materials and recordings. Documents, page titles, annotations, selected screen content, microphone audio and an optional camera image are processed in your browser to create your lesson. Microphone, camera and screen capture are subject to browser permissions. Screen capture starts only after you choose a source; it may include notifications visible in that source.
- Playlists and watching progress. Playlist titles and recording IDs are stored with the creator’s verified Drive account. A shared playlist shows only recordings whose own Locus links and public Drive access are enabled. Shared videos stream directly from Google Drive; Locus does not relay or retain a server video copy. Public viewing pages send only the Locus site origin as their referrer, not the private link path. Guests’ last playback positions stay in this browser. Signed-in viewers can enable private progress sync to their Locus account; creators do not receive individual viewing history. Progress records contain recording IDs, positions, durations, completion and save times, not transcripts, video or lesson titles.
- Content reports and blocking. Shared lesson pages let you report inappropriate content to the Locus owner without giving your name or email. Reports contain the shared link, lesson title, creator and video identifiers, selected reason and any details you choose to write. Do not include private student information. Reports expire after 180 days. An hourly keyed network hash limits spam; raw IP addresses are not saved in the report store. Creator blocks stay in this browser; when signed in they also stay with your Locus account for up to 180 days. Account deletion removes those synced viewer blocks. Safety restrictions on public sharing and up to 1,000 moderation decisions may be retained to prevent repeated abuse. These controls apply to Locus links, not direct Google Drive links or private files.
- Optional creator analytics. On shared Locus viewing pages, you can choose “Share viewing statistics with the creator”. This is off until you choose it, separate from sign-in and Continue watching. Locus then collects active, visible playback time, approximate timeline coverage and playlist completion. A random browser identifier lasts up to 90 days; the server hashes it separately for each creator to estimate audiences. Different devices or cleared browser storage can count separately. Analytics requests omit account cookies and contain no name, email, IP address, filename, transcript, video or private resume record. Infrastructure providers still process connection information to serve requests as described below.
- Creators see aggregate plays, estimated viewers, watch time, completion, daily counts and engagement by video section. They cannot inspect individual analytics sessions or identify which student watched. Pseudonymous technical sessions used for deduplication expire after 24 hours. Aggregates expire after 90 days without activity; daily charts cover the latest 30 days. Switching the analytics choice off stops new collection but does not remove already aggregated totals. Direct Drive playback, the embedded Drive fallback and downloaded copies are outside Locus’s analytics. Counts are estimates, not evidence of attendance or attention.
- Private account administration. The Locus owner can see verified account emails and provider identifiers, first and last activity, sign-in counts, completed recording counts and duration, successful summary counts and subscription status. Recording reports contain no titles, documents, audio, video or transcript. This helps operate the service and provide support. The owner can grant Pro or restrict an account to Free; these access changes do not cancel a Stripe or Apple subscription. The latest 1,000 access changes and their reasons are retained for accountability. Account records and cumulative operational totals remain until deletion is requested or the service no longer needs them; daily operational counters expire after 90 days. The owner also sees app-wide totals from the separately opt-in viewing statistics above, without individual viewer identities or private watching history.
- Captions and summaries. Locus handles live or imported captions and summaries when you use those features. Captions and private summaries can be saved on your device and as separate files alongside the video in Drive.
- Subscription information. We use your Google-linked Locus identifier, Stripe customer and subscription identifiers, subscription status, billing-period dates and summary usage counts to provide Pro access and enforce your allowance. Your email is sent to Stripe when a billing customer is created. Payment details are entered into Stripe; Locus does not receive or store your full payment-card number. Apple in-app subscriptions use Apple and RevenueCat. RevenueCat receives a random Locus billing identifier and purchase/renewal information to validate access. We do not send RevenueCat your email, Google tokens, recordings, lesson files or transcripts. The same Google Drive account keeps the subscription and summary allowance consistent across devices. Apple and Google sign-in identities are not automatically merged.
- Service information. Hosting and service providers may process IP addresses, request times, requested URLs and technical error information to deliver and secure the service. Locus does not add advertising trackers or sell personal information. Application logs are not intended to contain recordings, transcripts, document text, file names or access tokens.
Contacting support
When you contact support, we store the reply email address, topic, subject, message, reference number, conversation replies and request status in a private owner-only inbox. Requests expire after 180 days without activity. No recordings, transcripts, lesson files or device logs are automatically attached. Please do not include passwords, card details or student information.
When support email is enabled, Resend processes incoming messages and outgoing replies, including sender and recipient addresses and message contents. Resend may process this information outside Singapore. Its email and event retention is normally 30 days. Email attachments and HTML are not imported into the Locus inbox. When owner notifications are enabled, basic request metadata (subject, topic, source and reference number) may be emailed to the Locus owner. The full message and contact address remain in the private support inbox. We use short-lived, keyed network hashes and request counters to limit spam; raw IP addresses are not saved in the support database. Contact email addresses supplied in the form are not treated as proof of account ownership.
2. Google permissions and Limited Use
Locus requests the drive.file permission: access to files you select for
Locus or files Locus creates. It does not request access to all files in your Drive, your
Gmail or your contacts. Google Docs and Slides open as PDFs. Word and PowerPoint
conversion creates a copy in your Drive’s Locus › Sources folder; the original is not
edited.
Google access tokens are held temporarily in the browser and sent over HTTPS when needed to authenticate Locus server requests. Locus’s backend does not persist Google access or refresh tokens. We do not ask for your Google password.
Locus’s use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. We use Google data to provide the features you request, not for advertising, sale, credit decisions or training general-purpose AI models. Human access is limited to your explicit permission, necessary security investigation or legal requirements permitted by that policy.
You can disconnect in Locus and revoke access in your Google Account’s third-party connections. Revocation stops future authorised access; it does not automatically delete files already saved in Drive or records held for billing and sharing.
3. Optional captions and cloud AI
Live captions are on by default in supported browsers and use your browser’s speech-recognition service. You can switch them off before recording. Depending on the browser and settings, audio may be processed by Google or Apple under their policies.
Cloud AI summaries are an optional Pro feature. Before each generation, Locus asks for your agreement to send that lesson’s transcript through Vercel AI Gateway to the provider named in the app (currently Inception, Mercury 3). The model request contains the transcript, not the video, camera feed, Google token, file name or lesson title. Personal information spoken in the transcript is still included, so remove information you are not authorised to send.
Locus does not use your lesson data to train general-purpose AI models. AI providers process requests under their applicable service and data-handling terms; we do not promise zero retention by those providers. You may record, play and share videos without generating an AI summary. Viewing a saved shared summary does not trigger a new AI request.
4. Sharing and service providers
New recordings are private by default. You may choose a Workspace-domain link or an anyone-with-the-link setting for a video. Creating a public Locus lesson link requires you to permit public link access to the Drive video. Anyone who obtains that link can view the shared lesson without buying Pro. Publishing the saved AI summary is a separate option, off by default.
Turning off summary sharing hides it from future Locus link responses but keeps your private copy and the saved server snapshot. Turning off a Locus link does not by itself remove the Drive video’s sharing permission. Making the Drive video private or moving it to Trash also blocks access through the Locus viewer. Copies already downloaded or saved by others cannot be recalled.
We use Google and Apple for the sign-in methods you choose, Google for Drive, document conversion and video delivery; Vercel for hosting, server functions and the AI Gateway; Upstash for account mappings, usage and share records; Stripe for web subscriptions; Apple and RevenueCat for in-app subscriptions; and the disclosed AI provider for requested summaries. These providers receive information needed for those services. We may also disclose information when legally required or necessary to protect the service and people from abuse.
Providers may process information outside Singapore. The Locus account database is configured in Singapore, but that does not mean all processing stays there. Where personal information is transferred overseas, we take steps required by applicable data-protection law to provide appropriate protection.
5. Storage and retention
- On your device: recording pieces and recovery metadata are stored in browser storage. Successfully uploaded, non-discarded recordings with no pending metadata are eligible for cleanup after seven days, when Locus next checks local storage. Local-only, unfinished and recently discarded copies remain until removed or browser storage is cleared. Browser or device storage loss can remove them sooner. With Time Machine enabled, the newest 30 seconds remain in memory until committed and may be lost if the tab closes.
- In your Drive: videos, converted source copies, captions and private summary files remain under your Google account until you remove them. Discarding a saved recording through Locus moves its video to Drive Trash; associated caption or summary files may need separate removal. Google’s Trash and retention rules apply.
- On Locus servers: playlist metadata remains until the creator removes it. Watching progress keeps at most 500 account entries for 180 days; this browser keeps at most 200 progress entries for 180 days. Turning sync off stops further progress uploads but does not erase already saved account progress. Account-to-billing mappings and published share records currently have no automatic expiry. Summary allowance records and cached generation results expire seven days after the relevant billing period ends. Disabling a share link hides it; it does not erase its stored record. Use Delete account in the signed-in workspace to remove your Locus account, synced progress, playlists, Locus share links and shared summaries. This also removes Locus cloud content associated with the linked Drive account and signs out linked Locus sessions. Files in Google Drive and recordings kept only on this device are independent copies and are not erased by account deletion.
- Billing, support and security: relevant records may be retained for legitimate operational, accounting, dispute-resolution or legal obligations. Provider backups and records follow their own retention processes. After account deletion, minimal billing identifiers, subscription records and allowance counters remain for payment reconciliation and fraud prevention; de-identified operational totals may remain. Security deletion timestamps prevent old sessions from restoring a deleted account. A fresh sign-in can create a new account without resetting a paid period's summary allowance.
We keep information only while needed for the purposes described here or legitimate legal and business requirements, and remove or anonymise it when those purposes no longer apply.
6. Your control, requests and security
You can download recordings, manage Drive files, change sharing, turn captions off, decline AI processing, cancel a subscription and revoke Google access. Before clearing browser storage, download any local-only lessons you want to keep. Disconnecting Google does not cancel a subscription; use Manage subscription in the Pro tab or Apple’s subscription settings for an Apple purchase.
To delete your account, sign in, choose Delete account beside Sign out, type DELETE and confirm the same Google or Apple identity. For Apple sign-in, Locus exchanges a fresh authorization code and revokes the authorization with Apple; these provider tokens are not stored. If another Apple identity was previously linked through the same Drive account, its Locus data and sessions are removed too; remove that separate grant manually in your Apple account’s Sign in with Apple settings. Deletion does not cancel a subscription. Cancel in the Pro tab or Apple subscription settings first if you want billing to stop. Download or remove your local recordings in On this device, and manage Drive files separately.
For access, correction, withdrawal of consent, deletion requests or privacy complaints, contact Locus support with the subject “Locus privacy”. We may verify your identity and explain any records we must retain or feature limitations caused by withdrawal. Do not send passwords, access tokens or full payment-card details.
We use HTTPS, restricted service credentials and owner checks for private account actions. No system can guarantee absolute security or uninterrupted recovery. Locus is designed for teacher-managed use; teachers must have the authority and any required consent to record or upload other people’s information, particularly students’ information.
7. Changes to this policy
We will update the date on this page when the policy changes. Material changes to how we use your data will be communicated in the app or through an appropriate contact channel. If a new use requires your consent, we will ask before using your information for that purpose.