Privacy
This policy explains how Aeglo collects, uses, stores, and shares account, booking, payment, and data from Google and Zoom when connected by the user.
Optional card payments
If a provider connects Stripe and enables card payments, Stripe collects identity, business and payout information in its own form. Aeglo stores connected-account and payment identifiers, amount, currency, and payment/refund status. To process payment we send Stripe the customer’s email, service name, amount and booking identifier. Aeglo does not store card numbers or CVC codes. Stripe’s own processing is covered by its privacy policy at stripe.com/privacy.
Technical error monitoring
We use Sentry to detect and fix errors. We send limited technical error information to its German ingestion endpoint: error type, code location and application version. Error messages, request data, user identifiers and booking content are removed before sending. Session replay and user activity tracking in Sentry are disabled. The provider necessarily sees the connection IP address when processing a browser request.
Measuring service adoption
We record preview creation, claiming, publication and first-booking events to improve adoption. Aggregate reporting distinguishes entry channel and campaign. This measurement does not add advertising cookies or send booking contents to third-party analytics.
Processing roles and contact
Aeglo is the controller for Aeglo account, authentication, subscription, and service-operation data. The provider is the controller for their customers’ booking, contact, and invoice data, and Aeglo processes that data on the provider’s behalf as a processor. A data-subject request concerning a booking should first be sent to the provider named on the booking page; Aeglo assists the provider in fulfilling the request. Questions about Aeglo’s own processing can be sent to mart@aeglo.me.
Data and purposes
Aeglo processes account and workspace data, service descriptions, working hours, customer booking and invoice data, and the receipt status recorded by the provider. We use this data to manage accounts, create public booking pages, show availability, prevent double bookings, manage bookings and billing documents, and send service-related notifications. Bank account numbers and integration credentials are encrypted at rest; the settings summary masks the bank account. Payment instructions and invoices show the account details needed for payment; an authorized user can edit them in the invoice editor.
Use of Google data
For Google sign-in, Aeglo uses the name, email address, and Google user identifier to identify the account. When a user connects Google Calendar, Aeglo reads only busy time ranges to hide conflicting booking slots, and creates, updates, or deletes only Aeglo booking events and their Google Meet links in the user's calendar. Aeglo does not need or retain the titles, descriptions, or attendees of the user's other calendar events.
Protection of Google user data
Aeglo transfers Google user data only over HTTPS/TLS-encrypted connections. Google OAuth access and refresh tokens are encrypted with AES-256-GCM before they are stored in the database, processed only on Aeglo's servers, and never returned to the user interface or another customer account. Protected operations require a valid authenticated session and an appropriate account role; database requests are bound to the authenticated user and their Aeglo account to isolate customer data. Access to production systems is limited to authorized services and people who need it to operate the service, investigate a security incident, or meet a legal obligation. Authenticated encryption detects tampering with encrypted credentials, and sign-in sessions can be revoked.
Google Limited Use
The use of information received from Google Workspace APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Aeglo uses Google data only to provide user-visible sign-in, availability checking, and calendar synchronization. Aeglo does not sell Google user data, use it for advertising or credit assessment, use it to train general-purpose AI or machine-learning models, or transfer raw or derived Google Workspace data to OpenAI or other third-party AI services.
Artificial intelligence
When a user chooses AI-assisted service or working-hours creation, Aeglo may send the provider name, service description, working-hours description, and schedule supplied by that user to the OpenAI API. Model-side storage is disabled for these requests. Data received from Google Workspace is not included in them.
Google data retention and deletion
Calendar busy ranges are processed for the request and are not stored in Aeglo's database. Google access and refresh tokens, granted scopes, Google user identifier, and selected calendar identifier remain encrypted while the calendar is connected. On disconnect, Aeglo revokes the Google authorization and deletes the connection data; if Google's revocation service is temporarily unavailable, the encrypted credential is retained only for an automatic retry. The Google event identifier for an Aeglo booking is retained with that booking so the event can be updated or cancelled.
Use of Zoom data
When a user connects Zoom, Aeglo identifies the authorized Zoom account and creates a Zoom meeting for a confirmed booking or open-group session. Aeglo adds the Zoom join link to the customer's confirmation and calendar details, updates the meeting when the booking is rescheduled, and deletes it when the booking is cancelled. Only the service name, start time, duration, and customer name needed to create the meeting are sent to Zoom. Aeglo does not use Zoom data for advertising or to train artificial-intelligence models.
Protection, retention, and deletion of Zoom data
Zoom OAuth access and refresh tokens are encrypted with AES-256-GCM before database storage and are processed only on Aeglo's servers. While the connection is active, Aeglo retains the Zoom account identifiers, granted permissions, and each booking's Zoom meeting identifier and join URL so the meeting can be updated or cancelled. When Zoom is disconnected, Aeglo revokes the authorization and deletes the access and refresh tokens. To disconnect safely, Aeglo first asks the user to choose another meeting method for active Zoom services and complete or cancel future Zoom bookings.
Retention
We retain personal data for bookings without an invoice for up to 730 days after the service ends, and waitlist data for 30 days after the session ends. The system then automatically anonymizes names, email addresses, answers, and management credentials. Invoice records are retained for seven years from the end of the financial year in which the invoice was recorded, as required by Estonian accounting law; buyer data is anonymized after that period.
Access, export, and deletion
An account owner can download a JSON copy of workspace data from Settings and the data associated with an individual client from the client detail view. A customer can use the booking management link to export booking data and request anonymization. If a statutory invoice retention period still applies, the data is anonymized when that period ends. A provider’s customer may submit a rectification, deletion, restriction, or other data-subject request to the provider; Aeglo supports the provider in fulfilling it.
Service providers and transfers
Aeglo uses Hetzner for hosting, Resend for transactional email, Google for optional sign-in and calendar synchronization, and OpenAI for optional AI-assisted copy and working-hours creation. Each provider receives only the information needed to perform its service. Raw or derived Google Workspace user data is not transferred to OpenAI.