Effective date: 17 August 2026 · Last updated: 15 November 2026
The data controller for yeih is yeih UG (haftungsbeschränkt), Sitz Berlin, Germany, registered at Amtsgericht Charlottenburg under HRB 280527 B, VAT identification number DE460174950. Postal address: see the Impressum. Contact: hello@yeih.ai.
yeih UG (haftungsbeschränkt), formerly kikoship UG (haftungsbeschränkt), registered under HRB 280527 B.
This policy explains what personal data we collect, why we collect it, how we use it, and what rights you have under the General Data Protection Regulation (GDPR). yeih is directed at users in the European Union. Your account, inventory and files are stored in Frankfurt, Germany (AWS eu-central-1, via Supabase). Some providers process data in the United States; see section 07.
You create an account with your email address and a password. Authentication is handled by Supabase Auth, which stores your password only as a one-way hash. Accounts created with Google or Apple sign-in before 14 November 2026 also hold the name, email address and profile photo the provider sent at the time; sign-in with Google and Apple has been removed.
Photos and documents are stored in Supabase Storage, hosted in the Frankfurt AWS region.
If you connect a mailbox, Nylas retrieves your messages and each one is checked to determine whether it is a purchase receipt. This check is performed by Anthropic's Claude model and by our own processing rules. We cannot identify receipts without examining messages, so this applies to every message in the connected mailbox, not only receipts.
For messages that are not receipts, we keep a limited record so the same message is not checked twice: the sender, subject, date, the classification result, and technical sender-verification details (DKIM, SPF and DMARC results). We do not retain the message bodies of non-receipt emails. Where a message contains no evidence of a purchase, any extracted details are discarded and no inventory item is created.
For receipts we also keep what was read from the email: the merchant, order number, items, prices and dates.
Items are added to your inventory only from messages containing evidence of a purchase, such as an order number, line item prices, or an invoice total.
Reading your mailbox and creating items are separate permissions, both controlled in Settings. Turning either off stops future processing.
For iCloud mailboxes, connection uses IMAP with an Apple app-specific password rather than the hosted sign-in flow used for Gmail and Outlook. The password is passed to Nylas, which uses it to connect to Apple's mail servers on our behalf. yeih does not store it: we keep only the connection reference and the mailbox address.
Saved emails, their attachments and the records above are kept for as long as your account exists. Disconnecting your mailbox stops processing and does not delete them. Deleting your account deletes them.
If you connect a Gmail account, yeih requests the gmail.readonly permission and receives message content and metadata through Nylas. We use it for one purpose: finding purchase receipts and turning them into inventory items you can see and edit. We do not use Google user data for advertising, do not sell it, do not transfer it to third parties except the processors listed in section 05 for that single purpose, and do not allow humans to read it except with your explicit permission for a support request or where required by law. The complete set of Google permissions yeih requests is openid, userinfo.email, userinfo.profile, gmail.readonly, and nothing else. Receipt content is sent to Anthropic's API for extraction under terms that prohibit retention for or training of generalized AI models. Disconnecting Gmail in Settings removes our access in your Google account, so yeih cannot read that mailbox again.
yeih's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
When an item is sold or deleted, yeih keeps a de-identified record of what the item was, what was paid for it, and what it was valued at. This record carries no link to your account: no user identifier, no item identifier, no serial number, and no photos or documents. Dates are reduced to month precision.
These records are used only in aggregate, to improve the accuracy of our valuations. Aggregate figures are shown only where at least five records exist for the same product, so no single record can be singled out through them.
The legal basis is our legitimate interests under Art. 6(1)(f) GDPR in improving valuation accuracy. You have the right to object to this processing at any time by contacting us. We describe this data as pseudonymised rather than anonymous: while we hold no means to link it back to your account, we do not claim it has been irreversibly anonymised.
yeih retrieves current market pricing from active eBay listings for similar items via the eBay Browse API. This is a read-only query using item names and categories. No personal data is sent to eBay.
Because eBay receives no personal data and processes nothing on our behalf, it is not one of our sub-processors. eBay acts as an independent controller and receives only non-personal product queries.
When you tag an item as For sale, your AI agent may broadcast it to the yeih buyer agent network. The following data is shared within the network:
Your full name, email address, and home address are never shared with buyer agents unless you explicitly confirm a connection.
Pseudonymised usage data including pages visited, session duration and device type, processed on PostHog's EU infrastructure, not linked to your name or email. You can opt out in Settings.
Payments are processed by Paddle, which acts as merchant of record and seller of record for all subscriptions. yeih does not store payment card details. From Paddle we receive only: confirmation of payment, subscription plan and billing period, and billing email address.
Sign-in events; item creation, deletion, and retagging; valuation requests; price confirmations; feedback submissions; introduction confirmations; and records of technical failures affecting your data. See section 04 for how these records are used and how long they are kept.
Account, inventory, and payment data are necessary to provide the yeih service.
Usage analytics help us improve the product. We also keep limited technical records of messages we have already checked: sender, subject, date, classification result and sender-verification details, so that the same message is not processed twice and so we can identify spoofed senders. You may opt out of analytics at any time.
To resolve delivery disputes and demonstrate that required notices were sent, we keep the rendered subject and body of transactional emails for 90 days after sending. This log contains the exact content the recipient received, including account or item details. Access is restricted to the company administrator, currently the sole director of yeih UG. After 90 days the rendered body is purged, leaving only the send record (recipient, template, status, and timestamp).
Reading your mailbox and creating inventory items from it are separate permissions, each recorded when you give it. You can withdraw either at any time in Settings, or by disconnecting your mailbox.
We keep a short record of actions you take in yeih. This covers when you sign in, when you add, delete, or retag items, when you request a valuation, when you confirm a price, when you send feedback, when you confirm an introduction, and when a technical operation fails.
For deletions we record which item was deleted, so that we can answer your questions about missing data and restore items where possible. For all other actions we record how many items were affected, not which ones.
We do not log what you view, what you search for, or how you move around the app.
When you send the access request form on our business page, we store a one-way hash of your IP address so that we can limit automated submissions. We never store the address itself, and we erase the hash 24 hours after the request. If we refuse a submission, for example because it looked automated or because too many arrived from one network, we keep a record of the refusal and its reason for 30 days so that we can find genuine messages we turned away, and then we delete it.
Our legitimate interests under Art. 6(1)(f) GDPR: operating a reliable service, diagnosing faults, answering your questions about your own account, and investigating suspected unauthorized access. We have assessed that this processing is limited to what is necessary for those purposes, that it records actions rather than the content of your data, and that it does not build a behavioral profile of you.
Activity records are deleted 45 days after the action they describe. They are also deleted immediately and permanently when you close your account.
You can request a copy of your activity records at any time. You can object to this processing under Art. 21 GDPR by writing to us at hello@yeih.ai.
We record sign-in events, deletions, and technical failures for security and data-integrity reasons, and we cannot switch these off while your account is open: without them we could not investigate unauthorized access or tell you what happened to data you have lost. You can ask us to stop recording the remaining categories, which are retagging, valuation requests, price confirmations, feedback submissions, and introduction confirmations, and we will do so.
We do not sell your data. Sub-processors are contractually bound to process data only on our instruction.
We use the following service providers to operate yeih. Each processes personal data on our instructions under a data processing agreement.
Google is the model provider behind the in-app assistant, where it acts as a sub-processor engaged by Lovable rather than a provider we contract with directly.
Lovable engages its own sub-processors to provide the platform, transactional email delivery and the in-app assistant.
Some of our providers engage their own sub-processors. Nylas publishes its list at nylas.com/security/subprocessors, and Lovable engages sub-processors including Google for the in-app assistant. Each is bound by onward-transfer obligations under the agreements described above.
Every claim in this section is something we can point at in the running system. Where a protection comes from a provider rather than from our own code, we say which.
yeih stores no access token and no refresh token for any mailbox. There is no column for one anywhere in our database.
The OAuth credential is held by our mail provider, Nylas. What we store is a grant reference: an identifier that lets us ask Nylas to read on your behalf. If our database were copied, it would contain nothing that can open a mailbox.
For Gmail, yeih asks Google for one mailbox permission, gmail.readonly, and nothing else. That permission does not allow composing, sending, deleting or moving anything.
Separately from what we are permitted to do, the only mailbox request yeih ever makes is a read. The one exception is deleting our own access when you disconnect.
For Outlook, the permissions are set on our mail provider’s Microsoft connector rather than in our own code, so we describe what yeih does rather than what it is prevented from doing. For iCloud, access uses an Apple app-specific password, which is not limited to reading: it is a credential rather than a permission. yeih still only reads, but in that case the limit is our behavior, not Apple’s.
For every message we look at, our record holds the subject, the sender address and domain, the date, the delivery authentication results (SPF, DKIM, DMARC), a content fingerprint used to avoid processing the same message twice, and the structured reading our extractor produced: line descriptions, prices, quantities, document totals and order numbers.
We name the extraction explicitly because it is detailed. It is not the message, but it is more than a summary, and it is kept so that a later correction to our reading can be checked against what we originally read.
We do not keep the body of the message. The text you wrote or received is not stored.
A message our filters refuse keeps no reading at all. Where a message is classified as promotional, as carrying no receipt signal, or as showing no evidence of a purchase, the extraction field is emptied: the row records only that the message was seen and why nothing came of it.
There is one deliberate exception, and it is the point of the product: when a message becomes an item, that email is saved in full as a document attached to the item, and so are later emails about the same purchase, such as a dispatch note or an invoice, together with any PDF attached to them. They are stored under a path belonging to your account and reachable only through your own session.
Your rows are separated from other accounts’ in the database itself, by row-level security policies that compare the signed-in user to the owner of each row. This is enforced by the database on every query, not by the interface, so a mistake in our application code cannot return another person’s items.
Three kinds of access exist beyond your own, and we would rather name them than imply there are none.
Administrative access by a person is limited to a named role held by a small number of accounts, and every administrative action against another person’s account is written to an audit log recording who did it, to whom, and when.
Automated server processes run with elevated database access that bypasses row-level security, because they do work that spans accounts: processing inbound mail, running valuations, sending service email and erasing accounts on request. That access belongs to the software, not to a person, and it is used to carry out those tasks rather than to browse.
Our application platform provider, Lovable, operates a development role used by its AI agent while building the app, which can read and insert data across accounts. Its credentials are held by Lovable and never exposed to our app. Lovable tells us the role cannot change or delete existing rows and cannot run database functions, and that it is not reachable through the public interface. We are naming it because it is access we do not control and cannot independently log.
Traffic between your browser and yeih is encrypted in transit with TLS, and so are the calls yeih makes to its database, its file storage and its mail provider’s API.
Data at rest is encrypted by the platforms that host it: our database and file storage are managed services that encrypt stored data and their backups. We rely on that rather than operating our own encryption layer on top, and we are telling you where the safeguard comes from so you can judge it.
Where we rate-limit a public form, we store a one-way hash of the IP address rather than the address, and a scheduled job erases those hashes after 24 hours and the surrounding records after 30 days.
Deleting your account erases your data immediately. There is no grace period and nothing is queued for later: the deletion runs as one operation, each table is counted before and checked after, and a final sweep re-reads every table to confirm nothing of yours remains, except the records listed in sections 02 and 08. Mailbox access is revoked and any subscription canceled before the irreversible step, so a failure leaves the account intact rather than half-erased.
Disconnecting a mailbox stops the scanning immediately and deletes the access record we hold, so yeih cannot read that mailbox again. It does not delete the items already in your inventory; deleting your account does that.
Disconnecting your mailbox in yeih removes our access in your Google account. You do not have to do anything else. If you would like to confirm it for yourself, your connected apps are listed at myaccount.google.com/connections. You can also remove yeih there instead, and that is enough on its own. We notice within about fifteen minutes and tell you.
yeih's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
If you need more detail than this section gives for a procurement or security review, write to hello@yeih.ai.
Some of our providers are established outside the European Economic Area, or store or access personal data outside it. Where that happens, we rely on the following safeguards:
You can ask us for details of the safeguards applying to any specific provider by writing to hello@yeih.ai.
Contact hello@yeih.ai. We will respond within 30 days. You may also lodge a complaint with the Berliner Beauftragte für Datenschutz und Informationsfreiheit (BlnBDI) at datenschutz-berlin.de.
When an account is deleted we keep one record of the deletion itself, retained indefinitely. It exists so we can demonstrate that an erasure request was carried out, and it contains no identifying content: the internal account identifier, who initiated the deletion (you or an administrator), the timestamp, and the number of rows removed per data category. No email address, name, or inventory content is kept in it.
No session cookie. Staying signed in uses your browser's local storage, not a cookie.
Your consent choice is kept in local storage too, so we can remember it without a cookie.
Analytics. PostHog sets a cookie and uses local storage, only if you accept analytics. You can change that in Cookie settings at any time.
Strictly necessary cookies. Two cookies are set on your first visit, because the site cannot be served safely or consistently without them. Neither holds account information or needs consent:
__cf_bm, from Cloudflare, which serves this site. It tells people from bots and lasts 30 minutes.__dpl, from Lovable, our application platform. It routes your visit to a consistent published version of the site, holds a signed deployment token and no information about you, lasts one day, and cannot be turned off.Lovable keeps the operational and security logs from serving this site for as long as it needs them to run and secure its services, and longer while investigating an incident, then deletes or de-identifies them (lovable.dev/privacy, section 13).
Paddle's checkout, and the Cloudflare check on our sign-up page, run under those companies' own policies when you use them.
We will notify you by email at least 14 days before any material changes to this policy take effect.
For privacy questions or to exercise your rights: hello@yeih.ai