Privacy Policy

1. Introduction

EventLink is event planning and operations software for teams. This policy explains what personal data we collect, why we collect it, who we share it with, and what you can do about it. We have tried to write it in plain language rather than legalese.

The company responsible for your data (the “data controller”) is:

This policy covers both our website at eventlink.dev and the EventLink application at app.eventlink.dev. We are based in Thailand and comply with the Personal Data Protection Act (PDPA). If you are in the European Economic Area or the United Kingdom, the GDPR gives you additional rights; if you are in California, the CCPA/CPRA does. Those rights are set out in section 6.

EventLink is not intended for children. See section 7.

2. Information We Collect

Your privacy choices

When you answer the cookie question, or change analytics, session replay or marketing email later, we keep a record of the answer itself: which choice you made, when, which version of the wording you were shown and in which language. The law requires us to be able to show what you agreed to, and a note in your own browser cannot do that. Changing your mind adds a new entry rather than replacing the old one, so the history is honest. The record holds a one-way scramble of your IP address, never the address, and it is deleted with your account. If you answer before you have signed in, it is tied to the anonymous ID our analytics gives your browser instead, and kept as that proof.

Account information

When you create an account we collect your name (and any nickname or username you choose) and your email address. There is no password: we sign you in with a single-use link or code sent to that address. You can optionally add a phone number, profile photo, gender, date of birth, job title, employer, location and country, and links to your other profiles. The optional fields are exactly that: optional, and you can remove them at any time.

If you sign in with Google, Microsoft, LinkedIn, Facebook or LINE, we receive your basic profile information and email address from that provider so we can create or match your account. We never receive your password for those services.

If you sign up through a referral link or code, we record which code you used, and we link your new account — and your first workspace, including the one we set up for you when you join — to the person that code belongs to. We keep this as our record of how people found EventLink. No discount or other benefit is attached to a referral today; if that changes, this policy will change with it.

Content you put into EventLink

We store what you create in the product: your workspaces and teams, your events (including descriptions, target audience, and event addresses, which include map coordinates), tasks and their descriptions, comments, approvals, files and documents you upload, your conversations with the AI assistant (both the one inside an event and the one that creates an event for you), and post-event reflections.

About “anonymous” reflections: post-event reflections are presented to your team without your name attached, but they are still stored linked to your account. They are not technically anonymous, and we would rather tell you that than let you assume otherwise. Please keep it in mind when writing them.

Technical information

We automatically collect your IP address, browser type, device information, and pages or features you use. Specifically, we store your IP address with your active session (alongside your browser user-agent) so you can stay signed in and so we can spot suspicious activity, and we use it to enforce rate limits; this is how we stop brute-force login attempts and abuse. Your IP address is also seen by the providers who deliver the service to you (our hosting platform and our network provider) and appears in their access logs, as it would for any website you visit.

We also record the IP address each AI generation was requested from, and keep it with that generation's usage record. AI costs us real money per request, so we use it to cap AI spending per origin; that is how we stop someone creating account after account to get a fresh AI allowance each time, which a per-account limit cannot catch. We clear these IP addresses after 90 days; the usage record itself (which model, how many tokens, what it cost) is kept.

Information you send us directly

If you fill in our contact form, ask us about a pricing plan, or join a waitlist, we collect the name, email address, phone number, organisation and message you provide, along with your IP address, your language preference and the page you submitted the form from. We use this only to reply to you and to tell you when a plan you asked about becomes available; we do not add you to a marketing list without asking. We clear that IP address after 90 days. If you send us feedback from inside the app, we keep it with your account, along with your IP address and browser details, which we also clear after 90 days.

What we do not collect

We do not currently process payments, so we do not collect or store card or billing details. We do not sell your personal data, and we do not use it for advertising or share it for cross-context behavioural advertising.

3. How We Use Your Information

We use the data described above to:

• Provide, maintain and improve EventLink, and keep your account working.
• Let you collaborate, showing your name and avatar to other members of your workspaces and events.
• Power our AI features (see below).
• Send you service messages: sign-in links, invitations, security and technical notices. You cannot opt out of these while you have an account, because they are part of the service.
• Send you product or marketing email, only if you have opted in. You can withdraw that at any time.
• Understand how the product is used, so we can improve it.
• Keep EventLink secure, detecting abuse, enforcing rate limits, and investigating incidents.
• Comply with our legal obligations.

AI features

What we send, and where. Planning with Blobby means sending what you type, say or upload to AI services in the United States: Anthropic for everything below, and OpenAI for voice notes. We send it to plan your events and nothing else. It is not used to train anyone's models, and we do not use it to profile you or to make decisions about you or your account.

We never ask you for sensitive information. Planning can still touch it — a funeral, an ordination or a child's birthday may say something about a family's faith, health or children. Please share only what your plan needs.

EventLink uses Claude, an AI model provided by Anthropic, to generate starter task lists, write event descriptions, power the in-app assistant, draft an event from a description you type, add to your plan when you answer one of its questions, and, if you choose it, set up a new event by talking to you. To do that, we send Anthropic the relevant content: your event details, task descriptions, team names and descriptions, how many people are working on the event and on each team, and whether the event has an approver, the names of the people on the event, their role on it and which teams they are on, the outcomes your plan is built around and which approach you chose for each, the comments your team leaves on tasks, the record of what changed on a task and when, anything recorded in the event's notes (see below), the first name or username of the person using the assistant, and any documents you deliberately upload.

Your plan is built around outcomes — the things that have to become true for your event to work, like "Venue secured". Where we cannot know how you are handling one, the AI asks instead of guessing, and you answer by tapping one of the options it offers or by replying in your own words. When you answer, we send Anthropic that outcome, the approach you picked, and the descriptions of the tasks already on the event, so that what it adds fits your situation and does not repeat work you already have.

You can also answer in your own words instead of picking one of the options, using "Something else" on the question or by telling the assistant in the chat. When you do, we keep exactly what you wrote and send it to Anthropic as part of building the plan for that outcome — that is the point of answering this way, since the detail in your own sentence is what stops the plan assuming work you have already done. We store it with the question you answered and with the outcome itself, for as long as the event exists, and it can later be read by the assistants like anything else recorded on the event.

Replying to the question as an ordinary comment works differently: we match what you typed on our own servers, not by asking the AI to interpret it, and if it plainly means one of the options we record that option. Your reply is an ordinary comment on the task, visible to your team as any comment is, and like any other comment it can later be read by the AI as described below.

Some events are ceremonies, and a plan that treats one as an ordinary party can be wrong in ways that matter. So each time the AI writes your plan, or adds to it after you answer one of its questions, we check what you wrote about your event against a list of ceremony names we maintain ourselves, in English, Thai and Chinese. That check runs on our own servers and involves no AI. If it matches, we send Anthropic our own reference material about that ceremony with the request, so the plan covers what it actually needs. We do not keep the result: nothing about which ceremony or religion an event seems to involve is stored, and the records we kept of this before October 2026 have been deleted. We never ask for, and never store, any person's religion. If the check guesses wrong, describing your event in different words changes what it finds.

If you describe an event in the box on our marketing site ("a wedding for 200 guests"), we keep that sentence in your browser session and carry it into the app, where it opens your conversation with the AI: we send it to Anthropic to fill in the event's first details. We hold that first draft briefly against your account so refreshing the page does not re-run it, and it is discarded once you create the event. If the AI is unavailable, we do not send it: we keep it for up to two hours in case the AI comes back, and you can fill in the details yourself meanwhile.

When you create an event by talking to the AI, everything you type in that conversation is sent to Anthropic, along with the event it is building for you. If you ask it to find your venue, we send what you typed to Google Maps to look the place up, exactly as the venue search in the event's details does. The conversation is kept with your draft so you can pick it back up, and deleted after 90 days (see below). You can stop talking to the AI at any point and fill in the details yourself.

Before it replies to the first thing you type in that conversation, the AI reads it a few times to work out what kind of event it is, whether a person or an organisation is hosting it, who is coming, whether you are organising it for someone else, how big and formal it is and, if you say, which country it is in. When it cannot tell, it asks you one question about it and reads your answer the same way. We store what it concluded, not your words, with the event, and use it to set the event's type and fit the conversation and the task plan to your event. Who the event is for and how big it is show on the draft's details, where you can change them before you create the event, and are sent to Anthropic with the conversation, the task plan and the tasks added to it later. It is our inference about the event, not about you, it never records a religion, and it is deleted when the event is.

Searching the web. In either conversation, when an answer depends on something current or local, such as a venue's capacity, a supplier or a public holiday, the assistant can search the web through Anthropic. The searches it writes can include details of your event, such as its type, city and dates. They go to Anthropic's search service, which may use a search partner to run them, and we send your event's timezone (or yours, before the event has one) so the results are local. The pages the assistant cites are kept with the conversation so you can open them again, and are deleted when the conversation is: after 90 days for the one that creates an event, and for the one inside an event when you delete it, or the event or your account is deleted.

When you are ready to build an event, the AI writes its description from what you typed in the conversation that shaped it and what the assistant noted about the event, along with the event's details, so we send those to Anthropic. It is told to keep to what you said, and you can change it or write your own.

You can also attach documents to that conversation — a brief, a run sheet, a budget, a slide deck — paste in a long piece of text, or attach a picture, such as a photo or a screenshot. We read the text out of a document and send that text to Anthropic so the assistant can use it to fill in your event. A picture is sent to Anthropic as it is and shown to the assistant on the message you attach it to; at the same time Anthropic writes down what it shows, including any words in it, and after that message the assistant works from that written description. We never show your attachments to anyone outside your workspace, and there is no way for a stranger to download them.

What you send is kept with your draft. Once you send a message with something attached, we keep the file, the text we read out of it (for a picture, the written description) and, for a picture, a re-encoded copy of the picture itself, with your draft, so you can open them from the draft while you plan. They stay until you delete the draft, which deletes them too, or until you create the event from it, when they become that event's documents: the assistants can then refer back to your brief while you actually run the event, and deleting the event deletes both the file and the text. In the event itself they are not currently listed anywhere — they are held for the assistants to read. Something you attach but remove before sending is never kept. The conversation's own working copy of an attachment is still deleted as soon as the conversation ends, and a daily clean-up removes anything left from an abandoned conversation within 48 hours of your last activity.

A document kept with an event stays readable by the assistants for as long as the event does. Until recently the text of something you attached reached the AI once, on the message you attached it to. Now an assistant can look at it again at any point while you run the event — and so can other people working on that event, through their own assistant, because a kept document belongs to the event rather than to the conversation it arrived in. If a file should not be that widely readable, it can be limited to a single team, and then only that team, your workspace's owners and admins, and the event's approver can see it or ask the AI about it.

We ask Anthropic to write one line describing each document we keep. When a document joins an event we send its opening pages to Anthropic once, and store the sentence it writes back — "a catering contract covering the budget ceiling and the headcount deadline", say. That sentence is what lets the assistant tell which file is worth opening instead of reading all of them, so it means less of your document is sent to the model as you work, not more. It happens once per document, not on every request.

We keep a copy of that conversation for 90 days. We read them to find out where the assistant is getting in your way (asking you the same thing twice, misunderstanding a date, taking ten replies to do something that should take three) and then we fix it. It is deleted after 90 days, and immediately if you delete your account. It is not used to train anyone's AI model, and it is not shown to your workspace. That copy does not include your attachments. It records only that you attached something, its name and how long it was — never what was inside it.

What you decide in that conversation is saved as a draft event until you delete it. The details the assistant has collected (the event's name, type, description, who it is for, audience, dates, timezone, venue, expected headcount, language, success measures and teams), any banner you choose, the files and pictures you send (see above), and the facts the assistant notes down along the way (see the event's notes below) are kept as a draft, so you can leave and come back to it later. Only you can see your drafts, though a banner you upload for one joins your workspace's banner library, as every banner upload does, and stays there if the draft is deleted. A draft stays until you delete it or go on to create the event from it, when it becomes that event. The conversation that shaped it is still deleted after 90 days; the draft keeps only those details, files and notes, and what the AI concluded from your first message (see above), not the conversation itself.

Your conversations with the in-app assistant (the one inside an event) are stored in your account so you can come back to them, and you can delete them. You can attach documents there too — a brief, a run sheet, a budget, a slide deck — or paste in a long piece of text. As with the create-an-event chat, we read the text out of what you attach and send that text to Anthropic. We do not keep the file itself. We keep only the text we read out of it, stored alongside that conversation for as long as the conversation lasts, so the assistant can look at it again later. Clearing the conversation deletes those documents, and so does deleting the event or your account. Clearing a conversation does not remove anything the assistant already saved to the event's notes from it — those entries are listed in event settings, where you can change or delete them.

We do not read those in-app conversations to improve the product. What we look at instead is what happened to the assistant's suggestions — how many it made, of what kind, and whether you took them or turned them down. That tells us which kinds of suggestion are worth making without anyone reading your thread. The one exception is an exchange you flag yourself, below.

You can tell us when it did badly. Each of the assistant's replies can be marked helpful or unhelpful, and now and then we will ask you outright. If you mark a reply unhelpful, our team may read that exchange — your message and its reply — so we can fix what went wrong, for as long as the conversation itself is kept. You can also pick what went wrong and add a short note; we keep those with the mark until you delete your account. If you would rather we did not read it, simply do not use the thumbs.

You can also attach a picture — a photo or a screenshot. Here the assistant looks at the image itself rather than at text we have read out of it, so the picture is sent to Anthropic. It is shown to the assistant once, on the message you attach it to. At the same time we ask Anthropic to write down what the picture shows, including any words in it, and it is that written description we keep, on exactly the same terms as a document's text above. The picture itself is not kept. It is held only for the moments between you uploading it and your message being sent, and is deleted as soon as the message goes; a daily clean-up removes anything a failure left behind.

The assistant can also open files attached to your tasks. If you ask it about a contract, a quote or a floor plan somebody uploaded to a task, we read that file at that moment and send its contents to Anthropic so it can answer. It only ever opens files on tasks you are already allowed to see. We do not store what it reads — the text is used to answer you and held briefly in a temporary cache so a follow-up question does not have to re-read the same file, and nothing is written into your event's records. A picture attached to a task is handled the same way as one attached to the chat: it is described, and the description is what the assistant reads.

An event can also have notes. These are the durable things about an event that do not fit anywhere else — who your caterer is, a budget ceiling, a decision you have already taken, something that went wrong last time. Each note sits in one of three sections: settled, still to decide, or ideas you like but have not committed to, and is filed under a topic: a built-in one such as People or Budget, or one that someone who can edit the event, or the assistant, named for it. Topic names are sent to Anthropic with the notes, and as the list of topics the assistants can file a note under. Whenever you use either assistant on that event, it is sent a list of every note's title and topic, in all three sections, and a short account of what changed in the notes since it last replied: which note, what changed, and the first name of whoever changed it. It reads a note's full text only when it needs to, by looking it up. All of this goes to Anthropic, so you stop having to re-explain the same context every time you ask for help.

Some of them are written by the assistant rather than by you. Four things can put an entry there: anyone who can edit the event writing one by hand; the durable things you tell the assistant while creating the event, which it keeps as notes as you mention them so the assistants can read them later; a one-off background pass, once your event is created, that re-reads that conversation and any documents you attached and records the durable facts nobody wrote down as they went; and the assistant inside your event, which saves a durable fact to the event's notes as you mention it while you work. Both assistants can also change, move or delete a note when you ask, or when something you say makes it out of date. Each change shows under the assistant's reply with an Undo button, and the assistant asks before deleting a note. That background pass is another request to Anthropic, and it is one of two times we send what you typed for a purpose other than replying to you (the other is the event's description, above). Anything the assistant recorded is marked as unconfirmed until a person checks it, and all of it is listed in event settings for you to correct or remove. While an event is still a draft, what the assistant has noted is shown in the event creator's details panel instead, where you can correct it or stop the assistant using it; deleting the draft deletes it outright. Only people who can edit the event can record a note, by hand or through an assistant — nobody else, and no one outside your workspace.

Your task board is also read overnight. Once a day, for each event where something meaningful happened, we send Anthropic what changed on the board that day — the tasks your team finished, the comments left on them, and edits to their descriptions and checklists — and keep the durable facts worth remembering, such as a supplier you picked or a quote you were given. Most days this records nothing at all. It is told to record facts about the event and never about how a person is doing their job, and never to record anyone's health, beliefs, political opinions, background, payment details or identity numbers.

The in-app assistant can read those comments too, when you ask it something. The conversation on the task you have open is sent with your question, it can search the comments on any task you are allowed to see, and it can read a task's history of changes. It only ever reaches what you could open yourself: if your event limits members to their own team's tasks, the assistant is limited the same way. Unlike the overnight pass above, which strips names out, this one includes who said what and who changed what, because answering "what did we decide" usually depends on it. Comments are written by your teammates to each other, so this is worth knowing even though nothing here is shown to anyone who could not already see it.

Two things about them are worth being plain about. First, a note can describe a person — a supplier's contact, a sponsor, someone you are dealing with — and that person may well not have an EventLink account, so they have no way of knowing we hold it or of asking us themselves. We ask you to record only what you need in order to run the event: who someone is, what they do, and how to reach them about it. Please do not record opinions about a person, their performance or conduct, anything about their health or beliefs, or payment and identity details. Second, unlike your AI conversations, an event's notes are not on a 90-day clock — they last as long as the event does, which is the whole reason they are useful. Anyone who can edit the event can change or delete them at any time. A deleted note waits in Recently deleted for 30 days, so it can be brought back, and is then erased for good. We also keep a history of the changes made to each note (what it said before and after, who made the change, whether a person or the assistant, and when) so a change can be undone. That history is erased with the note, and everything goes when the event is deleted. If someone who changed a note deletes their account, the history keeps the change but no longer says who made it.

The assistant also keeps a few private notes about you. When you tell either assistant something lasting about yourself, the people in your life or how you like to work, it can keep it as one short sentence, at most 30 for each event, so it does not have to ask again. Each one appears under the reply that kept it, with Undo and Edit, and Settings → Privacy lists them all. Unlike an event's notes, nobody else in your workspace can see them, and no other AI feature reads them.

What the assistant remembers about you for an event is sent to Anthropic with each message you send either assistant on that event. Before a memory is kept or changed, including when you edit one yourself, we send that sentence to Anthropic on its own to check it, and we do not keep anything about anyone's health, religion or beliefs, ethnicity, politics, sex life or gender identity, criminal record, biometric or genetic data, union membership, immigration status, grief or emotions, any ID or account number, or an opinion about another person. If that check cannot be made, nothing is kept. If you mention someone else, keep it to who they are to you or what they do for the event.

We do this on the basis of our legitimate interest in helping you plan without asking the same things twice. To object, turn memory off for one event or everywhere in Settings → Privacy, or forget any memory there. Your memories for an event are deleted when you leave the event or are removed from it, when the event or your account is deleted, and 12 months after the event ends (for an event with no end date, once both it and the memory are 12 months old). Starting a new conversation does not delete them.

You can talk to the assistant instead of typing. If you record a voice note, we send the recording to OpenAI — a different company from Anthropic, used for this and nothing else — because the model that powers the rest of our AI features cannot listen to audio. Along with it we send a short list of your event's own names: the event, its teams, and the people on them. That is so the words come back spelled the way you have them rather than as something that merely sounds similar. We send nothing else with it — not your tasks, not your comments, not your email address.

We do not keep the recording. It is turned into text and discarded straight away; we never store the audio, and there is nowhere in EventLink to play it back. What survives is the text, and only where you left it — in the message box, for you to read, correct or delete. Nothing is sent to the assistant until you send it. We do keep a record of what each recording cost us, so we can measure what the feature costs to run; that record holds no audio and no words. OpenAI processes the recording to return the text to us and their terms do not permit training their models on it, though they may hold it for up to 30 days to detect misuse before deleting it.

We do not send your email address to the AI model. Anthropic processes this content to return a response to us; their handling of it is governed by their commercial terms, which do not permit training their models on it.

Legal bases (GDPR / PDPA)

Where the GDPR or Thailand's PDPA applies, we rely on: performance of a contract (running the service you signed up for); legitimate interests (securing the platform, preventing abuse, improving the product, and letting the assistant remember what you tell it, as described above); consent (optional analytics cookies, session replay, and marketing email, each of which you can refuse or withdraw); and legal obligation where the law requires us to keep or disclose something.

4. How We Share Your Information

With people you work with

EventLink is collaboration software, so content you create is visible to other members of the workspaces and events you belong to, according to their role and permissions. Workspace owners and admins can see the content of their workspace.

When you invite someone, the sign-in page their invitation link opens shows your name and profile photo, the name of the event or workspace, the event's dates, and the role or team you invited them to, before they have an account, so they know what they are joining. Anyone the invitation link is forwarded to can see the same.

With service providers

We share data with companies that run parts of EventLink for us. They may only use it to provide their service to us, not for their own purposes.

Our website and app also load fonts and icons from third-party networks (Google Fonts, Bunny Fonts and Iconify). Doing so reveals your IP address to them, as it would to any website you visit.

Blog posts may embed videos hosted by YouTube or Vimeo. We use their privacy-enhanced players (youtube-nocookie.com, and Vimeo with Do Not Track), but opening a page that contains one still reveals your IP address to that provider, and anything you do inside the player is subject to its own privacy policy.

International transfers

We are based in Thailand, and the providers above are mostly outside Thailand, principally in the United States, the EU and Singapore. That means your personal data is transferred across borders. Where the law requires it, we rely on appropriate safeguards such as the European Commission's Standard Contractual Clauses, and we only work with providers that commit to protecting the data they handle for us.

Thailand has not certified the United States as having adequate data protection. We send what you type, say or upload to Anthropic, and voice notes to OpenAI, in the United States, because that is where the services that plan your events run, and sending it is necessary to provide the feature you asked for. They process it only for us, may not train their models on it, and delete it within 30 days unless it is flagged for misuse or the law requires them to keep it longer.

Other disclosures

We may disclose personal data if we are legally required to, if we need to protect our rights or someone's safety, or as part of a merger or acquisition, in which case we will tell you before your data becomes subject to a different policy. We do not sell your personal data.

5. Cookies, Analytics and Tracking

We use a small number of essential cookies to keep you signed in and to remember your language preference. These are required for the service to work and cannot be turned off.

We also set a cookie that remembers how you last signed in on this device, with Google or with an email link, so the sign-in page can point you back to it. It holds only that choice, never your email address, lasts a year, and stays after you sign out; clearing your browser's cookies removes it.

While you are signed in to the app, we also set a cookie on .eventlink.dev so that this site can show you a button back to your workspace instead of the sign-in buttons. It says only that this browser is signed in, never who you are. It is removed when you sign out, or the next time you open the app after your session has ended, and lasts at most 30 days.

We use PostHog for product analytics. In the app, analytics and session replay are off until you agree to them; you will see a banner asking, you can reject it, and you can change your mind at any time in your privacy preferences.

Session replay is not a video and does not use your camera or microphone. It reconstructs clicks and page changes so we can find usability problems, and everything you type, together with the content of your events, is masked before it leaves your browser — we see where people get stuck, not what they wrote. Replay is switched off entirely on the pages that carry a sign-in link, an invitation, or an email-verification link. Recordings are kept for 30 days and then deleted; the window is a setting held by PostHog rather than by us, so we state the period they currently apply rather than promising one we do not control. Our ordinary analytics events are masked the same way, and carry no text you have typed or entered.

On this website (eventlink.dev), analytics are also off until you agree: a small card asks on your first visit, and nothing is recorded if you say no. You can change your answer at any time with Cookie settings in the website's footer. Session replay is never used on this website.

One honest caveat. We record a small number of core business events server-side (for example: an account was created, an event was created) so we can count how the product is doing. These are tied to your account rather than to a cookie, and they are recorded regardless of your cookie choice. If you would rather we did not, contact us and we will remove you.

Our analytics cookie is set on .eventlink.dev, which means the same visitor is recognised across the marketing site and the app. We do not use advertising cookies, and we do not track you across other companies' websites.

6. Data Security and Retention

We protect your data with encryption in transit (HTTPS everywhere), sign-in links and codes that are single-use, short-lived, tied to the browser that asked for them, and stored only as SHA-256 hashes, strict role and permission checks on every request, and rate limiting against brute-force attacks. Photos you upload are re-encoded on upload, which strips embedded metadata such as GPS coordinates before we store them. Access to production data is limited to the people who need it.

No system is perfectly secure, and we will not pretend otherwise. If we ever suffer a breach affecting your personal data, we will notify you and the relevant regulator as the law requires.

We keep your personal data for as long as your account exists. When you delete your account, we delete your profile and personal records immediately; this is a real deletion, not a hidden flag. That includes any workspace only you are in, with everything in it, and anything that still holds your email address: sign-in links and the invitations sent to you, including ones you had already accepted. You are signed out everywhere. Content you contributed to a workspace (such as events and tasks) may remain with that workspace so your colleagues' records stay intact, but it is unlinked from you. We may keep the minimum necessary to meet legal obligations or resolve disputes.

When a workspace's owner deletes the workspace, everything in it (its events, tasks, notes, files and the list of who belongs to it) is hidden from everyone straight away but kept for 90 days, so the owner can restore it if the deletion was a mistake. After 90 days we delete it permanently, files included.

A referral record outlives the account it came from. If you signed up through a referral link and later delete your account, we sever the link to you and to your workspace; what remains is the code that was used and the date, which identifies nobody. We keep that indefinitely.

Some things we deliberately keep for less than that: the conversations you have with the AI when creating an event, which we delete after 90 days, the IP addresses recorded against AI generations, and the IP address saved with a contact form, a waitlist sign-up or a piece of feedback, which we clear after 90 days. What the assistant remembers about you is deleted 12 months after the event it is about ends, or sooner as described in section 3.

When you ask for a sign-in link, we store the address we sent it to — even if you never go on to create an account — together with the hashes of the link and the code, and the times they were issued and used. We keep that for seven days after the link expires, so we can tell you whether a link was actually sent; a nightly job deletes it after that, or straight away if you delete your account.

Server logs and backups. Our application logs are held by our hosting platform (Laravel Cloud) and our error-monitoring provider (Sentry), and are deleted automatically once they pass those providers' retention windows; we do not keep our own indefinite archive of them. Database backups are taken automatically by our hosting platform, which encrypts every database and backup at rest and in transit by default, and they expire on that platform's retention schedule.

7. Your Data Protection Rights

Wherever you live, you can ask us to: access the personal data we hold about you; correct it if it is wrong; delete it; export it in a portable format; object to or restrict how we use it; and withdraw consent you previously gave. You will never be treated differently for exercising these rights.

How to actually do it

• Delete your account: in the app, under Settings → Account. If you own a workspace that other people are in, hand it over to one of them first. A workspace only you are in is deleted with your account, along with everything in it.
• See, change or turn off what the assistant remembers about you: in the app, under Settings → Privacy.
• Change your cookie and analytics choices: via privacy preferences in the app, or Cookie settings in this website's footer.
• Opt out of marketing email: the unsubscribe link in any such email, or your notification settings.
• Get a copy of your data: we do not yet have a self-service export button. Email us and we will put your data together for you.
• Anything else: email hello@eventlink.dev.

We will respond within 30 days. We may need to verify who you are first, so that we do not hand your data to someone else.

If you are in the EEA or UK

You have the right to lodge a complaint with your local data protection authority. We would appreciate the chance to put things right first.

If you are in Thailand

The PDPA gives you the rights above, and you may complain to the Personal Data Protection Committee.

If you are in California

You have the right to know what we collect, to delete it, to correct it, and to opt out of sale or sharing. We do not sell or share your personal information, and we have not done so in the past 12 months. We do not knowingly sell the personal information of anyone under 16.

8. Children's Privacy

EventLink is business software for event teams. It is not directed to children, and we do not knowingly collect personal data from anyone under 13. If you believe a child under 13 has given us personal data, email us at hello@eventlink.dev and we will delete it promptly.

If you are between 13 and 20 and Thai law requires a parent or guardian's consent for you to use a service like ours, please get it before creating an account.

You may plan an event for your own child, such as a birthday or a naming ceremony. If so, you give any agreement we ask for, such as planning with AI, on your child's behalf as their parent.

9. Changes to This Privacy Policy

We will update this policy when what we do changes. When we do, we will revise the “last updated” date at the top. If the change is significant (new categories of data, a new purpose, a new kind of sharing), we will tell you directly, by email or in the app, before it takes effect. We will not quietly broaden what we do with your data and hope you do not notice.

10. Contact Us

Questions about this policy, or about your data? We would rather hear from you than have you wonder.