Privacy Policy

In Taesty 1.0, nothing leaves your devices except through your own iCloud. What the app learns about your screenshots stays on your iPhone and Mac and syncs between them through your private iCloud (section 3). There is no Taesty server, and nothing is sent to us or to an AI provider. Apple’s own services, such as iCloud Photos and device backups, work as described in section 3.

Taesty accesses screenshots and images you make available to the app to organize, understand and search them. The app’s image analysis, text recognition (OCR), tagging, embeddings and search indexing run on your device.

Original screenshots are read from Photos or, on Mac, the screenshot folder you choose. Taesty stores descriptions and references to those originals in its local index.

The agent connection is not part of Taesty 1.0. When it is available, it will be a separate data-sharing path: a reference an agent requests can be sent to that agent’s model provider. See Connected agents and MCP.

We do not use your screenshots or their contents to train AI models. We do not sell your personal data or use it for advertising or cross-app tracking. An agent provider’s own processing is governed by that provider’s policies and your settings.

Taesty does not require a separate Taesty account. Apple services use the Apple Account configured on your device. Taesty does not receive your Apple Account password.

If you use iCloud Photos, Apple may store your originals in iCloud and download an image when Taesty needs to read it. Device backups may also include local app data, according to your Apple settings.

Taesty syncs what it learned about your screenshots between your iPhone and Mac through your private iCloud database (CloudKit), using the iCloud account signed in on your device. By default only you can access your private database; we cannot read it. It counts toward your iCloud storage. If you are not signed in to iCloud, nothing syncs and each device keeps its own index.

What syncs, for each screenshot: its title, description and labels, the names and things Taesty recognized, what it is useful for, its most important lines of text, its kind, language and dates, the app or page it came from where known, and which model understood it. Your favorites, notes and removals sync too, with an identifier that matches the same screenshot on each device.

What never syncs: the images, the full text Taesty read, visual fingerprints (embeddings), Photos’ on-device identifiers and processing progress. A screenshot held back as sensitive syncs without its description or note.

Apple services are subject to Apple’s Privacy Policy and applicable terms. Apple’s Photos synchronization and backups are separate from Taesty’s own memory index.

To provide search and organization features, Taesty may store the following on your device:

• Recognized text, titles, descriptions and labels.
• Embeddings and semantic indexes used to find relevant screenshots.
• References to originals in Photos or the folder you select.
• Favorites, notes, organizational information and records of hidden items.
• App settings and processing progress.
• Search queries and comments that you choose to save with result feedback.

Taesty also uses your device’s Spotlight index to support search. Images displayed in the app are retrieved from their original source; displaying a thumbnail does not mean it is uploaded to a Taesty service.

Taesty needs your permission to read screenshots in Photos. You can limit or revoke Photo Library access through Apple’s system settings. With limited access, only the selected items are available to the app.

On Mac, you can also choose a screenshot folder for Taesty to read. Removing or changing that folder deletes what Taesty learned only from it; the files themselves stay.

This section applies when the agent connection is available. It is not part of Taesty 1.0, which does not open a connection to any agent, so today nothing in it takes place.

If you connect Claude Code, Codex, Cursor or another MCP client, that agent can request references from Taesty through the local MCP server on your Mac. That server talks only to the Taesty app on the same Mac; no Taesty server is involved. Your screenshots, images and notes go from your Mac to the agent you connected and that agent’s model provider.

Before the first pairing code, the Mac app asks for your consent. It shows what goes where: permitted text and requested images of your screenshots go to the agent you connect and to that agent’s AI provider, and nothing goes to Taesty. You confirm once per Mac. Settings then lists each paired agent by name, and you can revoke any of them.

A requested reference can leave your device. By default, an agent receives each result’s title, description, labels, source app and your notes. It receives the screenshot image and the full text Taesty read from it only when it asks for them explicitly. Everything included in a response becomes available to the agent and may be transmitted to the provider running its model.

Taesty holds a screenshot back automatically when the text it read contains a card number, an IBAN, an ID number, a password, a one-time code, an API key or private key, or a wallet seed phrase. You can also hold back any screenshot yourself. Held-back screenshots never appear in search and are never returned to a connected agent. Other personal content, such as photos of people, is not detected automatically.

Those providers process the information under their own terms, privacy policies and your account settings, including their rules for retention, model training and international transfers. Local processing in Taesty does not make a connected cloud agent local.

You can stop future requests by turning off Agent Access in the Mac app’s Settings, or by removing Taesty from the agent’s own settings. This does not erase information an agent or its provider has already received.

Taesty does not use third-party advertising or tracking SDKs.

If you choose to share diagnostic information with app developers through Apple’s settings, Apple may provide crash reports and limited technical information, such as app version, device information and performance data.

We use these reports to investigate technical issues and improve reliability. They are not intended to contain screenshot content. Please review any report or attachment you choose to send us.

When you visit taesty.dev, our hosting provider, Vercel Inc., 440 N Barranca Ave #4133, Covina, CA 91723, USA, processes the technical data your browser sends in order to deliver the pages: your IP address, the date and time, the page requested, the referring page, and browser and device information. These server logs are used to deliver the website and keep it secure, and are kept only briefly.

Where the GDPR applies, the basis is our legitimate interest in a reliable and secure website (Article 6(1)(f)). Vercel processes this data on our behalf under a data processing agreement. Transfers to the United States rely on Vercel’s certification under the EU-U.S. Data Privacy Framework and on the European Commission’s Standard Contractual Clauses.

The website sets no cookies and uses no analytics or tracking. Its fonts and images are served from taesty.dev itself.

If you contact us, we receive your email address, message and any attachments you send. Only include a screenshot if you want us to see it.

We use this information to answer your request and provide support. Where the GDPR applies, the basis is handling a contract-related request (Article 6(1)(b)), our legitimate interest in responding to other inquiries and maintaining a reliable product (Article 6(1)(f)), or compliance with a legal obligation (Article 6(1)(c)), as applicable.

We retain correspondence for as long as needed to resolve the request and meet applicable legal retention requirements. Service providers supporting our communications may process it for that purpose.

Local indexed information remains in the app’s storage until it is removed. “Remove from Memory” clears what Taesty read from a screenshot, including its description, text and visual fingerprint, and removes it from search and Spotlight. Taesty keeps only an identifier and a removal marker, so the screenshot is not added again. The removal syncs to your other devices.

When you delete a screenshot in Photos, Taesty clears what it read from it in the same way once it notices the deletion; this requires full Photos access. Removing or changing your screenshot folder on Mac deletes what Taesty learned only from that folder; the files themselves stay.

“Delete All Taesty Data” in the app’s settings deletes Taesty’s data everywhere: on that device, in your private iCloud database and, when they next sync, on your other devices. Your screenshots in Photos and the files in your folder are never touched, and Taesty learns your library again afterwards. Removing the app and its data also removes local Taesty data. On Mac, moving the app to the Trash alone may leave its data container behind. Copies in iCloud Photos, device backups, exported files or agent conversations must be managed separately through those services.

We cannot independently delete data that exists only on your devices or within your personal Apple services. Contact us if you need help identifying the local data to remove.

Taesty is designed to minimize the personal information accessible to its operator. Processing screenshot content locally reduces the need to transmit it for analysis.

No software or storage system can guarantee absolute security. Your device, Apple services and any agents you connect each have their own security settings and data-handling practices.

Depending on the law that applies, you may have rights to access, correct, erase, restrict or receive a portable copy of personal information, and to object to certain processing. Where processing relies on consent, you may withdraw it without affecting the lawfulness of earlier processing.

Many controls for local app data are available on your device. For information processed directly by us, contact privacy@taesty.dev.

You may also complain to a data protection authority, including the authority where you live or work. Our local authority is the Berlin Commissioner for Data Protection and Freedom of Information.

Taesty is not directed at children. If you believe a child has provided personal information to us, contact us so we can review and address it.

We will update this policy when Taesty’s functionality or privacy practices change and revise the date above. Material changes to data handling will be explained before they take effect, with consent requested where required.

Taesty is operated by the following company, which is the controller for personal information it processes:

Email: privacy@taesty.dev

Further company information is available in our Imprint.