Your privacy, in your hands.
Privacy policy & Google Calendar data
Last updated: 4 November 202690 days for past appointment records · Encrypted guest details · Google events remain after ETA data deletion
Your account and card
We store your name, email, card details, links and offerings to operate your account. Passwords are hashed. You choose public and private fields; contact exchange within accounts requires approval. Do not publish information you do not want visitors to see.
Google connection is optional
We request permission to manage events on calendars you own and to check availability. These permissions are broader than our current use: we use only your primary calendar, check busy periods without storing details of unrelated events, and create, read, reschedule and cancel ETA Card booking events. We do not read Gmail or Google Contacts.
What we store for appointments
We encrypt Google authorization tokens on the server and store availability settings, time zone, meeting types, event identifiers, times and booking status. Guest names, email addresses and notes are encrypted. Necessary booking details are sent to Google to create the event and request a guest invitation; Google copies and guest invitations are subject to their policies.
Retention: 90 days
Automatic cleanup deletes booking records, guest details and associated operations more than 90 days after the appointment ends, on the next cleanup cycle while the server is running. Pending or unresolved operations are excluded until resolved or you manually delete calendar data. Authorization remains until you disconnect Google; settings remain until you delete calendar data. OAuth authorization states expire after 10 minutes and are removed by cleanup.
Disconnect and delete calendar data
In Appointments, choose “Disconnect Google” to revoke authorization and remove tokens from ETA. If revocation fails, we report an error rather than claim success. Then choose “Delete calendar data” to remove all bookings, guest names, email addresses, notes, settings and follow-up operations from the active ETA database. Deletion waits if an operation is running. This does not delete Google events, guest invitations, your account, card or subscription. You can also remove access in your Google Account security settings.
Sharing and Limited Use
We do not sell Google data or use it for advertising or training AI models. Its use is limited to the booking features you choose. ETA Card’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Human access to Google data is limited to your consent or permitted security or legal needs. Hosting and email providers process data necessary to operate the service.
Google website and registration analytics
We use Google Analytics on public marketing pages and the registration and sign-in pages after analytics consent. We measure page views, successful account creation and traffic sources to understand registrations from search and other channels. We do not send names, email addresses, phone numbers, account identifiers, card contents, booking data or calendar data. Unnecessary URL parameters are removed and referrers are reduced to their origin. Automatic enhanced form measurement is off; advertising features and Google signals are not enabled in this integration. Card-specific analytics cookies can last up to 180 days, and your consent choice is stored locally for up to 180 days. Decline or change your choice using Analytics preferences without losing account creation or service access. Visits without consent are not measured, and reports can be delayed. Google processes measurement data under its policies. Google Calendar data is not included.
Sessions, analytics and drafts
Session cookies support sign-in and request protection. Card analytics help owners understand visits and sources; calendar data is not joined to marketing analytics. Your browser may store an appointment-settings draft and a temporary booking request identifier, without guest details, to recover its status. Server deletion does not clear drafts on other devices; clear browser site data when needed.
Backups and financial records
Our adopted policy for backups we manage is protected retention for 30 days from creation, followed by deletion. Enforcement and deletion verification are still part of launch preparation; Hostinger’s automatic backup retention has not yet been verified, so we do not currently promise that all hosting copies are deleted within 30 days. Deletion requests must be reapplied after restoration before service is reopened to users. Under our accounting policy, financial records, including invoices and evidence of payments and refunds, are retained for five years from the transaction date in protected storage with restricted access. This exception does not cover Google tokens, guest details or calendar content, and does not mean keeping the entire application database for five years.
Deletion, support and backups
The operator is «الراجح للاستدامة والتطوير», registered in Jordan, at Villa 5, Zainab Al-Asadiyah Street, Dahiyat Al-Rasheed, Amman, Jordan. To request account deletion or deletion of your guest information, contact us using the email associated with your request. We verify identity before processing it. Direct deletion applies to the active database; no hosting backup-deletion deadline is promised before its production retention settings are established. Material policy changes will be published on this page.