Privacy Policy
Updated: 26 October 2026
This Policy describes how AnyEventTool (“AET”, “we”, “our service”) collects, stores and uses data from users who interact with the site anyeventtool.com and related products.
1. Service
AnyEventTool is a web app for event organizers: event pages, registration and tickets, QR check-in, live quizzes, calendars and communities.
Communication: support@anyeventtool.com
2. What data may be collected
- contact details (name, email, other details specified by you);
- technical data (IP address, browser type, access time, country);
- data from participation in events, registration forms or feedback forms;
- analytical data that collects Google Analytics 4 (summarized and anonymous).
We process data only to run the service for event organizers and their guests. We do not collect personal data that directly identifies an individual without your consent.
3. How we use data
- to provide and improve service features;
- for statistics, analytics and protection against abuse;
- for communication with users (notifications, technical support).
4. Analytics and third-party services
We use the following third-party services:
- Google Analytics 4 (GA4) — to collect anonymous visit statistics. GA may use cookies.
More details: How Google uses information from sites or apps that use our services - Supabase — for storing accounts and event content (servers may be in the EU or the USA).
We do not share your personal data with third parties for advertising or sales.
The full list of processors and data transfer terms is in section 9.
5. Your rights
You can:
- view or update your data;
- request account deletion;
- withdraw consent to the processing of personal data by deleting your own data or contacting the organizers.
6. Security
Data security in Supabase is ensured through user authentication (Supabase Auth) and Row Level Security (RLS) - policies that control access to data. All connections are made via TLS encryption, and data is stored in PostgreSQL with support for roles, tokens, and secure access rights management. However, no online system can guarantee absolute security.
7. AI assistants and page drafts
If you ask an AI assistant (such as Claude or ChatGPT) to create an event page in AET, the assistant sends us the content you gave it: title, date, venue, description, programme, speakers' names and bios, links and design wishes. We store it as a draft. Your conversation with the assistant is processed by its provider under its own terms — we only see what the assistant sends us.
- A draft lives for 24 hours. If you don't claim it into your account, it is deleted together with its technical keys.
- Until a draft is claimed, registration and payments on it are switched off — we collect no visitor data beyond anonymous view statistics.
- Draft texts are checked by automated moderation (OpenAI Moderation); links inserted by an assistant are marked for search engines as user content (nofollow).
- We keep a log of AI actions: which assistant changed what on the page and when. So that a change can be undone, the previous content of the changed sections is kept with the log entry for 30 days; after that only the record of the action remains. The log is kept for 12 months; IP addresses in it are truncated after 30 days.
- Photos of people on a draft are only those you provided or stock images.
- If you connect an AI assistant to your account — by signing in from the assistant (OAuth) or with an access key you create in the cabinet (My workspace or event cabinet → «AI agent») — we store the connection's name, its access level (preview only; selected events, optionally together with the events the assistant creates itself; or all events), the dates it was created and last used, and only fingerprints of keys and tokens. With a connection the assistant sees the list of your events and manages only those its access allows; it receives aggregate statistics without guests' names or contacts. You can change the access or revoke a connection at any time; when you delete your profile, all connections stop working at once.
8. AI assistants' access to your account
You can give an AI assistant access to your account in two equivalent ways: sign in to AET from the assistant (OAuth) or create a key in the cabinet. Either way you choose one of three access levels: preview only; selected events (optionally together with the events the assistant creates itself); or all events; the assistant cannot widen its own access. We store the connection's name, its access level, the dates it was created and last used, fingerprints of keys and tokens (never the secrets themselves), and a log of the assistant's actions (12 months; IP addresses are truncated after 30 days; undo snapshots are kept 30 days). You can change the access or revoke a connection at any time in the cabinet ("AI agent"); all connections stop working when you delete your profile. The assistant receives your events' data and aggregate statistics; participants' names, emails and phone numbers are not shared with AI assistants.
9. Roles, processors and data transfers
For your participants' data the organiser is the controller and AET is a processor acting on the organiser's instructions. For drafts created by AI assistants, AET is the controller until the draft is claimed.
We use these processors: Supabase (database), Vercel (hosting), Cloudflare (file storage, network), Resend (email), OpenAI (AI features and moderation), Google (analytics, translation, image recognition). Some of them process data outside the EEA (including the US) under the European Commission's Standard Contractual Clauses.
The service is intended for organisers aged 18 or over.
10. Sign in with Google (Google user data)
When you sign in with Google (the “Sign in with Google” button or the Google One Tap prompt), Google shares only basic profile data with us: your name, email address, profile picture and Google account ID. We do not request access to Gmail, Google Drive, Calendar, contacts or any other data in your Google account.
- How we use it: to create your AnyEventTool account and sign you in, to show your name or email in your workspace, and to send service emails (sign-in, tickets, payments, support). We do not display or use your profile picture.
- How we store it: in our database (Supabase) together with your account; all connections are encrypted (TLS). We never see or store your Google password.
- Sharing: we do not sell Google user data, use it for advertising or to train AI models, or share it with third parties — except the processors listed in section 9 that the service cannot run without (database and hosting).
- Deletion: you can delete your profile in your workspace — after a 30-day recovery window your account and all this data are erased — or email support@anyeventtool.com. You can revoke AnyEventTool's access to your Google account at any time at myaccount.google.com/permissions.
AnyEventTool'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.
11. Changes to the Policy
We may update this Policy from time to time. The most current version is always available on the page anyeventtool.com/privacy.