Version dated 2026-10-08
01Controller and contact details
Roberto Drago provides Every One Seated and is the controller for account, support, billing, security and service analytics processing. For privacy questions or to exercise your rights, write to hello@robertodrago.dev. For guest data, also see the section on the organiser’s role.
02What we collect
We collect your email and account identifier, any name supplied by your sign-in provider, and events, floor plans, images, guest lists, notes and RSVP answers entered by users. We also process plan and transaction information, support requests and technical data needed to deliver and secure the service, such as IP addresses and error logs.
03How we use it
We use data to authenticate users, store and sync content, manage collaborators and invite or RSVP links, verify subscriptions, provide support and prevent abuse. Email and an identifier are required for an account; optional event data depends on the organiser’s choices.
04Purposes and legal bases
Account features and subscriptions rely on performance of a contract or pre-contractual steps (GDPR Article 6(1)(b)); tax and other statutory duties rely on legal obligations (Article 6(1)(c)). Service protection, abuse prevention and server diagnostics rely on legitimate interests in security and reliability (Article 6(1)(f)), subject to the right to object. Optional browser and app statistics rely on revocable consent (Article 6(1)(a)). The organiser must determine and explain the applicable legal basis for guest data.
05Your guests' data
The organiser decides which guest data to collect, why and with whom to share it. When acting as controller, the organiser must inform guests and respect their rights; EOS processes this content to provide the service. Collaborators have access according to assigned permissions. Send RSVP and share links only to intended recipients: a name lookup does not verify identity. Allergies, intolerances and other notes may reveal health or religious information; enter them only where necessary and with a valid GDPR Article 9 condition, such as explicit consent where applicable. Contact the organiser about invitations or answers.
06Signing in
You sign in with a one-time code sent to your email, or with Sign in with Apple or Google. We receive your email address and, if the provider shares it, your name. We never receive your Apple or Google password.
07Analytics and error reports
Browser statistics and errors are sent to PostHog only after acceptance in the banner; decline or withdraw through Privacy preferences. App consent is managed in Account. Technical identifiers, device and usage data and error details are not necessarily anonymous merely because they omit names or email. Web identifiers stay in memory; URLs are filtered to remove tokens, parameters and event identifiers. Session recordings are disabled. Server error diagnostics are separate from optional usage statistics.
08Payments
Apple and Google charge purchases in their stores; RevenueCat verifies subscriptions and access rights using user identifiers and transaction data. Web purchases use Stripe when payment is available. EOS receives plan status and transaction references without storing full card numbers. Payment providers also process data for their own statutory duties under their privacy notices.
09Who processes your data
Providers include Supabase (database, authentication and files), Vercel (hosting), Resend (sign-in email), PostHog (statistics and diagnostics), RevenueCat (subscription verification) and Stripe (web payments). Apple and Google provide sign-in and store purchases. Roles depend on the processing: processors follow contractual instructions, while sign-in and payment providers may also act as independent controllers. Data may be disclosed to authorities where required by law.
10Providers and international transfers
Cloud services may involve access or processing outside the European Economic Area. The configured PostHog endpoint is European; that does not mean every provider or processing activity stays in the EU. Transfers require an adequacy decision or applicable safeguards, such as standard contractual clauses and any necessary supplementary measures. For information about processing regions and applicable safeguards, or to request a copy, write to hello@robertodrago.dev.
11Retention and deletion
Account data and content are kept while needed to provide the service and until deletion or an applicable request. Shared team content may remain available to other members after you delete your account. Records needed for tax obligations, disputes or security are kept for the period required by their purpose or by law. Queued file deletion and backup copies follow separate processes: account deletion does not immediately erase every copy. Privacy requests remain available even if automatic deletion is blocked by a subscription or team ownership.
13Your rights
Where the GDPR applies, you can request access, rectification, erasure, restriction and portability, and object to processing based on legitimate interests. You can withdraw consent without affecting earlier lawful processing and complain to the Italian data protection authority or your competent authority. We normally respond within one month, subject to lawful extensions; we may request proportionate information to verify identity. You can also contact the event organiser about event data. Account deletion in Account is irreversible and does not itself cancel subscriptions. To exercise these rights, write to hello@robertodrago.dev.