Privacy is a promise, not a setting

This page is AresHub’s privacy policy. It applies to areshub.com, the workspace app at app.areshub.com, and related AresHub services.

Last updated: 2 September 2026.

AresHub's automation is designed so your contacts won't resent it: messages only during daytime hours in their country, a mandatory identified sender, one-click unsubscribe, hard volume caps. Good manners aren't a toggle you can switch off — they're part of the product.

AresHub is the controller of personal data processed to run the AresHub service (workspace accounts, product features, this website).

Questions about this policy, access, or deletion: contact form or info@areshub.com. We reply in Bulgarian or English.

When you create a workspace and use AresHub, we process the data needed to provide the features you use, including:

- Account and workspace data — name, email, role, workspace settings.
- Contacts and reservations — names, emails, phones, booking times, guest kinds, resource names and locations you enter.
- Inbox, documents, reminders, websites, short links, offerings — content and metadata you create in those modules.
- Technical data — authentication tokens, security logs, and the minimum needed to operate and secure the service.

We do not sell personal data. We do not use product data to train generalized AI or machine-learning models.

A workspace owner or admin may optionally connect one Google account so AresHub can put reservations on Google Calendar. This is never required to use AresHub. Until you connect, we do not access any Google user data.

When you connect, we request only these Google scopes and access only the data below:

1. Google account email (userinfo.email) — the email of the Google account that granted access, so we can show it in workspace settings (for example “Connected as owner@example.com”) and so you can tell which account is linked.
2. Calendar list (calendar.readonly) — the names and IDs of calendars that account can see, so you can pick which calendar each AresHub resource should write to.
3. Calendar events (calendar.events) — permission to create an event when a reservation is booked on a mapped resource, to update the end time of that same event if the member marks the reservation happened before the booked end, and to delete that event when the reservation is cancelled or marked as a no-show. We store the Google event ID that we created so we can update or remove that same event. We do not import, list, or copy existing events from your calendars into AresHub. AresHub remains the source of truth for bookings.

We do not request Gmail, Drive, Contacts, or any other Google product scopes.

Google user data is used only to provide the Google Calendar feature in the AresHub user interface:

- Show that the workspace is connected, and which Google email is connected.
- Let members map an AresHub resource to one of that account’s calendars (or leave it unmapped).
- On reservation create, insert a calendar event (title, start/end, timezone, optional location). For a single-guest booking we add the contact’s email as attendee so Google can send the invite. For multi-guest and anonymous bookings we insert the event without an attendee.
- On reservation cancel or no-show, delete that event so the invite is withdrawn (and the shared calendar is freed).
- On an early “happened”, patch the end time of the event we created.
- Refresh a short-lived access token using the stored refresh token so those actions keep working until you disconnect.

We do not use Google user data for advertising, for profiling, for selling data, or to develop, improve, or train generalized AI or machine-learning models.

AresHub's use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

We do not sell Google user data. We do not share it with advertisers or data brokers. We do not transfer it to other apps for their own use.

We disclose Google user data only in these cases:

- Google, as the calendar provider you connected — we send create, update, and delete requests to the Google Calendar API, and for a single-guest booking we send the contact’s email to Google as an event attendee so Google can deliver the calendar invite. That is the purpose of the integration.
- Infrastructure — AresHub runs on Google Cloud in the European Union (Cloud Run and Firestore). OAuth tokens and calendar mapping IDs are stored there so the feature can run. Google Cloud acts as our hosting processor, not as a recipient of calendar data for its own product use through this integration.
- Workspace members — people in your AresHub workspace can see that Google is connected, the connected email, which calendar you mapped to a resource, and whether a reservation synced. They cannot see OAuth tokens.
- Legal obligation — if we are required by law to disclose data, we will do so only to the extent required.

We do not allow humans at AresHub to read Google Calendar contents except where necessary to operate or secure the service, to comply with law, or with your explicit request (for example a support ticket you open about a failed sync). Tokens are never returned to the browser or written to application logs.

Google OAuth tokens and calendar identifiers are treated as sensitive:

- Storage — the refresh token is stored only on the workspace’s integration record in Firestore. It is never sent to the AresHub web app, never included in API responses, and never logged.
- Access tokens — minted when needed and not kept after the Calendar API call.
- Transport — all browser, API, and Google API traffic uses HTTPS.
- Access control — only the AresHub API (running as the Cloud Run service account) can read the integration record. Connecting or disconnecting Google is limited to workspace owners and admins. Each workspace is isolated from every other workspace.
- Hosting — data is stored in the European Union (Google Cloud, europe-west1).
- Disconnect — we revoke the token with Google and delete the stored tokens and connected email from AresHub.

We do not keep a copy of your Google Calendar. We only store the identifiers needed to write and later delete events AresHub created.

To delete Google user data from AresHub: an owner or admin uses Disconnect in the app. That revokes access with Google and deletes tokens and the connected email from our systems. You can also revoke AresHub in your Google Account permissions. After revoke, AresHub can no longer call Calendar until someone connects again.

To delete your AresHub workspace and remaining account data, contact us via the contact form. Website form submissions auto-expire after 12 months. Inbox mail stays until a member deletes it. Either can be deleted sooner on request.

Depending on applicable law (including GDPR), you may request access to personal data we hold about you, correction of inaccurate data, deletion, restriction of processing, and a copy of your data. Workspace owners can already disconnect Google Calendar and manage contacts, reservations, and other records in the app. For anything you cannot do in the product, write to us using the details in Who we are.

Get in touch · Start for free