Privacy Notice
Version 2026-11-05
Data Studio Privacy Notice
Effective November 5, 2026
1. Who is responsible
Vanteloq Inc., Alberta, Canada, operates standalone Data Studio. The Privacy Officer can be reached at hussienissa@vanteloq.com. This notice covers Data Studio, not the separate Vanteloq or BookLoQ services. Alberta's Personal Information Protection Act generally governs relevant private-sector activity in Alberta. Federal PIPEDA may apply to interprovincial or international commercial handling of personal information and other activities within its scope. Other applicable laws may also apply.
2. Information and purposes
We process account identifiers, email address, display name, provider identity and verified authentication status to identify you and protect access. Google sign-in requests basic profile and email information; it does not request Gmail, Drive or Calendar access. Email-code sign-in sends a one-time code to your account email through the configured delivery service. Passwords and authenticator verification are handled by the authentication provider. Verification codes should never be sent to support.
We process workspace names, preferences, roles, files, revisions, comments, tasks, calendars, sharing and linked-content metadata to provide the features you use. Security and operational records include session and request references, verification results, timestamps, network or device information available to service providers, and error or abuse-control events. Policy acceptance records identify the version and time accepted. We use these records for service operation, security, support and applicable obligations, not as authority to take unrelated business actions.
3. Authentication choices
Authenticator-based two-factor authentication is optional and recommended. If you enable it, new sign-ins require that extra verification until you remove it using a current code. Email verification codes are a primary sign-in option, not a second factor equivalent to an authenticator. SMS is not configured. A fresh sign-in or authenticator check is required for sensitive account deletion. Existing Vanteloq and BookLoQ authentication settings are not changed by these controls.
4. Service providers and locations
Supabase processes Data Studio account identity and authentication records. Resend delivers account verification and recovery emails. Sites and its hosting infrastructure, including Cloudflare, process the application, workspace data and technical requests. Cloudflare Turnstile processes verification signals to deter abuse. Cloudflare also handles Meets call control, and LiveKit processes live media and connection information when calls are enabled. Google processes Google sign-in under its own terms. Processing may occur outside Canada, including the United States, and information may be subject to lawful access in the processing jurisdiction. Provider location and retention vary by service; we do not promise that all Data Studio information stays in Canada.
5. AI and browser features
The supported Chrome built-in AI workflow processes selected content using the browser's local model when available. It may require a model download and is not available in every environment. This does not make an unconfigured cloud AI integration active. Browser or operating-system features have their own privacy terms. Any separately configured external AI or media action must identify its processing destination before sending content. Review proposed changes before applying them.
6. Meetings and sharing
Meeting hosts see guest display names and admission status. Participants receive the media and presented content shared with them. We store invitation, approval, session, expiry and call-control information to manage access. Passcodes are not included in invitation links. Camera and microphone start off and require user action and browser permission. Recording, transcription, AI participants and guest screen sharing remain disabled. A host can mute or remove participants; other tools may still capture content. Ending a call does not automatically erase call-control records. The guest meeting notice provides more detail.
7. Cookies and local storage
Essential secure cookies maintain account sessions, verification journeys and guest admission. Browser storage also supports interface preferences, temporary edits and offline features. Optional offline workspaces are encrypted using a separate passphrase and stored on the device when you choose to prepare them. Such copies are not remotely erased by account deletion. Open Offline workspace to unlock and remove them. Unsynchronized local changes may be lost if you clear browser data. We do not introduce advertising trackers through these account settings. Any optional analytics or marketing tracking must be disclosed with appropriate choices before activation.
8. Retention and deletion
Workspace content is kept while needed to provide your workspace or until it is deleted through available controls. File trash and version history are different from permanent account deletion. Self-service account deletion removes your identity at the authentication provider, Data Studio identity binding, local account sessions and credential slots, personal policy records, and memberships. For a sole-member owner, it also removes the workspace and its files, revisions, tasks, folders and meeting records held in the workspace database. A shared workspace owner's request is blocked until shared access is resolved. Content belonging to other workspace owners is retained for that workspace.
A minimal processing record remains while deletion is unfinished so the operation can be retried. It is removed after successful completion and technical cleanup. We may retain necessary security, fraud, provider call-control or legally required records for their applicable purpose. Provider logs and backups follow their own managed retention cycles and are not guaranteed to be erased immediately. There is no fixed automatic erasure promise for unresolved call-control records. Contact the Privacy Officer to request review of remaining records. Downloaded files, other recipients' copies, offline copies on your devices, and records another organization controls cannot be remotely erased by this request. We do not claim that a hash is anonymous.
9. Safeguards and choices
Safeguards include HTTPS, server-side identity and permission checks, scoped workspace access, protected session credentials, request proofs, abuse controls and optional two-factor authentication. No service can guarantee absolute security. Keep your inbox, devices and offline passphrase secure. You may export supported files from each app, manage authentication in Security and privacy, sign out, remove local offline copies, or request account deletion. Declining optional two-factor authentication does not opt you into marketing or authorize unrelated processing.
10. Access, correction, withdrawal and complaints
Ask the Privacy Officer for access to or correction of personal information, information about processing outside Canada, withdrawal of consent where applicable, or review of retention and deletion. Explain your request without sending passwords, codes, identity documents or customer records in an ordinary email. We will verify identity and authority proportionately, explain any lawful limitation, and respond within applicable legal requirements. Where an organization controls your workspace content, we may direct your request to that organization. You may contact the Office of the Information and Privacy Commissioner of Alberta at oipc.ab.ca or the Office of the Privacy Commissioner of Canada at priv.gc.ca, as applicable.
11. Changes
We will identify updated notices by date and provide additional notice or seek consent when required for material changes. Prior policy versions remain available for the corresponding acceptance records.
Close this tab to return to your account form.
Back to the overview