OctoOcto™AI BOOKING ASSISTANT +

Legal information

Octo™ Privacy Notice

How Octo handles account, website, booking, payment, communications, calendar, voice and AI-related personal data.

Supplier / controller
Octo
Business address
Brighton, England
Contact
info@askocto.app
Version
1.0 — effective 21 August 2026

This notice explains when Octo acts as a controller and when it acts as a processor for a tenant business. It includes the disclosures required for Google Workspace Calendar data. See also our Terms and Conditions and Cookie Policy.

1. Who we are

Octo is established at Brighton, England (Octo, we, us or our).

For privacy questions or requests, contact info@askocto.app. We have not appointed a formal data protection officer; this address is our privacy contact.

This notice applies to askocto.app, octo.askocto.app, hosted booking pages and widgets, our communications and the Octo application and integrations (together, the Service).

2. Our different data protection roles

Octo™ as controller

We act as controller when we decide why and how to use information for our own business, including website operation, account registration, subscriptions and invoices, platform security, support, product administration and our own business communications.

Octo™ as processor

A business using Octo (a tenant) normally acts as controller for information about its clients, patients, guests, leads and staff stored in its Workspace. Octo processes that information on the tenant's instructions to provide the Service.

If you are an end customer of a tenant, the tenant's own privacy notice should explain its purposes and lawful bases. Please contact the tenant first to exercise rights concerning its records. We will assist the tenant where required.

Important for tenants. This Privacy Notice does not replace a tenant's own privacy notice, marketing consent, treatment consent or legal basis for collecting customer or health information.

3. Information we handle

CategoryExamplesTypical source
Account and identityName, email, authentication identifiers, profile, role, Workspace memberships and sign-in records.You, an account owner, authentication provider or tenant administrator.
Business and subscriptionTrading details, addresses, services, prices, availability, staff settings, plan, invoices, Stripe customer/subscription identifiers and support history.You, your administrator, Stripe and Service activity.
End User and clientName, mobile/WhatsApp number, email, address, postcode, parking/access notes, waitlist status, preferences and marketing choice.The End User, tenant staff, booking forms, messages or imported records.
Bookings and service recordsService, dates and times, location, price, deposit, status, forms, answers, consent version, customer and internal notes, recurring booking information.End Users, tenant staff and Service automation.
Health and treatmentMedical, accessibility, contraindication, intake and treatment information entered in notes or forms.End Users or tenant staff. The tenant determines why it is collected.
Voice and communicationsVoice recordings, transcripts, telephone number, email/WhatsApp content, notification content, delivery status and audit information.You, End Users, tenant staff and communications providers.
CalendarConnected account email, calendar identifier/name/time zone, encrypted connection credential, event identifiers, imported busy timing, exported booking details selected by the tenant and sync logs.Google, Apple, the tenant and booking records.
Payments and giftsPayment status and provider references; invoice details; gift buyer/recipient names, emails and messages. Raw card details are handled by Stripe, not Octo.You, End Users and Stripe.
AI interactionPrompts, chat messages, selected record context, tool requests, outputs and audio sent for transcription.You, tenant staff, configured Service data and AI providers.
Technical and securityIP-derived or hashed identifiers, browser/device details, session and push subscription information, timestamps, audit logs, rate-limit records, errors and security reports.Your device, browser, network, Service and security tools.

4. How we use information and our lawful bases

PurposeInformationLawful basis where Octo is controller
Provide accounts, trials and subscriptionsAccount, business, subscription and support information.Performance of our contract; steps requested before entering a contract.
Operate, secure and troubleshoot the ServiceTechnical, security, audit, account and relevant Customer Content.Legitimate interests in a secure, reliable service; contract; legal obligation where applicable.
Billing, accounting and legal recordsContact, subscription, invoice, payment references and correspondence.Contract and legal obligations; legitimate interests in recovering debts and managing claims.
Support and service communicationsAccount, contact, diagnostics and information you provide to support.Contract and legitimate interests in responding and improving support.
Product improvementAggregated, de-identified or limited usage and error information.Legitimate interests in improving usability, reliability and security. We do not use Google Workspace data or Customer Content to train general-purpose AI models.
Direct marketingBusiness contact details and marketing preferences.Consent where required; otherwise legitimate interests where permitted. You may opt out at any time.
Prevent fraud and enforce rightsAccount, payment, logs, communications and evidence of misuse.Legitimate interests; legal claims; legal obligations.
Comply with authoritiesInformation required by a valid legal demand.Legal obligation, public interest or legitimate interests in legal compliance.

When Octo acts as processor, the tenant determines the lawful basis. Processing is governed by our Terms and Data Processing Addendum.

Where we rely on legitimate interests, those interests include providing and securing a B2B service, preventing abuse, supporting customers, maintaining business records and improving reliability. We consider necessity and balance those interests against individual rights.

5. Special category and health information

The Service permits tenants to collect health, treatment, disability and accessibility information. This is special category data under UK and EU data protection law.

The tenant is responsible for identifying both an ordinary lawful basis and an applicable special category condition, giving suitable privacy information, collecting only what is needed, restricting access and setting retention periods. Depending on the service, a condition may involve explicit consent, healthcare provision by a professional subject to confidentiality, or another lawful ground. Octo does not choose that ground for the tenant.

Octo processes this information only to provide configured features, support the tenant and maintain security, unless law requires otherwise. Tenants must not use the Service where a regulated or certified health-record system is legally required unless Octo has expressly confirmed suitability.

6. Google Calendar data

A Workspace owner may connect a Google Calendar using Google's OAuth permission process. The current Service requests permission to read calendar information and view and edit events so that it can provide two-way booking synchronisation.

Information accessed and stored

  • Connected Google account email or calendar identifier, calendar name and time zone.
  • OAuth connection information managed through Lovable's connector gateway; Octo stores an encrypted connection key rather than the Google password.
  • External event identifiers and start/end timing needed to maintain busy blocks and prevent double booking.
  • Identifiers and sync information needed to update or remove events created from Octo bookings.
  • Google API responses and limited error/audit information needed for reliability and security.

Privacy-preserving calendar design

For personal events imported from Google, Octo stores timing only. The current implementation does not store external event titles, descriptions, attendees or locations in Octo.

For events exported from Octo, the Workspace owner chooses a detail level. The event may show only 'Busy', a service name, or a client's first name and service. The business name may appear in the description and the booking location appears only if separately enabled. Surnames, phone numbers, customer notes and treatment summaries are not intentionally exported.

How Google data is used

Google data is used only to provide and secure the visible calendar synchronisation feature, including blocking unavailable times, displaying busy periods, creating and updating booking events, reconciling changes, troubleshooting sync and honouring disconnect or deletion requests.

We do not sell Google Workspace data, use it for advertising, credit decisions or unrelated profiling, or use it to train or improve general-purpose AI models. Human access is limited to what is necessary with the user's explicit consent for support, for security investigation, or to comply with law.

Google Limited Use. Octo's use and transfer of information received from Google Workspace APIs will adhere to the Google Workspace API Services User Data and Developer Policy, including its Limited Use requirements.

Disconnecting Google

A Workspace owner can disconnect the calendar from Octo settings. Octo asks the connector gateway to revoke the connection and removes the corresponding connection record. Busy blocks and links associated through that connection are deleted under the database relationship and cleanup process. A user may also revoke access from their Google Account security settings.

7. Apple / iCloud Calendar data

Apple does not provide an equivalent public Calendar OAuth flow for this use. A Workspace owner may connect using an Apple ID and an Apple app-specific password. The password is encrypted at rest, is not displayed back to members and is used server-side only to communicate with Apple's CalDAV service.

The owner selects a calendar. Pull and push start only after selection; a read-only shared calendar remains one-way. As with Google, personal iCloud events are imported as timing-only busy blocks without titles or attendees. Outbound event detail follows the tenant's selected privacy level.

Disconnecting deletes the Octo connection record and encrypted credential. The owner should also revoke the app-specific password through Apple if it may have been compromised or is no longer needed.

8. AI, audio and transcription

Some features send prompts, selected record context or audio to an AI provider to return a visible response, transcript or proposed action. Depending on configuration, providers may include Lovable's AI gateway, OpenAI, DeepSeek or Google Gemini.

One-shot microphone transcription is not intentionally persisted as audio by that function. Saved voice notes, including WhatsApp voice notes, are stored in private tenant-scoped storage and may be transcribed through the Lovable AI gateway using an OpenAI transcription model. The transcript is then stored with the voice note.

AI providers receive only information submitted or selected for the feature. Octo does not use Customer Content to train its own general-purpose AI models. Tenants should avoid including unnecessary personal or health information in prompts and should review AI outputs before acting.

Octo does not intend to make solely automated decisions about individuals that produce legal or similarly significant effects. Tenants control workflow settings and remain responsible for lawful human oversight.

9. Payments, messages and other integrations

Stripe processes card information and payment authentication under its own privacy terms. Octo receives identifiers, amounts, status, invoice and dispute information needed to manage subscriptions, deposits, payment links and gift vouchers. Octo does not intentionally store full payment card numbers.

Email is sent through Lovable's email service. WhatsApp features may transmit telephone numbers, messages, signed audio links and transcripts through Meta/WhatsApp and the communications endpoint configured for the Workspace. Push notification subscription endpoints are handled by the relevant browser or device push service.

When a user opens mapping or route links, mapping providers may receive addresses or route information under their own privacy terms.

10. Who receives information

We disclose information only where necessary for the Service, instructed by the tenant, required by law or otherwise described below.

RecipientPurpose
Tenant and its Authorised UsersAccess to their Workspace records, bookings, clients, communications and reports under assigned roles.
LovableHosting/runtime, email, connector gateway, AI gateway, transcription and related platform services.
SupabaseDatabase, authentication, private object storage, queues and scheduled backend processing.
CloudflareNetwork delivery, runtime, availability and security functions.
StripeSubscriptions and optional tenant/end-customer payment processing.
Google and AppleConnected calendar synchronisation; Google Gemini where enabled; mapping links where used.
OpenAI and DeepSeekAI responses, tool-assisted administration and transcription where enabled.
Meta/WhatsApp and communications providersDelivery and receipt of messages and voice notes where enabled.
Professional advisers and authoritiesLegal, accounting, insurance, security, dispute and compliance purposes where necessary.
Business transfereeA genuine sale, financing or reorganisation, subject to confidentiality and appropriate data protection.

11. International processing

Octo is established in England, but some service providers operate internationally. Personal data may therefore be processed outside the UK or the country where it was collected.

Where a restricted transfer requires safeguards, we use or rely on mechanisms such as UK adequacy regulations, the UK International Data Transfer Agreement or UK Addendum, European Commission Standard Contractual Clauses, provider binding corporate rules or another lawful mechanism. We also consider supplementary security measures where appropriate.

You may request further information about relevant safeguards at info@askocto.app. Commercially sensitive provisions may be summarised or redacted.

12. Retention

We keep personal data only for as long as reasonably necessary for the stated purpose, tenant instructions, security, legal claims and applicable law. Because tenants determine retention for their client records, periods may vary.

InformationTypical retention or criteria
Account and Workspace dataFor the trial/subscription and a limited closure period to support export, recovery and deletion. Remaining active-system Customer Content is ordinarily scheduled for deletion within 90 days after closure or a verified request, subject to legal holds and operational capability.
Tenant client, booking and health recordsUntil the tenant deletes them, instructs deletion or closes the Workspace, subject to legal retention and protected backups. Tenants must set periods suitable for their sector.
Voice notes and transcriptsUntil deleted by the tenant or as part of Workspace deletion, unless needed for a dispute, security or legal requirement.
Calendar credentials and busy blocksWhile the calendar is connected and for the limited time needed to synchronise, troubleshoot and complete deletion. Connection credentials are removed on disconnect; related rows are deleted through connection cleanup.
Messages and delivery recordsFor delivery, retries, support, audit and dispute needs. Queue entries use short operational lifetimes; minimal send/error records may be retained longer for security and accountability.
Security and webhook recordsAccording to risk and operational need. Some replay records are automatically deleted after 7 days and content-security reports after 30 days; relevant incident records may be kept longer.
Billing, tax and legal recordsAt least as long as required for tax and accounting. As a UK sole trader, business records are generally retained for at least five years after the relevant 31 January tax filing deadline, and longer where a dispute or inquiry continues.
Marketing preferencesUntil consent is withdrawn or you object, plus a minimal suppression record to ensure the opt-out is honoured.
BackupsDeleted data may remain in protected backups until overwritten in the normal backup cycle and is not restored for ordinary use except disaster recovery.

13. Cookies, local storage and offline data

The Service uses cookies and similar device storage needed for authentication, security, preferences, service-worker operation and offline functionality. Offline application data may be stored in IndexedDB and is partitioned by user and Workspace, with purge controls when identity or Workspace changes.

Strictly necessary storage is used to provide a service requested by the user. If we introduce analytics, advertising or other non-essential storage requiring consent, we will provide clear information and a consent control before using it where required.

You can control cookies through your browser, but blocking necessary storage may prevent sign-in, offline use or other features. Full detail is in our Cookie Policy.

14. Security

We use technical and organisational measures proportionate to the risks, including HTTPS, tenant-scoped access controls, row-level database security, encrypted calendar credentials, private voice-note storage, signed links, role checks, webhook verification, rate limiting, cache separation, logging and provider security controls.

No online service can guarantee absolute security. Tenants and users must protect passwords and devices, assign the minimum access needed and notify us promptly of suspected compromise at info@askocto.app.

15. Your rights

Depending on applicable law and our role, you may have rights to access personal data, correct it, erase it, restrict processing, object, receive portable data and withdraw consent. You may also have rights relating to automated decisions.

Right to object. You may object at any time to processing based on legitimate interests, including direct marketing. We will stop direct marketing and will consider other objections in accordance with applicable law.

To exercise a right relating to Octo's own account, billing, website or support records, email info@askocto.app. We may verify identity and clarify the request. There is normally no fee, but the law may allow a reasonable fee or refusal for a manifestly unfounded or excessive request.

For information held in a tenant Workspace about an End User, contact the tenant first. If you contact us, we may forward the request to the tenant or ask for details needed to identify the relevant Workspace.

Where processing is based on consent, withdrawing consent does not affect processing already carried out lawfully. Some information may be retained where necessary for legal obligations, claims, security or the rights of others.

16. Complaints

Please contact info@askocto.app first so we can try to resolve a concern.

You may complain to the UK Information Commissioner's Office at ico.org.uk/make-a-complaint or to the data protection authority in your country where applicable. This does not affect other legal rights.

17. Children

Octo accounts are for adults acting in business. The Service is not directed to children. A tenant may record a service involving a child only where it has appropriate authority, gives suitable information to the parent or guardian and complies with applicable safeguarding and data protection rules.

18. Worldwide customers

This notice is centred on UK data protection law because Octo is established in England. Additional local rules may apply where a tenant offers services or monitors individuals in another country. Tenants are responsible for their local notices and lawful bases; Octo will provide reasonable assistance under the Data Processing Addendum.

Where Octo is directly subject to another law, we will apply mandatory rights and safeguards. This notice does not limit rights that cannot lawfully be limited.

19. Changes to this notice

We may update this notice to reflect changes in the Service, providers or law. We will publish the new version and effective date. We will provide reasonable notice of a material change and seek consent where required before using personal data for a materially different purpose.

20. Regulatory and policy references

Privacy contact

Email info@askocto.app or write to Octo, Brighton, England.