Tidebase SaaS Privacy Policy
Effective date: 16 November 2026.
Who we are and what this policy covers
Tidebase SaaS is a hosted operations service for dive centers and excursion operators. It supports staff workspaces, client administration, customer and booking records, equipment and boat management, quotations, invoices, reporting and guest portals. It is operated by Beu LLP ("Tidebase", "we", "us").
This policy covers Tidebase SaaS at tidebase.app, admin.tidebase.app and client domains connected to the service. It does not describe the separate original Tidebase installation or unrelated websites.
For privacy questions or requests, contact amdcreation@gmail.com.
Our role and the client's role
We manage platform accounts, service security and our business relationship with clients. Each dive center or excursion operator decides what guest and staff information it enters, who may access its workspace, and why it uses that information. We process workspace information to provide the service on that client's instructions, subject to applicable law and our agreement with the client.
If you are a guest or staff member, contact the relevant operator first about its bookings, customer records, waivers or business practices. Its own privacy notice applies to its activities. We assist clients with requests concerning information held in Tidebase SaaS.
Information we process
- Trial signup information: business name and type, contact name, email address, verification status, terms acceptance version and timestamps, and workspace setup status. We use these to confirm your request, contact you about setup and provide your trial. Verification links expire after 24 hours. Abuse-prevention records use hashed identifiers and short-lived daily counters.
- Account and client information: staff names, email addresses, roles, password hashes, workspace settings, client contact information, plan labels, subscription amounts and billing dates, manually recorded payment references, subscription change history, custom domains and domain ownership verification records.
- Partner information: guesthouse and agency contact details, commission agreements, booking referrals, payment instructions, and collection, remittance, payout, refund and adjustment records entered by the client.
- Operational information: guest names and contact details, nationality, hotel or pickup information, diving certification information, participants, bookings, quotations, invoices, amounts and recorded payment references, and notes entered by authorized users. A recorded payment may have occurred outside Tidebase.
- Guest portal information: email verification records, booking requests and changes, reminder preferences, and waiver text, version, typed signature and signing time when a client enables waivers.
- Service and security information: session and invitation records, access attempts, audit events, timestamps and technical logs. Hosting and network providers may process IP addresses and request metadata to operate and protect the service.
- Communications: information you provide when contacting us, together with transactional emails and their delivery information.
Clients should collect only information needed for their services. Do not put card security codes, account passwords or unnecessary sensitive medical or identity information in free-text notes. Any special-category or similarly protected information requires appropriate client instructions and safeguards before collection.
Google sign-in
Google sign-in is available for eligible existing staff accounts and the designated platform super admin. When you choose it, Tidebase requests the openid and email permissions. Google supplies an identity token containing identity and verification claims, including your email address and whether Google has verified it. For Google Workspace accounts, domain information may also be used to check eligibility.
We validate this information and match the verified email to an existing staff account in the relevant workspace, or to the explicitly designated super admin address on the separate client-management sign-in. We create a session with the permissions for that account. Workspace membership does not confer platform administration rights. Google sign-in does not create a new staff membership or promote a user to super admin.
Tidebase does not receive your Google password. This integration does not request access to Gmail messages, Drive files, contacts or calendars. The current sign-in flow processes the Google token to authenticate the request; it does not persist Google access or refresh tokens for ongoing access. The staff email remains part of the staff account, and Tidebase session records remain subject to our retention practices.
We use Google identity information for authentication, account access and associated security. We do not sell Google user data or use it for advertising, credit decisions or training general-purpose AI models. We share it only as necessary to operate and secure sign-in, with service providers acting for us, as required by law, or with your direction. You can review or revoke the connection in your Google Account. Revocation does not itself delete your Tidebase account or the client's business records. Contact the workspace administrator or our privacy contact to request account or data removal.
Why we use information
We use information to provide and administer workspaces and guest portals; authenticate users; apply staff permissions; manage bookings, records and documents; send sign-in codes, invitations and requested operational notices; respond to support requests; prevent abuse; investigate faults; and meet applicable obligations.
Where a law requires a lawful basis, the basis depends on the activity and our role: providing a contract, legitimate interests in operating and securing the service where permitted, compliance with legal obligations, or consent where required. Clients are responsible for identifying the appropriate basis for their own processing.
Who receives information
Authorized staff can access information according to their workspace role. Guests can access the records made available to them through the guest portal. Platform operators may access information as needed for administration, support, security or lawful client instructions.
Our current service providers include Hostinger for application hosting and database infrastructure, Resend for transactional email, Google for optional staff authentication, and Cloudflare for domain and DNS services. Resend receives recipient addresses and the content needed to deliver messages, including sign-in codes or invitations. A DNS-only Cloudflare record does not by itself route application traffic through Cloudflare's proxy. Provider involvement depends on the features you use and the deployment configuration.
We may disclose information when required by law, to protect the service or legal rights, or in a business transfer with appropriate protections and notices. Payment checkout integrations are currently deferred. We will update the relevant disclosures before enabling a payment provider. Tidebase's bookkeeping features do not mean that Tidebase processes card details.
Cookies and browser storage
Tidebase uses necessary cookies for staff, guest and platform sessions and temporary Google sign-in verification. Current staff and guest sessions expire after approximately 12 hours, platform sessions after one hour, and the Google flow cookie after ten minutes. Signing out ends the relevant session. Your browser can block or remove cookies, but sign-in may then fail. Cookies are scoped to their hostname, so a client domain can require a separate sign-in.
The Tidebase application uses necessary authentication cookies and does not include advertising trackers.
Retention and deletion
We keep information only as long as needed for the purposes described here, client instructions, security and applicable legal obligations. Session and invitation expiry limits access; it does not guarantee immediate deletion of every related database or log record. Suspending or closing a workspace currently preserves its data and is not a deletion request.
We will explain any necessary retention when responding to a deletion request. Retention depends on the record type, the client’s instructions, the purpose of keeping it and any applicable recordkeeping or dispute requirements. Contact us for information about your records and to request deletion. Backup copies can remain until replaced or expired through backup rotation; deletion requests are handled separately from closing a workspace.
Security and international processing
Tidebase uses HTTPS, password hashing, secure session cookies, workspace access controls and sign-in protections. No system can guarantee absolute security. Clients should protect credentials, assign appropriate roles and promptly remove access when staff leave.
Service providers may process information outside your country. Applicable protections depend on the processing location and law. Contact us for information about the locations and safeguards relevant to your workspace.
Your choices and rights
Depending on applicable law and our role, you may be able to request access, correction, deletion, restriction, portability or an objection to certain processing, withdraw consent where processing relies on it, or complain to the relevant supervisory authority. We may verify your identity before responding. Contact the operator that supplied your data or our monitored privacy address; we will route requests to the responsible party where appropriate. Operational reminder preferences can be managed through the available guest controls. Necessary sign-in and account messages may still be sent.
Tidebase staff accounts are for authorized business users, not accounts opened directly by children. Clients arranging activities for minors are responsible for suitable guardian involvement, notices and collection practices. Contact us if a child has provided information improperly so we can work with the client to address it.
Changes
We will post updates here with an effective date and provide additional notice where required for material changes. New uses of Google user data will require updated disclosures and authorization where required before that use begins.