Privacy Policy for Keeption

Last updated: 14 October 2026 · TestFlight beta

1. Who is responsible for your personal data

The controller responsible for processing your personal data in connection with Keeption is:

Michelle Bründler
Müllerstrasse 5
8004 Zurich
Switzerland
Privacy contact: privacy@keeption.app

This policy explains how we process personal data when you use our website and iOS app, including the TestFlight beta. Keeption helps you save, organise and find selected content.

2. What data we process and why

Sign-in and your account

You sign in using Sign in with Apple. We receive the Apple identifier required for sign-in and information supplied by Apple, particularly your email address and, where provided, your name. If you choose to hide your email address, we receive the relay address provided by Apple. We use this information to create and manage your account and associate your saved content with it. Authentication credentials and session information allow you to stay signed in.

Your saved content

We process content you choose to provide to Keeption, such as links, text, photos, screenshots and supported media. This may include source URLs, titles, descriptions, import timestamps, file information, information about the source and publicly accessible details about shared posts, such as the author's name, username, caption or transcript.

We also store collections, categories, tags, notes and other entry details that you create or edit, together with their status and associations. Automatically identified information, such as summaries, places, addresses and topic classifications, becomes part of your saved content. This information may be inaccurate.

Data is processed and stored on your device and in our backend for synchronisation. Keeption does not indiscriminately access your entire photo library, contacts or browsing history. Processing relates to the content you select or share.

Saved content may include personal data about other people. Please carefully consider what you import and thereby submit to the AI processing described below.

Keeption is not intended for sensitive personal data. Please do not upload medical records, diagnoses, treatment information or other sensitive personal information about yourself or others.

Automated analysis using artificial intelligence

We use the OpenAI API to identify, structure and enrich imported content. Analysis may take place automatically as part of an import. Depending on the content, we send text, links, contextual information, publicly accessible post information and selected images or screenshots. Images may be made available through a temporary access link. For supported, accessible media, audio may be sent to OpenAI for transcription.

Analysis may use web search to obtain additional information. Search terms derived from the content may be disclosed to the search service and its participating providers. Processing therefore extends beyond your saved collection.

When you use natural-language search, your query and available filter labels from your collection, such as categories, tags or place names, are sent to OpenAI to identify suitable filters.

According to OpenAI's published terms, API data is not used to train its models by default unless data sharing is explicitly enabled. The app disables regular response storage using the API parameter store: false. This does not mean that no data is retained: security logs and other service-specific retention may still apply. OpenAI generally specifies up to 30 days for standard abuse-monitoring retention for the Responses API, subject to legal requirements and documented exceptions. See OpenAI's API data controls.

AI helps organise and retrieve content. We do not use it to make solely automated decisions about you that have legal or similarly significant effects.

Websites, previews and place information

To import and enrich shared links, Keeption or our servers may access the relevant websites and platforms to retrieve titles, preview images, descriptions or accessible media. These providers receive the technical information normally associated with a network connection. Requests from your device may disclose your IP address; server-side requests disclose the server's IP address. The requested URL itself may also contain personal data.

Keeption may use Apple's geocoding service to determine coordinates for saved place addresses. The relevant address is sent to Apple. This locates a saved place and does not require continuous collection of your device's current location.

When you open an external link or a place in a mapping service, that provider receives the information passed to it and connection data. Its own processing is governed by its privacy policy.

Technical operation, security and troubleshooting

Sign-in, synchronisation and server requests generate technical data, such as IP addresses, timestamps, request and error information, and technical identifiers. We and our service providers use this information to operate, secure and troubleshoot the service.

Account-specific counters are maintained to limit search requests. Our functions may log technical errors and AI usage information. Keeption also stores a limited diagnostic history on your device, containing up to 100 events, such as file type, file size, processing duration and import success or failure status.

The version described here does not use separate advertising or product-analytics tracking SDKs.

Permissions and notifications

The app requests the necessary permissions for camera access and other features protected by iOS. When you select photos, Keeption receives the content you choose. Reminder times are synchronised with your account. If notifications are allowed, reminders are delivered through Apple's push notification service. A notification contains the name of the relevant Thing and technical destination identifiers. If several Things are due at the same time, it contains the first name and the number of additional Things. These names may appear on your lock screen; you can restrict previews in the iOS notification settings. Without notification permission, reminders remain visible in the app. You can change permissions and notifications in your iOS settings.

TestFlight and support

Apple processes its own data in connection with TestFlight, such as installation, usage, crash and submitted feedback data. Where Apple makes beta reports or feedback available to us, we use them to support testing and troubleshoot issues. Apple's information in TestFlight and its privacy notices also apply.

If you contact us, we process your contact details and message to handle your request. Screenshots or diagnostic information you provide may contain additional personal data.

3. Who receives data

We use the following services in particular:

Technical service providers may use subprocessors. Your saved collection is not intended for public publication. Disclosure may also be necessary to comply with a legal obligation or establish, exercise or defend legal claims.

4. International processing

Keeption uses service providers that may process personal data outside Switzerland. Our database location does not determine all processing locations: AI analysis, support, operational services and subprocessors may involve international transfers.

Supabase

Our Supabase project is hosted in Frankfurt, Germany (AWS region eu-central-1). Supabase Pte. Ltd. is based in Singapore. Its published subprocessor list includes providers in the United States, Hungary and Singapore. The countries listed for those companies do not necessarily identify every physical processing location, and not every listed provider receives your saved content. Depending on the service involved, processing outside the hosting region may be necessary for support, infrastructure, security, operations and content delivery.

Supabase's Data Processing Addendum incorporates Standard Contractual Clauses (SCCs), including adaptations for Swiss data protection law, for the transfers covered by that addendum. Further information is available in Supabase's DPA, data residency and transfers information and subprocessor list.

OpenAI

Keeption's OpenAI API project is configured with Global residency. Our current integration does not restrict AI processing to Switzerland or Europe. Content submitted for analysis, transcription or natural-language filtering may be processed in the United States and other locations used by OpenAI and its relevant subprocessors.

OpenAI's published DPA provides for processing of Swiss and EEA personal data by OpenAI Ireland Limited, regardless of the applicable contracting party. It provides for safeguards for onward transfers, including SCCs or applicable adequacy decisions. See OpenAI's DPA, section 4 and its subprocessor list. These arrangements do not constitute a commitment to European-only processing. Our optional OpenAI data-sharing settings are disabled; this is separate from processing location and retention.

Apple

The Apple features described in section 2 may involve international processing. Apple's published privacy policy identifies Apple Distribution International Limited in Ireland as the controller for personal data relating to individuals in Switzerland and states that personal data is generally stored by Apple Inc. in the United States. Apple describes the use of SCCs for international transfers of personal data collected in Switzerland. Its own processing is subject to Apple's Privacy Policy and the notices for the relevant services.

Web search, source websites and external services

Retrieving shared links and media, using web search, or opening an external website or mapping service may disclose the information described in section 2 to providers outside Switzerland. The recipient and processing location depend on the source or service involved. This does not mean that all providers receive your entire collection. Their own processing is governed by their respective privacy notices. OpenAI's regional settings do not restrict processing locations of external search or source providers.

Information about safeguards

Where an applicable adequacy decision covers a transfer, that decision may provide its legal basis. For other transfers, appropriate safeguards may include the contractual arrangements described above and any additional measures required by applicable law. You can contact us using the details in section 1 to request information about safeguards relevant to your data and, where available, a copy, subject to necessary redactions.

5. Retention and deletion

Your account and saved collection

We retain your account information and saved content for as long as needed to provide your account and collection, unless you delete the relevant content or your account as described below. Signing out or uninstalling the app does not automatically delete your cloud account or its contents. Legal obligations, security incidents or legal claims may require further retention of specific data for those purposes; they do not automatically require us to retain your entire collection.

Deleting individual Things and original sources

Important for this beta: When you delete a Thing, its stored content is removed from the active database after successful synchronisation. To prevent older devices or devices that have been offline for an extended period from restoring it, a deletion record containing the entry ID, storage-space ID and timestamp, but no Thing content, remains until the account is deleted. Original sources in the Inbox archive, such as your photo or original text, remain independently and may also be used by other Things. Deleting a Thing therefore does not automatically delete its original source. Logs and backups may be deleted later.

Deleting your account

Account deletion is available in Settings under “Privacy & account”. After you authorise again with Apple, the Apple sign-in authorisation is revoked and your cloud account, associated content, private original files and deletion records are removed. The process reports an error if deletion cannot be completed. Signing out or uninstalling the app does not automatically delete your cloud account or the data stored there.

After the app receives confirmation of successful account deletion, it clears the account's local app data, pending uploads and notifications on that device. An offline device cannot be remotely wiped and may retain a local copy until it reconnects and the app updates its account state or clears that copy. Previously delivered notifications and copies outside Keeption's control are not retroactively erased by deleting database entries.

Diagnostics, provider logs and backups

The local import diagnostic history is limited to 100 events; older events are replaced as new events are recorded. Technical provider logs and backups follow separate retention arrangements and are not necessarily erased immediately when you delete a Thing or your account. OpenAI retention is described in section 2.

Transition from beta to public launch

Your account and saved content from the beta will be carried over to the regular service at public launch. The end of the beta does not itself trigger deletion of your account or collection. The retention and deletion rules described in this policy continue to apply.

6. Protecting your data

We use encrypted network connections and account-based access controls. Imported files are stored in private storage. Our service providers may access the data required for processing. The cloud and AI processing described here therefore does not use end-to-end encryption under which only you can decrypt the content.

7. Your rights

Under applicable data protection law, you may in particular request access to your personal data and correction of inaccurate data. To the extent provided by law, you may request deletion or restriction of processing and, where applicable, object to processing or request a copy or transfer of your data. Where processing is based on your consent, you may withdraw it with effect for the future.

To exercise your rights, contact us using the details in section 1. To protect your data, we may require an appropriate verification of your identity. You may also contact the competent data protection authority, including the Federal Data Protection and Information Commissioner (FDPIC) in Switzerland.

8. Additional information where the GDPR applies

Where processing in connection with Keeption is subject to the GDPR, the following additional information applies.

Where the European General Data Protection Regulation applies, processing necessary to provide the agreed app features is based on Article 6(1)(b) GDPR. Necessary processing for operational security, abuse prevention and troubleshooting may be based on Article 6(1)(f) GDPR; our legitimate interests are providing a secure and reliable service. Processing required by law is based on Article 6(1)(c) GDPR. Where consent is required and obtained for particular processing, that processing is based on Article 6(1)(a) GDPR.

Information required for sign-in and the relevant features is functionally necessary: account-based cloud use is not possible without sign-in, and server-side AI analysis is not possible without transmitting the selected content. You can choose not to use optional camera and notification features.

Optional AI processing, including the related web search and source retrieval described in section 2, is based on your consent under Article 6(1)(a) GDPR. You can allow this processing in the app or choose to use Keeption without AI. You can withdraw your consent in Settings under “Privacy & account”. Withdrawal stops future AI processing but does not affect the lawfulness of processing carried out before withdrawal; requests already sent cannot be recalled. International transfers are addressed separately in section 4; allowing AI processing does not replace the transfer safeguards described there.

Keeption is not intended for the sensitive personal data described in section 2. The AI permission is not a request for explicit consent to process special categories of personal data under Article 9 GDPR.

You may lodge a complaint with a supervisory authority in the EU Member State of your habitual residence, place of work or the alleged infringement. Where we rely on legitimate interests, you may object to processing on grounds relating to your particular situation. Where applicable, you may receive personal data you provided to us in a structured, commonly used and machine-readable format and request its transmission to another controller.

9. Changes

We update this policy when our features or data processing change. The current version will be available at www.keeption.app/privacy/. We will inform you of material changes in an appropriate way.

10. Website beta signup

If you join the Keeption beta list on this website, we process your email address, the time of your request and confirmation, the version of the consent text and technical confirmation and removal tokens. We use these data to verify your request and send beta invitations and testing updates. This does not create a Keeption app account and does not guarantee a TestFlight place. Registration is based on your consent; you may withdraw it at any time using the removal link in your signup email or by contacting privacy@keeption.app.

The beta list is stored in our Supabase project in Frankfurt, Germany, separately from app accounts. Supabase Edge Functions process signup and confirmation requests. To protect the form against abuse, we temporarily process your connection IP address and retain a keyed hash in short-lived rate-limit records, rather than storing the raw IP address in the beta list. Hosting, access and service providers may also process ordinary technical request logs. The international processing information in section 4 applies to Supabase.

We use Resend (Plus Five Five, Inc., United States) to send confirmation emails. Resend receives the recipient address, email content and technical delivery information. The selected sending region is Ireland; this does not restrict data storage to Europe. Resend states that customer data, including message content and delivery logs, are stored in the United States. Its privacy information and Data Processing Addendum describe international-transfer safeguards, including Standard Contractual Clauses. We do not add open-tracking pixels or tracked links to our confirmation emails.

Confirmation links expire after 24 hours. Unconfirmed registrations are removed automatically after seven days without a renewed request. Confirmed entries are retained for beta invitations and testing updates for up to twelve months after confirmation, unless you unsubscribe earlier. Unsubscribing deletes the active beta-list entry. Provider logs and backups may remain subject to their separate retention arrangements. Rate-limit records expire within two days and are removed by routine cleanup.

Our normal support mailboxes are hosted by Hostpoint AG, Switzerland. If you contact hello@keeption.app or privacy@keeption.app, we and Hostpoint process your email and the information you provide to handle your request. TestFlight invitations and participation involve Apple as described above.

11. Website hosting

The public website is hosted on Cloudflare Pages. Cloudflare, Inc. (United States) and its service providers process technical connection data, such as IP addresses, requested URLs, timestamps and browser information, to deliver the website, secure it and prevent abuse. Cloudflare operates a global network; processing may take place outside Switzerland and the European Economic Area. Its Data Processing Addendum describes applicable transfer safeguards, including Standard Contractual Clauses. Further information is available in Cloudflare’s Privacy Policy.

We do not add advertising trackers, third-party analytics or externally hosted fonts to this website. Technical hosting and security processing may still occur.