Privacy Policy
Last updated: 13 October 2026
This Privacy Policy explains how personal data is processed when you use PlanetaryHours.io, create an account, save content, purchase a subscription or contact us.
It should be read together with the Terms of Use. Payment processing by Paddle is also subject to Paddle’s own privacy notice.
1. Controller and Contact
The controller of personal data processed directly by Planetary Hours is Vladyslav Babii, a sole proprietor trading as taburetka and operating the Planetary Hours product and brand.
Privacy contact: [email protected]
Additional operator information is available in the Imprint.
2. Scope and Principles
This Policy covers the website, calculation tools, accounts, saved windows, Plus access, support and technical operation of the Service.
Planetary Hours does not sell personal data, disclose it to data brokers, use behavioural advertising, or use third-party analytics tools. Personal data is not used for advertising profiles.
3. Personal Data We Process
3.1 Public use and calculations
When you visit or use the Service, we may process:
- IP address, request time, requested page, and browser or device information supplied with the request;
- security identifiers and diagnostic information;
- dates, times, locations, coordinates, time zones and settings you submit for a calculation.
The browser’s location function provides coordinates only after you grant permission. You may instead enter a place manually.
Ordinary calculation results are not added to an account as calculation history. Search and Election may use a temporary server record. Temporary search records are retained for no more than six hours.
3.2 Account and authentication data
If you create an account, we process:
- your email address and internal account identifier;
- the Account ID shown on your account page, a reference for support requests;
- an optional display name and profile image;
- authentication provider and account-security information;
- account creation, confirmation, authentication and latest authenticated activity timestamps;
- interface language, preferences, default location and favourite places;
- the time and version of the Terms and Privacy Policy that you accepted;
- the time at which you confirmed that you were at least 18 years old;
- account, entitlement and deletion-request status.
We do not collect your date of birth merely to record the age confirmation.
Our authentication provider handles passwords. Google sign-in is optional. If you choose it, Google supplies account information such as your identifier, email, name and profile image.
3.3 Saved windows
A saved window contains its title, selected time and place, calculation settings, and limited headline facts displayed when it was saved. It does not store the complete calculation result. Removing a saved window deletes its record.
Saved Windows is a Plus feature. When Plus access ends, Saved Windows become unavailable immediately. We retain them for 14 days so that access can be restored if Plus is reactivated. If Plus is not restored within that period, the Saved Windows are permanently deleted. Plus access ends only when no other Plus entitlement remains.
3.4 Subscription and billing data
Subscriptions are sold and processed by Paddle, acting as Merchant of Record and as an independent controller for its payment, tax, invoicing, fraud-prevention and transaction-compliance activities.
When checkout is started, Planetary Hours provides Paddle with the email address associated with the account and an internal account reference. Paddle may provide Planetary Hours with limited information needed to activate and administer the subscription, including:
- Paddle customer, transaction and subscription identifiers;
- product, plan and billing interval;
- subscription and payment status;
- current billing period and scheduled-change dates;
- purchase email and limited billing information contained in Paddle notifications.
Complete payment-card numbers and card security codes are collected by Paddle and do not reach Planetary Hours.
3.5 Support and correspondence
We process your message, reply email, account reference, originating page, language and timestamps to answer support requests. We also process technical identifiers to prevent abuse. A copy of the message is sent to the Support inbox through an email delivery provider.
Please do not include sensitive information that is unnecessary for your request.
4. Sources of Personal Data
We obtain data from you, from your browser when it communicates with the Service, and from Google or Paddle when you use their services.
5. Purposes and Legal Bases
Where the General Data Protection Regulation applies, we rely on the following legal bases:
| Purpose | Legal basis |
|---|---|
| Provide public calculations and requested website functions | Performance of a contract or steps taken at your request before entering into a contract (Article 6(1)(b) GDPR) |
| Operate accounts, authentication, preferences, saved windows and account support | Performance of a contract (Article 6(1)(b) GDPR) |
| Provide paid or complimentary Plus access and related communications | Performance of a contract (Article 6(1)(b) GDPR) |
| Protect accounts and the Service, apply rate limits, prevent fraud and abuse, diagnose faults and maintain reliable operation | Our legitimate interests in security, service integrity and reliable operation (Article 6(1)(f) GDPR) |
| Answer support and privacy requests | Performance of a contract where the request concerns the Service, and our legitimate interests in supporting users and keeping necessary correspondence (Articles 6(1)(b) and 6(1)(f) GDPR) |
| Keep records required for tax, accounting, consumer-protection or other legal duties, and respond to binding legal requests | Compliance with legal obligations (Article 6(1)(c) GDPR) |
| Establish, exercise or defend legal claims and enforce the Terms | Our legitimate interests in protecting our legal rights (Article 6(1)(f) GDPR) |
| Notify users and delete accounts under the retention rule in Section 11 | Our legitimate interests in keeping personal data no longer than necessary and in reducing the security risk of accounts kept without Plus (Article 6(1)(f) GDPR) |
Where we rely on legitimate interests, we consider the necessity and proportionality of the processing and the effect on your rights.
Accepting the Terms or acknowledging this Policy is not consent to unrelated optional processing. Where consent is required, we request it separately.
6. Data Required to Provide a Feature
An email address, authentication credential, acceptance records and age confirmation are required to create an account. The Service cannot create or maintain the account without them.
The date, time, location and settings relevant to a requested calculation are required to perform that calculation. Subscription and transaction identifiers are required to provide paid access and administer the subscription.
Google sign-in, profile image, display name, favourite places and saving a window are optional. You may use public features without creating an account where the relevant feature is offered publicly.
7. Cookies and Browser Storage
Planetary Hours uses only storage necessary to provide, secure or remember the Service requested by the user.
Session cookie
The Service sets a cookie named session. It is used to distinguish a browser session from abuse and to associate an in-progress calculation with that session. It is deleted when the browser session ends.
Local browser storage
Local browser storage remembers locations, settings, display preferences and language. It also stores authentication information when you sign in.
Stored items remain until cleared or removed, including on sign-out where applicable. Blocking necessary storage may prevent features or account access from working.
Account security challenge
Account forms use Cloudflare Turnstile to prevent automated abuse. Cloudflare may process IP addresses and browser or device signals for this check. It is not loaded by other Planetary Hours pages.
Planetary Hours does not use analytics, advertising or cross-site tracking cookies.
8. Recipients and Service Providers
Personal data is disclosed only where necessary to:
- contracted providers acting on our instructions for authentication, database operation, infrastructure, security and transactional email;
- Paddle, as the independent Merchant of Record for purchases and subscriptions;
- Google, if you choose Google sign-in;
- Geoapify, operated by KEPTAGO LTD, for place suggestions, place search and reverse geocoding;
- Cloudflare, for Turnstile security checks on account forms;
- professional advisers, courts, regulators or public authorities where disclosure is necessary to comply with law or establish, exercise or defend legal claims.
For place search, Geoapify receives the search text and language, or coordinates for reverse lookup, through our server. Place-lookup responses may be cached for up to 90 days and are not linked to an account for that purpose.
The relevant independent-provider notices are:
- Paddle Privacy Notice;
- Google Privacy Policy;
- Geoapify Privacy Policy;
- Cloudflare Turnstile Privacy Addendum.
We do not disclose personal data to advertisers or data brokers.
Service providers and processing locations
We use Supabase to provide account authentication and database services and Resend to deliver transactional emails. These providers process personal data on our behalf only as necessary to provide their services. Our primary application server is hosted in Germany. Other service providers may process personal data in the European Economic Area or in other countries. Section 9 describes international transfers.
9. International Transfers
Providers may process personal data outside the European Economic Area. Where we are responsible for such a transfer, we use an applicable adequacy decision or appropriate safeguards, such as standard contractual clauses. Supplementary measures apply where required.
For information about applicable safeguards, contact [email protected]. Independent controllers describe their transfers in their own privacy notices.
10. Retention
We keep identifiable personal data only for as long as necessary for the stated purpose and then delete or anonymise it, unless a longer period is required by law or needed for a legal claim.
The current retention rules are:
- Session cookie and browser preferences: the cookie is deleted when the browser session ends. Preferences remain until cleared or removed.
- Temporary search records: no more than six hours. Ordinary results are not stored as account history.
- Place-lookup cache: up to 90 days, without an account link.
- Account records: while the account exists, subject to Section 11.
- Unconfirmed registrations: three days after the last confirmation email, unless a purchase or other billing record prevents deletion.
- Saved windows: until you remove them or the account is deleted. When Plus access ends, they are unavailable to you and retained for 14 days, then permanently deleted unless Plus is restored.
- Support communications: unhandled Support reports are retained for up to 180 days. Handled reports are removed from the database after archival. A limited archive is retained for 60 days after handling and removed at the next daily expiry check. Related email correspondence is retained as necessary to resolve the request or a dispute.
- Technical and security logs: local copies use limited rolling storage. Monitoring copies are retained for 30 days, or up to 90 days for warnings and errors. Relevant records may be preserved for an incident or legal claim.
- Billing and account-administration records: Paddle event content is removed after 90 days. Event metadata is retained for 24 months. Billing disputes and unresolved purchase-linking records remain until resolved and for 24 months after closure. Inactivity notices and deletion decision records are retained for 24 months after closure or deletion. Security audit records, including account deletion events, are retained for 180 days. Accounting, tax and legal-claims records may remain for applicable legal periods, without an active account link where practicable. Paddle applies its own retention rules.
- Backups: database-provider backups are retained for seven days. Our encrypted account and billing exports are retained for up to eight weeks. Saved-window exports are retained for up to twelve months. Deleted data may remain in these copies until expiry. After a restore, we delete again every account deleted since the copy was made.
11. Account Access and Deletion
To request a machine-readable copy of the account records available through the Service, write to [email protected], preferably from the email address associated with the account.
When signed in, you can open Account → Subscription and choose Delete my account. An account is scheduled for deletion seven days after the request. For a running subscription, confirming deletion cancels its renewal at the end of the paid period. Deletion is scheduled seven days after the subscription ends. Paused subscriptions or subscriptions with outstanding payment collection must first be cancelled. An unresolved billing dispute, legal hold or purchase-linking issue may delay deletion.
Before deletion, you can choose Keep my account on the account page to cancel the deletion request. This does not restore subscription renewal.
Deletion removes the authentication account, profile, saved windows, preferences and linked entitlements. Records retained under Section 10 are kept without an active account link where practicable.
Our authentication provider’s authentication log may keep sign-up and sign-in events under its own retention rules. Account deletion does not remove data independently controlled by Paddle or Google.
Inactive accounts
We delete an account that has been without Plus for six months. The six months are continuous calendar months. They run from the end of the account’s last Plus coverage or, if the account never had Plus, from its creation. Signing in does not change this. Paid coverage and a manual or promotional Plus grant both count. A cancelled renewal leaves paid coverage intact until its end; cancelling the renewal does not start the six months.
Before we delete an account, we send one warning email to its confirmed email address at least seven days before the deletion date. The warning states the date. If the warning is sent later than planned, the deletion date is at least seven days after it.
To keep the account, restore Plus before that date; a manual or promotional Plus grant also keeps it. You can also write to [email protected] and quote the Account ID shown in the email and on your account page.
Deletion removes the same account data as a deletion you request yourself, subject to Section 10.
We do not delete an account under this rule while:
- an email to it could not be delivered, bounced or was reported as spam;
- a subscription is paused or its payment is still being collected;
- a billing dispute, chargeback, refund review or legal hold is open;
- a payment or subscription has not been linked safely to an account;
- the account has no confirmed email address (the three-day rule in Section 10 applies instead).
A deletion you request yourself follows the seven-day process above, separately from this rule.
12. Your Rights
Subject to the conditions and limits in applicable law, you may have the right to:
- obtain confirmation whether we process your personal data and receive access to it;
- correct inaccurate or incomplete personal data;
- request erasure of personal data;
- request restriction of processing;
- receive data you provided in a structured, commonly used and machine-readable format and, where applicable, have it transmitted to another controller;
- object, for reasons relating to your particular situation, to processing based on legitimate interests;
- withdraw consent at any time where a particular processing activity is based on consent, without affecting earlier lawful processing;
- lodge a complaint with a competent supervisory authority.
To exercise a right, write to [email protected]. We may request information reasonably necessary to verify your identity and protect the account. We will respond within the period required by applicable law, normally within one month under the GDPR; a lawful extension may apply to a complex or numerous request.
You may complain to the supervisory authority for your habitual residence, place of work or the alleged infringement. Contacting us first is not required.
13. Automated Calculations
Calculations produce results you request. We do not use them to make solely automated decisions about you with legal or similarly significant effects.
14. Security
We use appropriate technical and organisational measures intended to protect personal data against unauthorised access, alteration, disclosure, loss or destruction.
No internet service can guarantee absolute security. You should protect your login credentials and notify [email protected] if you believe that your account has been compromised.
15. Children and Other People’s Data
Account registration requires confirmation that the user is at least 18 years old. The Service is not directed to children, and we do not knowingly create accounts for children.
The Service is not intended to be a client-record or medical-record system. Do not place names or other unnecessary identifiers in calculation inputs or saved-window titles. If you submit information relating to another person, you are responsible for having a lawful basis to do so and for providing any notice required by law.
If you believe that a child or another person has provided personal data unlawfully, contact [email protected].
16. Changes to This Policy
We may update this Policy to reflect changes in the Service, data processing or applicable law. The current version will be published with its effective date.
Where a change materially affects how existing personal data is processed, we will provide additional notice or obtain consent where required by law. Changes do not reduce rights that cannot lawfully be waived.