Privacy Policy

Who is responsible for data collection on this website?

Data processing on this website is carried out by the website operator. You can find their contact details in the section 'Information about the responsible party' in this privacy policy or in the imprint.

How do we collect your data?

Your data is collected in two ways: directly from you when you register or contact us by email, and automatically by our systems when you visit the website. The automatically collected data primarily consists of technical access data (e.g., browser type, operating system, time of page view, and IP address) processed by Vercel's infrastructure to provide the website securely and reliably. The IP address is personal data; details on its processing by our hosting provider can be found in the "Hosting" section.

What do we use your data for?

Your data is used to provide and improve the application, to manage your user account, to bill paid subscriptions, to enable offline synchronization across your devices, and to ensure the security and stability of the service. Aggregated and pseudonymized or technical usage data is used to analyze and optimize the performance of the website.

What rights do you have regarding your data?

You have the right to receive information about the origin, recipient, and purpose of your stored personal data free of charge at any time. You also have the right to request the correction or deletion of this data. If you have given your consent to data processing, you can revoke this consent at any time for the future. You also have the right, under certain circumstances, to request the restriction of the processing of your personal data. Furthermore, you have the right to lodge a complaint with the competent supervisory authority. You can contact us at any time if you have further questions about data protection.

Requirement to provide data:

Unless stated otherwise in the sections below, you are not legally or contractually required to provide your personal data, and it is not necessary for concluding a contract; you are not obliged to provide the data. However, without certain data (e.g. registration data for an account) we cannot provide the service (Art. 13(2)(e) GDPR).

External Hosting

This website is hosted by an external service provider (hoster). The personal data collected on this website is stored on the hoster's servers. This may primarily include IP addresses, contact requests, meta and communication data, contract data, contact details, names, website accesses, and other data generated via a website.

The hoster is used for the purpose of fulfilling contracts with our users (Art. 6 para. 1 lit. b GDPR) and in the interest of secure, fast, and efficient provision of our online offering by a professional provider (Art. 6 para. 1 lit. f GDPR). We use only technically necessary cookies and do not employ any consent-requiring storage of, or access to, information on your end device within the meaning of § 25 TDDDG.

Our hoster will only process your data to the extent necessary to fulfill its performance obligations and follow our instructions regarding this data.

Vercel

We use Vercel as our hosting provider. The provider is Vercel Inc., 440 N Barranca Ave #4133, Covina, CA 91723, USA. When you visit this website, Vercel automatically collects various log files including your IP addresses. This data is used to provide and ensure the stability and security of the service. For more information, see Vercel's privacy policy: https://vercel.com/legal/privacy-policy

Vercel provides a standard Data Processing Addendum (DPA) as part of their Terms of Service. By accepting Vercel's terms, this addendum applies automatically and governs the processing of personal data in accordance with GDPR Art. 28.

Server location

Vercel runs the server-side functions of our web application (including the APIs, the AI assistant and the regular calendar synchronization) on its server infrastructure. Vercel delivers static content via its global network; your request is first received by the nearest Vercel location, which may be outside the EU.

Data processed:

Purpose:

The processing serves to detect, analyze, and resolve errors, to ensure the technical stability and security of the service, and to improve application performance.

Legal basis:

The processing is based on our legitimate interest in the secure, stable, and reliable operation of the application (Art. 6 para. 1 lit. f GDPR).

Privacy measures:

Before transmission to Sentry, all our apps apply automatic scrubbing that removes sensitive key values (e.g., tokens, passwords, session identifiers) from error reports. For native crashes of the mobile and desktop apps (minidumps) outside the JavaScript runtime, the crash report is captured directly by the native Sentry SDK; the scrubbing described does not apply to the same extent. Session replay is not enabled in any of our apps.

Browser security reports (Content Security Policy):

Our website sends security headers to your browser, including a Content Security Policy. It currently runs in report-only mode and does not block any content. If a page loads content from a source that is not allowed, your browser may automatically send a report to Sentry's security endpoint. Such a report contains the affected page address, the blocked address, the violated rule, technical details of your browser (e.g. user agent) and the IP address it is sent from. We use these reports only to detect misconfigurations and attacks (e.g. injected scripts); the legal basis is Art. 6 para. 1 lit. f GDPR.

Cookies and storage:

To correlate error reports, Sentry may use local storage or session mechanisms on your end device according to the provider. We do not enable Session Replay; whether Sentry sets cookies depends on the SDK and browser.

Retention period:

Error and performance data is stored according to the retention periods configured in our Sentry project and is subsequently deleted or anonymized (see Sentry documentation; specific periods may be set in the project dashboard).

Third country transfer:

Functional Software, Inc. is based in the USA. Transmission takes place via EU regional ingestion (ingest.de.sentry.io); processing in the USA cannot be ruled out. Data transfer is based on the EU Commission's standard contractual clauses (Art. 46 para. 2 lit. c GDPR). Sentry processes the data as our processor (Art. 28 GDPR).

What happens when you sign in with GitHub:

When you click 'Sign in with GitHub', you are redirected to GitHub's servers. GitHub authenticates your identity and sends us a token along with basic profile information. We do not receive your GitHub password.

Data received from GitHub:

Purpose:

The data is used exclusively for authentication and to create and manage your user account in Self-Engine.

Legal basis:

Processing is based on contract performance (Art. 6 para. 1 lit. b GDPR) because sign-in is required to set up and use your account.

Third country transfer:

GitHub Inc. is based in the USA. Data transfer is based on the EU Commission's standard contractual clauses (Art. 46 para. 2 lit. c GDPR). GitHub is additionally certified under the EU-U.S. Data Privacy Framework.

What happens when you sign in with Google:

When you click 'Sign in with Google', you are redirected to Google's servers. Google authenticates your identity and sends us a token along with basic profile information. We do not receive your Google password.

Data received from Google:

Purpose:

The data is used exclusively for authentication and to create and manage your user account in Self-Engine.

Legal basis:

Processing is based on contract performance (Art. 6 para. 1 lit. b GDPR) because sign-in is required to set up and use your account.

Third country transfer:

Google LLC is based in the USA. Data transfer is based on the EU Commission's standard contractual clauses (Art. 46 para. 2 lit. c GDPR). Google is additionally certified under the EU-U.S. Data Privacy Framework.

Scope of access:

Once connected, Self-Engine receives read and write access to your Google Calendar. We read events within a window of roughly one year into the past and one year into the future, and we can create, update, or delete events you create or modify in Self-Engine within your Google Calendar (bidirectional synchronization).

Data processed:

Storage:

The synchronized event data is stored on our Supabase servers (EU region) to enable synchronization and offline use. The Google refresh token required for access is stored exclusively server-side and in encrypted form.

Background synchronization:

As long as the connection exists, our servers periodically reconcile your events with Google Calendar even when you do not have the application open. Synchronization ends as soon as you disconnect the integration.

Purpose:

We process your Google Calendar data to provide the calendar feature you have activated: showing your events in Self-Engine and synchronizing them between Self-Engine and Google Calendar. Beyond that, we use it only for features you switch on yourself: the optional AI assistant (see “AI assistant”) and, where available for your account, connected agents (see “Connected agents”). Which other uses are excluded is set out in the Limited Use paragraph at the end of this section.

AI assistant:

If you have switched on the optional AI assistant, event data may be transmitted via OpenRouter to the AI model in use (provider, model and third-country transfer: see the “AI Assistant (OpenRouter)” section). Without a specific calendar request, the model receives only the number of your events, not their contents. When the assistant queries your calendar, an internal identifier, the title, start and end time, the all-day flag, the status and – if set – the location of the matching events are transmitted; the event description is not transmitted when reading. A description is only part of the transmission when the assistant itself creates or changes an event with a description. Self-Engine carries out such changes only after you confirm them and then synchronizes them with Google Calendar.

Connected agents:

If you have connected an external agent (see the “Connected Agents (MCP)” section), it can, at your instruction, query events and – with write permission – create and change them, including events from Google Calendar. The agent receives the same event fields as the AI assistant; they are transmitted to the provider of the agent you chose (e.g. Anthropic for Claude Code), whose own privacy policy governs its processing. Self-Engine carries out changes made by an agent without an additional in-app confirmation – you approve them in your agent's chat – and then synchronizes them with Google Calendar.

Legal basis:

Processing is based on your consent (Art. 6 para. 1 lit. a GDPR), which you grant by connecting your Google Calendar. Transmission of event data to the AI assistant or to a connected agent is based on your separate consent, given by enabling these features or authorizing the connection. You can withdraw any consent at any time with effect for the future.

Third-country transfer:

Google LLC is based in the USA. The data transfer is carried out on the basis of the European Commission's Standard Contractual Clauses (Art. 46(2)(c) GDPR). Google is additionally certified under the EU-US Data Privacy Framework.

Withdrawal and disconnection:

You can disconnect the integration at any time in the settings. When you disconnect and when you delete your account, we revoke the granted access at Google and delete the stored tokens; synchronization then ends. You can additionally revoke the granted access at any time directly in your Google account under the security settings.

Scope of access:

The connection uses the iCloud CalDAV protocol. To connect, you enter your Apple ID and an app-specific password generated in your Apple account; we never receive your actual Apple ID password. Self-Engine thereby receives read and write access to the calendars of your iCloud account. By default, only calendars you own and are allowed to edit are synchronized; calendars shared with you and subscribed calendars are initially disabled. You choose which calendars are synchronized in the settings. We read events within a window of roughly one year into the past and one year into the future, and we can create, update, or delete events you create or modify in Self-Engine within your Apple Calendar (bidirectional synchronization).

Data processed:

Storage:

The synchronized event data is stored on our Supabase servers (EU region) to enable synchronization and offline use. Your Apple ID and the app-specific password are stored exclusively server-side and in encrypted form and are used solely to communicate with the iCloud servers.

Background synchronization:

As long as the connection exists, our servers periodically reconcile your events with iCloud even when you do not have the application open. Synchronization ends as soon as you disconnect the integration.

Purpose:

Processing serves to provide the calendar feature you have activated and to synchronize your events between Self-Engine and Apple Calendar. If you use the optional AI assistant or connected agents, the same details as in the “Google Calendar Integration” section under “AI assistant” and “Connected agents” apply to events from this synchronization.

Legal basis:

Processing is based on your consent (Art. 6 para. 1 lit. a GDPR), which you grant by connecting your Apple Calendar.

Third-country transfer:

Apple Inc. is based in the USA. Your calendar data resides in your iCloud account with Apple, which you use under your own agreement with Apple; Apple processes this data as an independent controller under Apple's privacy policy. During synchronization, our servers retrieve event data from the iCloud servers and transmit changes you make in Self-Engine to them. According to its own information, Apple bases international transfers of personal data from the EEA on the European Commission's Standard Contractual Clauses (Art. 46(2)(c) GDPR).

Withdrawal and disconnection:

You can disconnect the integration at any time in the settings. Doing so deletes the stored credentials and ends synchronization. You can additionally revoke the app-specific password at any time in your Apple account, after which no further access is possible.

Data collected:

Purpose of processing:

Legal basis:

The processing is carried out for the performance of the user agreement (Art. 6 para. 1 lit. b GDPR). The processing of technical data for security purposes is based on our legitimate interest in the security of the service (Art. 6 para. 1 lit. f GDPR).

Third country transfer:

Clerk, Inc. is based in the USA; your account data is stored there (Clerk does not offer EU data residency). Data transfer is based on the EU Commission's standard contractual clauses (Art. 46 para. 2 lit. c GDPR).

Purpose:

The record shows which version of the Terms you accepted and when, which version of the Privacy Policy you acknowledged and when, and that you confirmed your minimum age.

Legal basis:

Art. 6 para. 1 lit. f GDPR (legitimate interest in demonstrable documentation and in defending legal claims) and Art. 6 para. 1 lit. b GDPR insofar as the record concerns the conclusion of the contract of use.

Request for an early start:

If you tick the box for an early start during ordering, we store this request with its time, the chosen plan, the version of the statement and the language in the non-public account data at Clerk. The record serves to prove the pro-rata amount in case of withdrawal and to repeat the request in the contract confirmation (Art. 6 para. 1 lit. b, c and f GDPR).

Retention:

We keep the records for as long as your account exists; they are deleted when the account is deleted.

Processed data:

Purpose of processing:

Legal basis:

The processing is carried out for the performance of the subscription contract (Art. 6 para. 1 lit. b GDPR). Where we store billing and transaction data due to statutory retention obligations, this is based on Art. 6 para. 1 lit. c GDPR. Processing for fraud prevention is based on the legitimate interest in secure payment processing (Art. 6 para. 1 lit. f GDPR). For fraud prevention and compliance with its own legal obligations (e.g. anti-money-laundering), Stripe processes data in part as an independent controller.

Cookies and identifiers during payment:

During the payment process, Stripe may use technically necessary cookies and similar identifiers for fraud prevention and the secure execution of the payment. These are required for the payment processing you have explicitly requested (Section 25 (2) no. 2 TDDDG).

Third country transfer:

Stripe may transfer personal data to Stripe, Inc. in the USA. Data transfer is based on the EU Commission's standard contractual clauses (Art. 46 para. 2 lit. c GDPR); Stripe is also certified under the EU-US Data Privacy Framework. Subscription and billing metadata is additionally processed by Clerk, Inc. (USA); for details, see the section "Authentication and Account Management (Clerk)".

Retention period:

We store billing and transaction data for as long as this is necessary for the administration of the subscription and as long as statutory retention obligations (in particular under commercial and tax law) apply. After these periods expire, the data is deleted.

Data collected:

Purpose of processing:

Legal basis:

The processing is carried out for the performance of the user agreement (Art. 6 para. 1 lit. b GDPR). The processing of technical data for security purposes is based on our legitimate interest in the security of the service (Art. 6 para. 1 lit. f GDPR).

Data location:

Your data is stored in a Supabase project in the AWS region eu-central-1 (Frankfurt am Main, Germany).

Assistant memories:

The content data stored in Supabase also includes the memories of the AI assistant (see “AI memory” in the AI assistant section).

Third country transfer:

Supabase Pte. Ltd. is a company based in Singapore. Data transfers to third countries are based on the EU Commission's standard contractual clauses (Art. 46 para. 2 lit. c GDPR). Despite the use of EU servers, administrative access from Singapore may occur. Supabase includes standard contractual clauses (SCCs) in their terms of service to ensure appropriate safeguards for international data transfers.

Security:

All data is encrypted both in transit (TLS/SSL) and at rest. Access to your data is restricted to your own user account via access rules (Row Level Security).

How it works:

PowerSync creates a local SQLite database on your device with data released for your account. Changes you make are written directly to our Supabase database (EU region). In production we use PowerSync Cloud (Journey Mobile, Inc.) as a processor: PowerSync reads data released for your account from Supabase, holds it in a cache, and synchronizes it with your devices. Transfer to PowerSync Cloud may involve third countries; it is based on the EU Commission's standard contractual clauses (Art. 46 para. 2 lit. c GDPR).

Locally stored data:

Storage location:

In the web and desktop apps the local database is held in browser storage (IndexedDB); in the mobile apps in SQLite on the device. The web app may also store AI assistant thread history in localStorage. Local application data, including the AI assistant history, is cleared on logout in the web app; the mobile app also clears its local database on logout.

Security:

The local database uses your browser's security mechanisms. When you log out or clear your browser data, the local database is also removed.

Legal basis:

Local storage is based on the performance of a contract (Art. 6 para. 1 lit. b GDPR) as it is necessary to provide the application's offline functionality.

Mobile apps (Expo / EAS):

Mobile app updates may be delivered via Expo Application Services (EAS Updates, u.expo.dev, operator: Expo / 650 Industries, Inc., USA). Technical access data (e.g. IP address, device and app version) may be processed. We use EAS Observe (650 Industries, Inc., USA) for performance and stability metrics, which may process navigation and startup timings. Local app data is stored in SQLite; authentication and session data may be held in Expo SecureStore.

Desktop app (macOS):

The desktop app (macOS) displays the web application in its own window; the statements on the web application (including IndexedDB/localStorage) apply accordingly. In addition, the desktop app checks GitHub (GitHub, Inc., USA) for published updates and downloads them with your confirmation (download also via our website); your IP address is transmitted to GitHub. On native crashes the desktop app may send minidump reports to Sentry; the scrubbing described in the Sentry section does not apply to the same extent.

App stores (Apple App Store / Google Play):

If you obtain our mobile apps via the Apple App Store or Google Play, Apple or Google process data as independent controllers in connection with download, updates, billing (where via the store), and device management under their respective privacy policies. We generally do not receive complete payment data from the store operator.

Legal basis:

Art. 6 para. 1 lit. b GDPR (providing the app you use and updates) and Art. 6 para. 1 lit. f GDPR (legitimate interest in secure updates and stability/performance analysis).

What happens when you use it:

When you send a message to the assistant, your input is transmitted server-side via OpenRouter to the selected AI model in order to generate a response. Access to the AI model takes place exclusively via our server; the access key required for OpenRouter is not transmitted to your browser.

Data processed:

Purpose:

Processing serves to provide the assistant function you have enabled, in particular to answer your requests and to prepare and carry out the actions you confirm. For data from Google Calendar, the restrictions in the “Google Calendar Integration” section apply in addition.

Legal basis:

Transmission of your inputs to the AI model is based on your consent (Art. 6 para. 1 lit. a GDPR), which you grant by enabling the AI assistant in the settings. You can withdraw your consent at any time with effect for the future by disabling the AI assistant again. We process usage metadata stored server-side (number of requests, token consumption, and estimated costs) on the basis of our legitimate interest in abuse and cost control (Art. 6 para. 1 lit. f GDPR).

AI models and providers used:

In production we currently use the “Claude Haiku 5.5” model by default (OpenRouter identifier anthropic/claude-haiku-5.5). It was developed by Anthropic, PBC, San Francisco, USA. Anthropic is not our processor, and we do not transmit your data directly to Anthropic. Because we require Zero Data Retention, OpenRouter — according to OpenRouter (as of October 2026) — does not forward requests for this model to Anthropic itself but to platforms on which the model is operated without data retention: currently Google Cloud Vertex AI (Google) or Amazon Bedrock (Amazon Web Services). According to OpenRouter, these platforms do not store your inputs or use them for training; according to the platform operators, Anthropic has no access there to your inputs and the responses. The platforms available for a model may change; what remains decisive is that OpenRouter only selects providers with Zero Data Retention. If we use a different model via OpenRouter in individual cases, the same restriction applies.

AI memory:

You can give the assistant short memories so that it knows things across conversations (e.g. “Project Alpha is billed to customer Müller” or “keep answers short”). You create memories yourself, or the assistant proposes them; it does not extract memories from your conversations without your instruction or confirmation. There are at most 50 memories of at most 500 characters each.

Memories are stored like your other content in our database (Supabase, eu-central-1) and synchronized with your devices via PowerSync. AI memory is switched off by default, even if you saved memories before. Such memories stay stored but are only used once you switch memory on; you can view, edit and delete them while memory is off, and they are included in the data export. Only once you switch it on in the web app under Settings → AI assistant → Memories do we add all active memories to the instructions for the AI model on every request; they therefore reach the model via OpenRouter (Zero Data Retention as above). We point this out next to the switch. While memory is off, we send no memories, the assistant cannot read or create memories, and connected agents cannot read them. You can switch it off again at any time. You can edit or delete memories at any time; deleted memories first go to the trash and are removed for good when you empty the trash or delete your account. Connected external agents may at most read memories, never create or change them.

The legal basis for sending memories to the AI model is your consent by switching AI memory on (Art. 6 para. 1 lit. a GDPR); you withdraw it by switching it off. Storage is based on the performance of the contract (Art. 6 para. 1 lit. b GDPR).

Storage and logging:

The history of your conversations with the assistant stays in your browser (localStorage) and is not synchronized with our servers. We delete it from the browser when you log out. For transmission to the AI model we enforce OpenRouter's Zero Data Retention on every request; according to OpenRouter, your inputs and the responses are neither stored nor used for training by the intermediary or the hosting provider. If no such provider is available, the request is not carried out. We have not enabled OpenRouter's optional prompt logging.

Log of tool calls: we log every call of a tool by the assistant (e.g. “create time entry” or “list events”) on our server, including refused calls. We store the time, tool, outcome, duration, the arguments passed (shortened, e.g. texts to 200 characters) and the result message, so that you can see under Settings what the assistant did. We delete arguments and result message after 30 days and the entry itself after 90 days; the log is deleted entirely with your account. The legal basis is Art. 6 para. 1 lit. b GDPR where we show you the history in the settings, and otherwise Art. 6 para. 1 lit. f GDPR (traceability, security and abuse control).

We store usage metadata (e.g. number of requests, token consumption and estimated costs) to enforce the monthly quota and prevent abuse for as long as your account exists, in monthly cost windows. For quality feedback on an assistant reply we always store your rating, the selected reason (for “not helpful”), the model identifier and the names and outcomes of executed tools (Art. 6 para. 1 lit. f GDPR). Only if you explicitly agree do we additionally store your message and the assistant reply (Art. 6 para. 1 lit. a GDPR). Feedback data is deleted with your account.

Third-country transfer:

OpenRouter, Inc. is based in the USA. The transfer of data to OpenRouter takes place on the basis of the European Commission's standard contractual clauses (Art. 46 para. 2 lit. c GDPR). OpenRouter engages the hosting providers to which it forwards your request (for the default model currently Google or Amazon Web Services) as its own sub-processors; we do not transmit your data directly to these providers or to Anthropic. Depending on the selected endpoint, processing may take place in the EU, in the USA or — for globally routed endpoints — in further countries outside the EU/EEA; due to the Zero Data Retention requirement, it takes place — according to OpenRouter — without permanent storage.

No automated decision-making:

The AI assistant makes suggestions and prepares actions. By default it changes your data only after your confirmation. You can turn this confirmation off per data type under Settings → AI assistant → Permissions; permanent deletions always ask. There is no solely automated decision producing legal effects within the meaning of Art. 22 GDPR. AI-generated content may be incomplete or incorrect and should be reviewed by you.

Data processed:

Purpose and legal basis:

Transfer of content to the connected agent is based on your consent (Art. 6 para. 1 lit. a GDPR) by enabling the feature and authorizing the connection. Logging of tool calls serves security and abuse detection and is based on our legitimate interest (Art. 6 para. 1 lit. f GDPR). You can revoke connections at any time in settings; stored tokens are deleted.

Recipients:

Clerk, Inc. (OAuth authorization and token revocation) and the provider of the agent you connect (e.g. Anthropic for Claude Code), whose privacy policy applies to content processed there.

Changes by agents:

Within the permission you granted (read only, or read and write), a connected agent can create and change entries without an additional confirmation in Self-Engine; you approve them in your agent's chat. Changed events are then synchronized with your connected calendars. For data from Google Calendar, the restrictions in the “Google Calendar Integration” section apply in addition.

Essential Cookies

We use essential cookies that are technically necessary for the operation of the website. These cookies serve exclusively to provide our services and cannot be deactivated.

Essential cookies used:

Processing is based on legitimate interest (Art. 6 para. 1 lit. f GDPR) in the technically error-free and secure provision of our website.

Browser settings:

You can set your browser to inform you about the setting of cookies and only allow cookies on a case-by-case basis, exclude the acceptance of cookies for certain cases or in general, and activate the automatic deletion of cookies when closing the browser. Disabling cookies may limit the functionality of this website.

USA (Vercel):

Vercel Inc. is based in the USA. Data transfer is based on the EU Commission's standard contractual clauses (Art. 46 para. 2 lit. c GDPR). Vercel has implemented additional technical and organizational measures to ensure an adequate level of data protection.

USA (Clerk):

Clerk, Inc. is based in the USA; your account data is stored there (Clerk does not offer EU data residency). Data transfer is based on the EU Commission's standard contractual clauses (Art. 46 para. 2 lit. c GDPR).

USA (Stripe):

As part of payment processing, Stripe may transfer personal data to Stripe, Inc. in the USA. Data transfer is based on the EU Commission's standard contractual clauses (Art. 46 para. 2 lit. c GDPR). Stripe is also certified under the EU-US Data Privacy Framework.

USA (OpenRouter):

If the AI assistant is enabled, OpenRouter, Inc. may process personal data in the USA and forward it to hosting providers of the AI model in use, which OpenRouter engages as sub-processors (for the default model currently Google or Amazon Web Services). Data transfer is based on the EU Commission's standard contractual clauses (Art. 46 para. 2 lit. c GDPR). We use OpenRouter's Zero Data Retention option, so that — according to OpenRouter — processing takes place without permanent storage. Depending on the endpoint, processing may also take place in further third countries outside the EU/EEA. For details, see the "AI Assistant (OpenRouter)" section.

USA (Sentry):

As part of error and performance monitoring, Functional Software, Inc. (Sentry) may process personal data in the USA even when transmission takes place via EU regional ingestion (ingest.de.sentry.io). Data transfer is based on the EU Commission's standard contractual clauses (Art. 46 para. 2 lit. c GDPR). For details, see the "Error and Performance Monitoring (Sentry)" section.

USA (Apple):

When your Apple Calendar is connected, our servers exchange event data with the iCloud servers of Apple Inc. Apple processes your iCloud data as an independent controller under your own agreement with Apple and, according to its own information, bases international transfers on the European Commission's Standard Contractual Clauses (Art. 46(2)(c) GDPR). For details, see the "Apple Calendar Integration (iCloud)" section.

Singapore (Supabase):

Although your data is stored on EU servers, Supabase Pte. Ltd. is based in Singapore. Administrative access from Singapore may occur. Data transfer is based on standard contractual clauses (Art. 46 para. 2 lit. c GDPR).

USA / third countries (PowerSync Cloud):

For offline synchronization, Journey Mobile, Inc. (PowerSync Cloud) may be used as a processor. Data transfer is based on the EU Commission's standard contractual clauses (Art. 46 para. 2 lit. c GDPR).

USA (Expo / 650 Industries):

For mobile app updates and EAS Observe, 650 Industries, Inc. (Expo) may process personal data in the USA. Data transfer is based on the EU Commission's standard contractual clauses (Art. 46 para. 2 lit. c GDPR).

USA (GitHub):

When downloading or updating the desktop app via GitHub, GitHub, Inc. may process personal data (e.g. IP address) in the USA. Data transfer is based on the EU Commission's standard contractual clauses (Art. 46 para. 2 lit. c GDPR). GitHub is also certified under the EU-US Data Privacy Framework.

USA (Resend):

For email delivery (feedback, contract, withdrawal, cancellation, and deletion confirmations) we use Resend (Plus Five Five, Inc., 2261 Market Street #5039, San Francisco, CA 94114, USA). Data transfer is based on the EU Commission's standard contractual clauses (Art. 46 para. 2 lit. c GDPR) and a data processing addendum with Resend.

Third countries (connected agents):

When agent connections are enabled, content may be transferred to the provider of the agent you connect (e.g. Anthropic for Claude Code) in third countries. Their privacy policies apply; where we act as controller, we base transfers on your explicit consent (Art. 49 para. 1 lit. a GDPR). Third countries may not offer a level of data protection comparable to the EU; in particular, authorities there may gain access to the data.

Data processed:

Purpose:

The processing is carried out to receive, review, and respond to feedback, to analyze and resolve reported issues, and to improve the stability and usability of our application.

Legal basis:

The processing is based on Art. 6 para. 1 lit. f GDPR. Our legitimate interest lies in the efficient handling of feedback, troubleshooting, and protecting the feedback form against abusive use. If you voluntarily provide a contact email address, we use it solely to assign your feedback and contact you if follow-up questions are necessary.

Email delivery via Resend:

We use Resend, a service of Plus Five Five, Inc., 2261 Market Street #5039, San Francisco, CA 94114, USA, as a processor to send emails related to the feedback form, contract confirmations, confirmations of receipt of withdrawals, cancellation confirmations, and account deletion confirmations. The respective content (feedback messages including optional screenshots, contract, withdrawal and cancellation data and confirmation texts, or the recipient email address and the account deletion confirmation text) is transmitted to Resend for this purpose. Processing in the USA cannot be ruled out. According to its own information, Resend provides appropriate safeguards for international data transfers, in particular through a Data Processing Addendum and the EU Commission's standard contractual clauses (Art. 46 para. 2 lit. c GDPR).

Contract confirmations:

After you conclude a paid subscription, we send a contract confirmation to your account email address. For this we process your email address, plan, price, billing period, date of conclusion and, if given, your request for an early start with its time. We learn of the occasion from Clerk via an automatic notification (webhook). A copy of the same email goes as a blind copy to our own mailbox; we keep it as proof that, and with which content, we sent the confirmation (Art. 6 para. 1 lit. c and f GDPR). The legal basis is our legal obligation under § 312f para. 2 BGB and the performance of the contract (Art. 6 para. 1 lit. b and lit. c GDPR).

Withdrawal declarations:

If you declare a withdrawal via the “Withdraw from contract” button, we store your declaration in our database (Supabase): name, the contract details, your email address, the time of receipt and the time of the confirmation of receipt and, if you are signed in, your account ID. We send you a confirmation of receipt by email with the content of your declaration and the date and time, and forward the declaration to us by email. The legal basis is our legal obligation under § 356a BGB and the handling of the withdrawal (Art. 6 para. 1 lit. b and lit. c GDPR) and our legitimate interest in proof (Art. 6 para. 1 lit. f GDPR).

The withdrawal declaration remains stored as proof even after your account is deleted and is not part of the data export.

Cancellation confirmations:

When you submit a cancellation declaration via our cancellation page, we send you a receipt confirmation by email and forward your declaration to us. In doing so, we process in particular your name, email address, type of cancellation, requested termination date, and — for extraordinary cancellation — the reason you provide.

Legal basis (cancellation):

The processing of cancellation data is carried out to receive and handle your cancellation declaration and to fulfill statutory information obligations (Art. 6 para. 1 lit. b and lit. c GDPR).

Account deletion confirmation:

When you delete your user account in the web or mobile app, we send a confirmation of the deletion to the email address associated with your account. Apart from your email address, the email contains no further personal data. The processing is carried out to wind up the user agreement and on the basis of our legitimate interest in informing you about a security-relevant change to your account (Art. 6 para. 1 lit. b and lit. f GDPR).

Important notice (feedback):

Please include only the information necessary for your feedback. Screenshots may show personal or confidential content — attach images only when needed to describe the issue.

Retention period:

We generally store feedback content only for as long as necessary to process your feedback and any related follow-up. The identifier used temporarily for rate limiting is processed only for the duration of the relevant protection window in volatile server memory and is then discarded.

Overview:

Our security measures include:

Contact for data protection inquiries:

For questions about data protection or to exercise your rights, please contact: kontakt@self-engine.com

Bavarian State Office for Data Protection Supervision (BayLDA)

Promenade 18 91522 Ansbach Germany

Phone: +49 (0)981 180093-0

Email: poststelle@lda.bayern.de

Website: https://www.lda.bayern.de

Data export:

As long as you have access to the application (subscription or tester access), you can download an export of your data stored with us as a JSON file in the account settings of the web application at any time (self-service). Without active access – or if you prefer – we send you a copy on request to kontakt@self-engine.com.

Account deletion:

You can delete your user account and all associated data at any time in the account settings of the web and mobile apps or by emailing us. Withdrawal declarations, which we keep as proof, are excepted (see “Withdrawal declarations”). Before deletion in the web or mobile app is carried out, we immediately terminate all running subscriptions except the free base plan (immediate end). Deletion is also possible without a subscription (via the subscription page of the web application). If that termination fails, account deletion is aborted and your account remains. No refunds are granted; any remaining paid period ends with the immediate termination. When the account is deleted, we revoke access to a connected Google Calendar at Google and delete the stored tokens. After successful deletion, your personal data will be removed from our production systems. We send email confirmation for account deletion in the web and mobile apps (see the section "Feedback, Contract, Withdrawal, Cancellation, and Account Deletion Emails (Resend)"). Backup copies are overwritten as part of regular backup cycles (see retention periods), unless legal retention obligations apply.

Retention periods:

Deleted data is removed from production systems as promptly as technically and organizationally feasible. Backups and recovery media are overwritten or deleted in line with the applicable backup and retention cycles, unless legal retention obligations (for example under tax law) require longer storage.

Right to information

You have the right to obtain confirmation as to whether personal data concerning you is being processed and, if so, to receive information about this personal data and further information in accordance with Art. 15 GDPR.

Right to rectification

You have the right to request the correction of inaccurate personal data concerning you and, if necessary, the completion of incomplete personal data (Art. 16 GDPR).

Right to erasure ('right to be forgotten')

You have the right to request the deletion of your personal data under the conditions of Art. 17 GDPR. This right includes, among other things, the right to have data deleted if the personal data is no longer necessary for the purposes for which it was collected.

Right to restriction of processing

You have the right to request the restriction of processing under the conditions of Art. 18 GDPR.

Right to data portability

You have the right to receive the personal data concerning you that you have provided to us in a structured, commonly used and machine-readable format and to transmit this data to another controller (Art. 20 GDPR).

Right to object

You have the right to object at any time to the processing of your personal data on the basis of Art. 6 para. 1 lit. e or f GDPR for reasons arising from your particular situation (Art. 21 GDPR).

Right to lodge a complaint with a supervisory authority

You have the right to lodge a complaint with a supervisory authority, in particular in the Member State of your habitual residence, place of work or place of the alleged infringement, if you consider that the processing of your personal data infringes the GDPR (Art. 77 GDPR).

Right to withdraw consent

If you have given your consent to the processing of your data, you can revoke this consent at any time with effect for the future. The lawfulness of the processing carried out on the basis of the consent until revocation is not affected by this.