Privacy Policy

1. Data controller

Privacy enquiries: hello@ceqtor.com

2. Visiting the public website

When you open the website, technically necessary connection data may be processed, including IP address, time, requested URL, transferred volume, referrer, browser, operating system, and status code. This is required to deliver the site, detect attacks, and operate it securely. The legal basis is Article 6(1)(f) GDPR.

Hosting

The application is hosted by STRATO GmbH, Otto-Ostrowski-Straße 7, 10249 Berlin, Deutschland. The host processes technical data on our behalf under a data-processing agreement.

Cookies

We currently use no analytics, advertising, or social-media tracking cookies. Technically necessary cookies protect login sessions, security, and language settings.

3. Account and weekly planner

Registration and profile

We process name, email address, password hash, verification status, timezone, and optional profile details to create, authenticate, and manage your account. The legal basis is Article 6(1)(b) GDPR.

Appointments, tasks, notes, and files

To provide the app, we store the appointments, tasks, boards, notes, links, uploaded files, archive records, focus data, and settings you create. Free text, calendar-feed URLs, billing addresses, and other sensitive app content are encrypted in the database. Passwords are stored only as one-way hashes.

Support and philanthropic accounts

Service Desk and free-access requests require the message, category, processing status, correspondence, and contact data needed to respond and prevent misuse. The legal basis is Article 6(1)(b) and (f) GDPR.

4. Integrated services

Optional sign-in with Google or Apple

If you choose Google or Apple, that provider receives the authentication request and technical connection data. We receive its stable account identifier, your name, and a verified email address; Apple may provide a private relay address. We store the identifier only as a keyed, non-reversible fingerprint and do not retain provider access or refresh tokens. The purpose is secure account creation and sign-in under Article 6(1)(b) GDPR. Google Ireland Limited and Apple Distribution International Ltd. may involve processing outside the EEA under their applicable safeguards.

Google privacy · Apple privacy

Stripe

Stripe handles subscriptions and invoices. When you set up payment or open billing, name, email, billing address, transaction, and payment information are sent to Stripe. Full card or wallet data is not stored on our servers. For EEA users, the provider is generally Stripe Payments Europe, Limited, Dublin, Ireland. Processing may take place outside the EEA using recognised safeguards. The legal basis is Article 6(1)(b) and, for statutory records, Article 6(1)(c) GDPR.

External calendars

If you connect a calendar feed, our server retrieves its address and displays selected event data. Feed URLs are encrypted. The connected provider’s privacy terms also apply.

Weather and geocoding

For timed appointments with an address, the address may be sent server-side to a configured OpenStreetMap/Nominatim geocoder and the resulting coordinates to Open-Meteo. The cache uses a non-reversible address hash with coordinates and forecast data. Appointments without time or address are not queried.

Stripe privacy · Nominatim policy · OpenStreetMap · Open-Meteo terms

Email

A configured email processor delivers verification, security, billing, and support messages and processes recipient, subject, message, and delivery metadata.

5. Security, logs, and recipients

Safeguards include encrypted transfer and sessions, access controls, separate administrator permissions, private file storage, security headers, audit logging, and encrypted backups.

Limited metadata about security-relevant actions may be retained for operation, fraud prevention, support, and forensic investigation. It can include account, time, action, object ID, request information, and outcome. Content is logged only where necessary.

Recipients receive data only where required to perform the contract, operate securely, comply with law, or follow your instruction. Required processor agreements are concluded.

6. Retention

Account and app data are generally retained for the user relationship. After deletion is requested, data are deleted or restricted unless legal retention duties, an active security incident, or open claims require otherwise. Billing documents follow commercial and tax retention periods; security logs are deleted or anonymised according to configured retention.

Rolling backups are overwritten over time, so final deletion from backup copies may be delayed. Restoration occurs only after a security or data-loss event.

7. Your rights

Subject to the GDPR, you may request access, correction, deletion, restriction, portability, or object to processing. Consent can be withdrawn for the future at any time. Contact hello@ceqtor.com. You may also complain to a data-protection authority, particularly the competent authority in Brandenburg.

No solely automated decision with legal or similarly significant effect takes place.

8. Changes to this policy

We update this policy when functions, providers, or legal requirements change. The current version remains available on this page.

9. Staff access, Stripe roles, and log retention

Private appointments, tasks, notes, and files are not routinely read. Authorised staff may access personal data only for a specific support request, billing, security incident, legal duty, or documented investigation. Access is limited to what is necessary and is logged where possible.

Depending on the activity, Stripe acts either as our processor or as an independent controller, for example for fraud prevention, regulatory duties, and its own payment services. Transfers outside the EEA rely, as applicable, on adequacy decisions, the EU-US Data Privacy Framework, or EU Standard Contractual Clauses.

Production application logs are currently rotated after 14 days. Security and audit events are currently retained for up to 400 days unless an incident, legal claim, or statutory duty requires longer retention.

The legal basis depends on the purpose and is Article 6(1)(b), (c), or (f) GDPR. Our legitimate interest is the secure and accountable operation of the service, balanced against the confidentiality of your work content.

10. Waiting list, email preferences, and file checks

When registration is paused, you may consent to store your encrypted email address and language for one reopening message. A keyed, non-reversible hash prevents duplicates within that list. The entry is not carried into a later list and is deleted no later than 30 days after reopening. The legal basis is Article 6(1)(a) GDPR.

Necessary verification, account-security, billing, contract, cancellation, and support messages are processed under Article 6(1)(b), (c), or (f) GDPR. An inactivity reminder after 14 days is sent only with your voluntary consent and can be disabled in Settings or through its unsubscribe link.

For delivery, retry control, and duplicate prevention, we retain only the required transactional-message metadata.

Uploads are checked locally with ClamAV for known malware before storage. Files that are unsafe or cannot be scanned reliably are rejected. Modern Office files are converted locally with LibreOffice in a short-lived environment separated from the network and other customer data. No external malware-scanning or conversion provider receives the file.