Clav World HQ Privacy Policy

Last updated November 3, 2026

Clav World HQ is the internal workspace operated by Clavs World Inc. (“we”). Our team uses HQ to coordinate schedules, events, messages and daily work. This policy explains what HQ handles and who can see it. For privacy questions or deletion requests, email clavicularalt@gmail.com.

Information in the workspace

We use team members’ names, sign-in email addresses, phone numbers, roles and access status to run accounts, manage permissions and deliver work updates. HQ also stores information people put into the workspace, including messages, announcements, acknowledgments, event plans, tasks and files or photos they submit, and text messages team members send to HQ’s number (for example replies and commands). We use these records to coordinate work, show who is responsible for a task and keep a history of changes. HQ uses session cookies to keep people signed in. If someone enables browser notifications, HQ uses their browser’s push subscription to deliver alerts.

What connecting Google Calendar means

When Calendar sync is available, the owner of the designated team calendar can connect their main Google Calendar to HQ. Events from that calendar, including personal appointments on it, can appear on the shared HQ schedule for the whole team. A “private” label in Google should not be relied on to hide an appointment in HQ. Individual team members can use HQ without connecting their own Google calendars.

Google’s Calendar events permission (calendar.events) allows an app to view and edit events across calendars the connected account can access. HQ uses it to sync the designated main calendar. HQ reads event details such as titles, dates, times, locations and descriptions when present. It uses calendar and event identifiers, event changes and cancellations to match records and keep the schedule up to date. When an event changes or is deleted in Google, HQ updates its copy. When an authorized teammate creates or reschedules an event in HQ, HQ writes that change to the connected calendar. HQ does not send Google Calendar invitations for those changes.

Google issues tokens that let HQ keep syncing after the calendar owner signs out. HQ stores the connection credentials on its server and stores the event information needed for the shared schedule in its database. When Google signals that the calendar has changed, HQ uses the connection to retrieve the changes.

Who receives information

Approved team members see information according to their workspace access. On the shared calendar, that includes synced appointments even when a teammate is not a Google invitee. When a schedule change affects someone’s work, HQ may send that person the event title, updated time or task deadline through the app, push notification, email or text. Email and text alerts can leave a copy in the recipient’s inbox or on their device.

We use Vercel to host HQ and Supabase for accounts, database records and file storage. When a delivery channel is enabled, Resend processes sign-in and notification emails, Sendblue processes text messages to and from HQ’s number, and browser push services deliver push alerts. These services receive the information needed to perform their functions. Separately, when enabled, HQ uses Anthropic to interpret text commands, to-do lists and itineraries submitted to those features. Connecting a calendar does not send its contents to Anthropic.

We use data received from Google to provide and maintain the scheduling features described here. We do not sell Google user data, use it for advertising, or use it to train general-purpose AI models. Our use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Retention, disconnection and deletion

We keep workspace records while they are needed to coordinate work, maintain account security or meet legal obligations. We keep Google connection credentials only as needed to maintain the authorized sync. The calendar owner can stop future access by removing Clav World HQ from Google Account connections. Revoking access stops HQ from fetching or writing new changes. It does not by itself erase information already copied to HQ, remove events already written to Google, or recall alerts already delivered.

To request deletion of your HQ account information, the stored Google connection or imported event data, email clavicularalt@gmail.com and identify the account and records involved. We may verify your identity before acting. We remove the requested data from active systems unless we need to retain specific records for security or legal reasons. Backup copies may remain until the backups expire. Deleting an HQ copy through a privacy request does not instruct us to delete the original Google event.

Changes to this policy

We will post updates on this page. If we intend to use Google data for a new purpose, we will explain the change and ask the calendar owner for consent before using it that way.