Skip to content
OOctopus Life AI
  • About us
  • Octopus
  • Features
    • Services & bookings
    • Marketplace products
    • Messages & calls
    • Clubs & events
    • Calendar & availability
    • Location & tracking
    • Stores & branches
    • Octopus AI Beta
  • How it works
  • Trust & Safety
  • Help & FAQ
  • Contact
Get in touch

Last updated October 17, 2026 · Octopus Life AI

Privacy Policy

This policy explains how Octopus Life AI ("we," "us") handles information when you use Octopus and this company website. It covers marketplace and booking features, social connections, and optional AI or connected-email features where available. Features depend on your app build, account, permissions, and region.

1. Who we are 2. Google and connected-account data 3. Limits on Google data use 4. Optional email and AI features 5. Sharing and service providers 6. Storage and security 7. Retention and deletion 8. Your choices and account deletion 9. Other Octopus data and permissions 10. Children's privacy 11. Changes to this policy 12. Contact us

1. Who we are

Octopus Life AI develops Octopus, a platform for services, marketplace products, bookings, payments, messaging, clubs, and events. We handle information to provide these features, authenticate users, communicate about activity and requests, operate and troubleshoot the service, and protect users against abuse and fraud. Contact octopus@octopuslife.ai about support, privacy, or this policy.

2. Google and connected-account data

Connecting a mailbox is optional and separate from using Google to sign in. Where Gmail features are available, the mailbox connection requests:

  • Your Google account email address (openid, email) — to identify the connected mailbox.
  • Read access to Gmail (gmail.readonly) — to retrieve recent message details and relevant content for the enabled assistant features described below.
  • Permission to send Gmail messages (gmail.send) — to send a message or reply through the approval process. Connecting a mailbox alone does not approve a particular message.

These Gmail permissions do not let Octopus move or delete your messages, create labels, or edit Gmail drafts. Drafts prepared by Octopus are stored in Octopus. Where Microsoft email connections are available, we request account identity, continued access, and Microsoft Mail.Read and Mail.Send permissions for the same supported email purposes.

Google sign-in can supply your account identifier, email address, name, and profile photo for authentication and your Octopus profile. Connected-mail processing can retrieve sender and recipient addresses, subject, preview text, timestamps, message identifiers, and relevant message bodies. It can generate summaries, proposed replies, follow-ups, and observed-correspondent records.

Octopus Life AI's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

3. Limits on Google data use

  • We do not sell or rent Google user data or derived information. Necessary processing by service providers is described in section 5.
  • We do not provide it to data brokers or advertising networks for their own use.
  • We do not use Google user data for advertising, including personalized or interest-based ads.
  • We do not use Google user data to develop, improve, or train generalized AI models.
  • We do not use it to assess creditworthiness or make lending decisions.
  • Mailbox synchronization uses bounded recent-message windows rather than importing your entire historical mailbox. Relevant message content can also be retrieved for an enabled feature or your request.

These limits also apply to information derived from Google data. Human access to Google-derived content is limited to the cases permitted by Google's Limited Use rules: your affirmative agreement for specific content, necessary security investigations, legal requirements, or permitted internal operations using aggregated and anonymized information.

4. Optional email and AI features

When available, and after you connect a mailbox and grant the relevant permissions, email features may process recent messages in the background to:

  • Organize and summarize recent email, identify relevant commitments or follow-ups, and record observed correspondents to support your assistant experience.
  • Prepare a message or reply for your review and send it after the required approval and permission checks.

Connecting email does not authorize automatic sending. Proposed outgoing email goes through an approval step. Disconnecting a mailbox and revoking provider access are explained in sections 7 and 8.

When you use Octopus AI, the conversation, relevant account or booking information, and information supplied for a supported task can be sent to OpenAI to interpret requests and generate responses. Enabled email features can also send relevant email information for summaries, drafts, and follow-up processing. AI conversations and generated assistant records can be stored by Octopus. AI availability varies; email assistance is not included in every AI Beta build.

5. Sharing and service providers

Information is shared to provide the features you use. Your profile and published listings, posts, reviews, or community activity are visible to their permitted audiences. Messages, contact details you share, booking information, and approved location sharing reach the relevant participants. Providers and customers receive information needed for their transaction; account blocking and privacy settings affect access.

Our service providers include Stripe for payments, payouts, and identity checks; iDenfy for identity-verification routes where used; Google/Firebase for sign-in, push notifications, and crash diagnostics; Mapbox and map services for maps, routing, and navigation; DigitalOcean for hosting and file storage; and OpenAI for enabled AI processing. Google and Microsoft process connected-mail authorization and email operations. These providers receive information needed for their role. Providers acting on our behalf must protect it consistently with this policy and applicable law. Some providers also process information under their own terms and privacy policies. Processing may occur outside your country.

OpenAI's API data is not used for model training by default, but provider safety monitoring and feature-specific retention can apply. This policy does not promise zero provider retention or that no human can ever access data. Authorized personnel may access account or support information when needed for assistance, moderation, security, or legal obligations; Google-derived content remains subject to the narrower limits in section 3. We may disclose information when legally required or necessary to address fraud, abuse, or threats to safety.

6. Storage and security

We use account authentication, access controls, and encrypted stored mailbox tokens to protect information. Google and Microsoft authorize mailbox access without giving Octopus your mailbox password. Those mailbox connections are separate from Octopus sign-in; that separation is not a guarantee that failures cannot affect other features. Connections to provider APIs use HTTPS. No transmission or storage system is completely secure. Never send passwords, verification codes, full payment-card details, or identity documents to our support email; use the relevant in-app or provider verification flow.

7. Retention and deletion

Account information, listings, messages, uploads, bookings, preferences, and assistant records are retained to provide the features you use until removed through the relevant feature or account-deletion process, subject to the exceptions below. Records have different lifecycles; there is no single 30-day deletion rule for all Octopus data.

The local email message index is scheduled for nightly cleanup of entries older than 30 days. This index contains message metadata and preview text rather than a full-body mailbox archive. Cleanup runs in batches and can be delayed by failures or backlog. Generated drafts, insights, observed correspondents, follow-ups, and AI conversation records have separate lifecycles and are not all erased by that index cleanup.

Disconnecting a mailbox stops its Octopus connection, removes its local message index, clears stored credentials, and retires associated follow-ups. Some shared email-derived records are cleaned up only after no active mailbox remains; observed-correspondent records are handled separately. Cleanup can require retries. Contact octopus@octopuslife.ai to request deletion of retained email or assistant data without waiting for scheduled cleanup.

After account deletion, records of bookings, transactions, payments, refunds, disputes, identity-verification outcomes, and security or deletion actions may remain for reconciliation, fraud prevention, and legal obligations. Unrelated personal details are removed after acceptance. Only the information needed for an unresolved obligation or permitted retention remains; the request stays pending until required cleanup is complete. Account references and payment-provider identifiers may remain to preserve transaction integrity. Existing account restrictions can retain protected identifiers to prevent repeat abuse.

The current deletion process has no fixed automatic expiry for all retained financial, booking, and restriction records. Their retention is separate from the email index's 30-day cleanup. Deletion-verification access lasts 10 minutes; an accepted request can be checked while pending and for 30 days after completion. The encrypted notification address is retained for up to 30 days after acceptance, or cleared after completion notification. Unresolved provider cleanup may retain the information needed to finish it. Contact us about a particular retained record or deletion request.

8. Your choices and account deletion

You can change available profile and sharing settings and manage phone permissions in your device settings. Where mailbox features are available, disconnect the mailbox to stop its connection and initiate the cleanup described above. You can also revoke access in your Google Account at myaccount.google.com/permissions. Provider revocation stops further authorized provider access but does not itself delete information already held by Octopus. Use disconnect, account deletion, or a privacy request for that information. Contact us to request access, a copy, correction, deletion, or withdrawal of consent, subject to applicable rights and retention obligations. We may need to verify your identity.

Delete your Octopus account

Use Settings → Delete account in Octopus or start account deletion on the web. Verify your identity, review the impact, review any retained obligations, and explicitly confirm permanent deletion. Restricted or banned accounts can verify for deletion without receiving ordinary account access. Email-code recovery is available for supported accounts. A missing Apple revocation credential does not prevent verified account deletion; we explain how to remove any remaining Apple connection.

Your personal profile, personal posts, comments, reviews, messages, files, services, marketplace products, and AI/email records are removed during cleanup, subject to the retention exceptions in section 7. Other participants' messages remain and identify you as Deleted account. Content and shared assets belonging to a surviving club, event, or transferred store can remain with private attribution removed. Eligible club/event administrators inherit ownership; otherwise the club or event is removed. Ordinary groups pass to the longest-standing eligible member.

Deletion removes your personal posts, comments, reviews, messages and uploads, including personal contributions in club or event feeds. Removing your post or comment also removes its dependent reply thread. Official posts published as a surviving club remain with the club, with private creator attribution removed. Other members’ independent content remains.

Deletion can be accepted while bookings, orders, payments, disputes, or store obligations remain. Unrelated personal data starts to be removed while only the necessary settlement records remain. Eligible bookings that have not started are cancelled using the normal cancellation and refund rules; started work and unresolved financial obligations still need settlement. Owned stores are not transferred without an accepted transfer. Requests remain pending until required settlement and provider cleanup finish. Once accepted, the account is disabled and deletion cannot be undone. Cleanup starts after acceptance and may require retries; the target for ordinary cleanup is 30 days, but necessary settlement, legal retention, and provider failures can take longer. Keep your private status link and check progress; pending status is not confirmation of completion. Acceptance and completion emails are attempted while the notification address remains available. Device calendar copies or copies retained by other people or services may need separate removal. Contact octopus@octopuslife.ai for deletion assistance or retained-record questions.

9. Other Octopus data and permissions

Accounts and profiles. We collect sign-in identifiers, authentication information, names, contact details, profile photos, handles, language, interests, preferences, and saved addresses or service areas that you supply. Session information can include IP address, device, operating system, and browser details to authenticate access and protect accounts.

Marketplace, bookings, and social activity. We process service and product listings, requests, schedules, booking details, prices, orders, payment status, reviews, favourites, posts, comments, memberships, invitations, and RSVPs to run the marketplace and community features. Published content is visible to its audience. Messages and uploaded images, video, audio, files, or shared contacts are processed for communication with your chosen recipients. Call features use microphone/camera data, connection information, and call history to connect participants and show call outcomes.

Location. Saved addresses, approximate areas, and device coordinates can be used for discovery, distances, navigation, service availability, and the location-sharing features you enable. Precise live location can reach permitted map viewers, chat participants, or booking participants according to your choices, consent, and access rules. Approved live sharing or provider availability can continue while the app is in the background, subject to phone permission and platform controls. Booking tracking also depends on booking status and its tracking window; it is not automatically available the moment any booking is made.

Contacts. With permission, the app can read device contacts to help you find or invite people and share a selected contact. Relevant phone numbers can be sent to Octopus for matching; contact names and photos can be used locally for presentation. Sharing a contact sends the information you select to its recipients. Connected-email observed correspondents are a separate assistant feature described above.

Calendar. With permission and enabled synchronization, calendar access helps avoid booking conflicts and add supported bookings to a device calendar. Synchronization can send event start/end times, titles, calendar/event identifiers, timezone, and device identifiers to Octopus and can run in the background. Turning off permission or synchronization stops future access; existing exports or copies can require separate removal.

Payments and identity verification. Stripe processes payment methods and payouts. Octopus stores transaction references, amounts, currencies, funding/refund/dispute status, and provider-account references to manage bookings and accounting; it does not store full payment-card numbers or security codes. Identity-verification providers can collect identity documents, selfies, and document details. Octopus can receive verification results and extracted details such as name, birth date, document type, and issuing country for account eligibility and fraud prevention.

Notifications, diagnostics, and this website. Push delivery uses device registration tokens and relevant activity information. Firebase Crashlytics and service logs process errors, stack traces, and technical app/device information to diagnose reliability and security issues. The company website requests fonts from Google Fonts, which receives connection information such as your IP address. Contacting support supplies your email address and the information you include. Optional permissions can be denied or withdrawn; features that require them may then be unavailable.

10. Children's privacy

Octopus is not intended for children under 16. If you believe we hold information about a child who should not be using Octopus, contact octopus@octopuslife.ai so we can investigate and handle the information under applicable requirements.

11. Changes to this policy

We update the date above when this policy changes. Material changes will be communicated through the app or another appropriate channel. Where required, additional disclosure and consent must occur before a new use of personal data.

12. Contact us

Contact Octopus Life AI at octopus@octopuslife.ai for Octopus support, privacy questions, data requests, or deletion assistance. Describe the request without including passwords, verification codes, full card details, or identity documents.

octopus@octopuslife.ai
OOctopus Life AI
  • Home
  • About us
  • Octopus
  • Features
  • How it works
  • Trust & Safety
  • Help & FAQ
  • Contact
  • Privacy Policy
  • Delete account

© 2026 Octopus Life AI. All rights reserved.