Privacy and Cookie Policy

We collect only the personal information needed to provide the service. We do not sell data or use it to build an advertising network.

1. Cookies and local storage

• Required functions: cookies or browser local storage may be used for functions such as theme preferences and secure administration or download sessions.
• Optional analytics: Google Analytics runs on public pages only after you opt in. Advertising tracking is not used.
• Third-party links: when you visit PayTR, WhatsApp, YouTube or Instagram, the privacy and cookie terms of the respective service apply.

2. Payment Privacy

Before payment, checkout collects the details needed for delivery, contact and invoicing. Card payment is completed on PayTR’s domain; the card number, expiry date and CVV do not pass through Hermes servers. A successful payment notification is matched to the order. A personal download invitation goes to the customer, and a sales and invoice summary goes to authorized administrators. A bank transfer request is also recorded in the Mail Center; only the request and delivery email are sent to WhatsApp.

3. Optional Google account and Google Calendar connection

The Google connection is established when you initiate it in the Hermes desktop application. Your Google account identifier, name, email address and profile picture are used to display the connected account and perform actions with the correct account. This information is not used to create an advertising profile.

• Calendar created by Hermes: the https://www.googleapis.com/auth/calendar.app.created permission creates a separate “Hermes” calendar in your Google account. Depending on the sources you enable, classes, tasks, appointments, notes, birthdays and sky events are synchronized to this calendar. Event identifiers and mapping information, titles, descriptions, start and end dates and times, time zones, all-day information and reminders are used to create, read, update or remove events in this calendar. Supported Hermes event changes made in Google may also be reflected in local Hermes records. This permission is not used to write to other calendars that were not created by the application.
• Read-only display of Google events: if you enable “Show events from my Google calendar”, which is off by default, the https://www.googleapis.com/auth/calendar.events.readonly permission is requested separately. The current application obtains event records for the relevant date range from your Google account’s primary calendar through the Google API. Event identifiers, titles, locations, start and end dates and times, time zones, all-day information, cancellation status and Google Calendar links are used to display events read-only in the Hermes calendar, exclude cancelled events and offer the “Open in Google Calendar” function. The API response may contain additional event fields such as descriptions, organizers or attendees; this read-only feature does not save those additional fields in persistent storage. Hermes does not create, modify or delete events in your primary calendar through this feature. The scope name on Google’s permission screen may also cover other calendars; the current feature requests data from the primary calendar.
• Sharing permissions: Hermes does not manage Google Calendar sharing lists or access controls and does not request permission for that purpose. You manage calendar sharing through the Google Calendar interface.

4. Use, storage and sharing of Google user data

Google user data is used only to provide the user-visible account and calendar features described above. Account session information and OAuth access and refresh tokens are stored encrypted on the device using the operating system’s secure storage facilities. The Hermes calendar identifier, event mapping information and synchronization status are kept on the device. Supported changes retrieved from the separate Hermes calendar may be applied to local Hermes records. Events displayed read-only from the primary calendar are cached in application memory; data for the same date range may be reused for five minutes. This is not a server retention period; the memory ends when the application closes. Google Calendar event content is not sent to, or stored on, Hermes/Vercel servers.

Google user data is not sold or used for advertising, retargeting, credit assessment, surveillance, profiling, or developing, improving or training artificial intelligence models. Hermes administrators, employees and other users cannot access this data through Hermes servers. Data is not transferred to third parties other than the Google service acting on the user’s express instructions; only necessary and limited processing may take place where applicable law or security obligations require it.

Hermes’s use of information obtained from Google APIs and its transfer to other applications comply with the Google API Services User Data Policy, including the Limited Use requirements.

5. Disconnecting Google and deleting data

Disabling calendar synchronization: “Disconnect” on the Google Calendar card stops synchronization and read-only display and clears the event memory. This action alone does not sign you out of your Google account. If “Also delete the Hermes calendar in Google” is selected, the calendar created by the application and local mapping information are also removed. If it is not selected, the calendar identifier and mapping information are retained on the device so that you can reconnect.

Signing out of your Google account: “Sign out” on the Google account card attempts to revoke the refresh token in Google and deletes the encrypted Google session record on your device. The local session record is deleted even if you are offline. You may also revoke access through the third-party connections page of your Google Account. Your other Google calendars and local Hermes work records are retained unless you delete them separately. For deletion or privacy requests, you may write to info@hermesastroloji.com.

6. Administration and security

You can clear cookies and local storage in your browser. Blocking essential storage may prevent some session features from working. Connections use HTTPS, secret keys are kept on the server, and Hermes servers do not receive card details.

7. Changes and contact

Material changes are published by updating the effective date on this page. For questions, email info@hermesastroloji.com.

Optional visitor measurement

With your permission, Google Analytics 4 helps us understand public page visits, language and the referring domain. Our code removes query parameters other than lang and URL fragments from the page address, and removes paths and queries from referral addresses. Google uses pseudonymous analytics-cookie identifiers and network information processed during the connection. On permitted public pages, we also measure reaching approximately 90% of a page and selecting predefined product, pricing, preview, education and public AstroPen file links. Only fixed content codes are sent, never link text, full destination URLs, form fields or personal file access. A click is not a purchase or a completed download.

This public-page visit measurement does not start on account, administration, payment or personal download pages. Our code does not send names, email addresses, phone numbers, birth details, calendar content, administration keys, download tokens or form fields to Analytics. Google Signals and advertising personalization are disabled.

Your choice is stored in your browser for 180 days; analytics cookies are also configured for a maximum of 180 days. Use Cookie preferences at the bottom of the page to change or withdraw your permission. Withdrawal disables Analytics, clears analytics cookies and reloads the page. Google-side reporting and retention settings are governed by the Google Analytics service.

How Google uses data from sites that use its services

Purchase measurement with separate permission

Card checkout offers a separate, optional measurement checkbox. It starts unchecked and is separate from the agreements and delivery consent. Your choice does not affect payment, pricing, licence rights or delivery. Measurement applies only to purchases you permit and whose payment has been verified.

Google Analytics 4 receives a random transaction code, product plan, product value, currency, transaction time and pseudonymous analytics identifiers. A current identifier from a permitted public visit may be used to link that visit; otherwise a separate random measurement identifier is used and no traffic source is invented. Names, email addresses, phone numbers, invoice fields, birth details, licences and personal download keys are not sent. No Analytics tag reads payment form fields; advertising permissions remain denied.

Purchase permission lasts at most 7 days. Its control cookie is HttpOnly and Secure; only its hash is stored on the server. Permission and dispatch records enter daily cleanup after 30 days. Use the withdrawal button at checkout to withdraw this permission. Necessary only in Cookie preferences withdraws both public-visit and purchase measurement permission; a server withdrawal failure is shown and can be retried. Withdrawal prevents future dispatches; it cannot recall a network request already started and does not automatically delete previously processed Google reports.