Privacy Policy
Last updated: 6 October 2026 · Deutsche Fassung
WishEase keeps wish lists and gift arrangements — data about other people, some of it deliberately hidden from them. This page says what we store, who gets to see it, and how you get rid of it.
Controller
The controller under the General Data Protection Regulation (GDPR) is:
Tobias Laurent
Alte Bergstr. 146
84028 Landshut
Germany
Email: t.terence@web.de
Full provider identification:
Impressum
No data protection officer has been appointed; the thresholds in Art. 37 GDPR and § 38 BDSG are not met.
What we process
| Data | Purpose | Legal basis |
|---|---|---|
| Email address, password hash, sign-up and sign-in timestamps | Run your account, authenticate you | Art. 6(1)(b) GDPR (contract) |
| Session data: IP address, user agent, timestamps | Maintain and secure signed-in sessions | Art. 6(1)(b) and (f) (security of the service) |
| Content: wish lists, wishes (title, description, price, link, image address), occasions and dates, invitations, organizer roles | Provide the service | Art. 6(1)(b) |
| Coordination data: who reserved or bought a wish | Let gift-givers coordinate without anyone learning who it was; hidden from the gift receiver entirely | Art. 6(1)(b) |
| Notifications: log of messages sent, preferences, push tokens | Reminders, where you enable them | Art. 6(1)(b) |
| Contact form: name, email address, message | Answer your enquiry | Art. 6(1)(b) or (f) |
| Access logs for the connection and sign-in paths: method, address, status code, user agent | Operation and debugging | Art. 6(1)(f) |
| Error logs: if a database query fails or an unexpected error occurs, the error is logged. It can contain content from the record involved — for a violated database constraint, even the whole record including the identifiers in it. | Debugging | Art. 6(1)(f) |
| Abuse protection: IP address as a counter key, held in memory only | Rate limiting | Art. 6(1)(f) |
While nothing goes wrong, we do not log the contents of
your calls to /mcp and /v1 — no lists, no wishes.
When something does go wrong, that changes: the logged error can contain
content from the record involved (see the "Error logs" row above). These
logs fall under the hosting platform's retention, are not processed further,
and are not archived long-term.
An email address is required to create an account; without it we cannot provide the service. Everything else you supply is voluntary.
Recipients and processors
| Provider | Role | Location |
|---|---|---|
| Supabase | Database and authentication | Data centre in Ireland (eu-west-1) |
| Fly.io | Application hosting | London, United Kingdom |
| Resend | Confirmation and contact emails | USA |
| Cloudflare | DNS and domain management for wishease.net | USA / global |
| The controller's own hardware | Database backups | Germany |
Other users
Anyone who shares a list with you — as its receiver, its creator, or a co-organizer — can see your email address. That is deliberate: a shared list has to show who is involved. People you share no list with see nothing of your profile; the database returns nothing for their queries.
The wishes you put into a shared list are visible to its members, though secret wishes are not visible to the gift receiver. Who reserved or bought something is told to nobody. Co-organizers see that an item is taken, never by whom; the gift receiver does not even see that. This is not a setting we flip — it is fixed in the database, and your identifier does not leave it for those queries.
Someone you send an invite link to learns the list's title and the role it offers before accepting — including if they never accept.
Beyond that we disclose personal data to no third party. We do not sell data, run advertising, or embed analytics.
International transfers
Stored in Ireland (the database) and the United Kingdom (the application server). The United Kingdom is covered by a European Commission adequacy decision.
Access from the USA is still possible, and you should know that: both our database provider and our hosting provider are US companies whose support teams can reach the systems in the course of running them. On top of that, email delivery and domain management happen in the USA anyway. All four transfers rely on the safeguards those providers make available — the EU Commission's standard contractual clauses or the EU-US Data Privacy Framework — which we have accepted with them.
What reaches the email provider is delivery data and the content of the emails we send you — not your lists. Domain management sees DNS queries only, no account data.
Your AI assistant
WishEase is operated through the AI assistant you choose and connect to your account. Once you do, the content you read or create flows to that assistant's operator — much as it would flow to your browser. The assistant is therefore not our processor: we have no contract with its operator and send nothing there on our own initiative. Many such providers are outside the EEA; their own privacy policy governs what happens there. Only connect an assistant you trust.
What any assistant can retrieve is bounded technically — not by trusting it, but in the database: someone who is the receiver of a list does not get secret wishes or reservation data even if their assistant asks for them. For that caller, the data never leaves the database.
Retention
- Account and content: until you delete it or ask us to. There is no self-serve deletion yet — an email to t.terence@web.de is enough.
- Backups: eight weekly database dumps on the controller's own hardware, overwritten after that (about eight weeks). Deleted data may still sit in a backup until then; those dumps are offline and used only for disaster recovery.
- Signed-in sessions: each session record holds an IP address, a user agent, and timestamps. No session time limit is configured at present: the record stays until you sign out or your account is deleted. Disconnecting an assistant on its own side does not sign you out here, so the record survives that. The access tokens themselves expire after an hour and are rotated.
- Server logs: the hosting platform's default retention; we keep no long-term archive.
- IP addresses in abuse protection: minutes, in memory only.
- Contact enquiries: in the controller's mailbox and in the email provider's delivery log.
Cookies and tracking
These pages set no cookies — neither strictly necessary ones nor any for analytics or advertising. We store no information on your device and read none from it, so § 25 TDDDG (the German ePrivacy implementation) is not engaged and no cookie banner is required.
When you sign in, your access token is held only in the open page's memory; closing the tab discards it. We embed no external fonts, scripts, maps, videos, or social media widgets — these pages load nothing from third-party servers.
The assistant or app you connect to WishEase stores its own credentials on your device, under its rules rather than ours. If we ever add analytics or embedded services, we will ask for your consent first.
Your rights
You have the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), and data portability (Art. 20), and the right to object to processing based on legitimate interests (Art. 21). Any consent you give can be withdrawn at any time with effect for the future (Art. 7(3)).
An email to t.terence@web.de is enough. We answer within one month (Art. 12(3)). To verify identity, please send the request from your registered address.
An access request under Art. 15 does not include the secret wishes and reservation data on lists meant for you: the right to a copy must not adversely affect the rights of others (Art. 15(4)) — and telling you the surprise planned for you is exactly that. Our answer says where it was trimmed. Your own reservations on other people's lists are included.
Right to lodge a complaint
You may complain to a data protection supervisory authority at any time — either the one responsible for us or the one where you live. Ours is:
Bayerisches Landesamt für Datenschutzaufsicht (BayLDA)
Promenade 18
91522 Ansbach
Germany
lda.bayern.de
Security
Connections are encrypted with TLS throughout. Passwords are stored only as hashes, never in clear text. Who may see which data is enforced in the database itself rather than in the application, and the application server deliberately holds no privileged database key. Backups sit on the controller's own hardware.
No automated decision-making
There is no automated decision-making, including profiling, within the meaning of Art. 22 GDPR.
Children
The service is not directed at children under 16. We do not knowingly collect their data; if we learn of such an account, we delete it.
Changes to this policy
If what we process or whom we rely on changes, we change this policy and update the date above. WishEase is at an early stage; we will announce material changes to registered users by email.