Last verified: 15 September 2026
What happens to your event’s data
If you put 500 people into a platform you have never used, the question is not what features it has. It is what happens when something goes wrong. Below are the answers, each with the mechanism behind it. Every line was checked in the product running right now, not in a document.
My data reaches another organizer
The separation is done by the database, not by the application. Every table holding event data has row-level access policies, enforced so that they apply even to the table’s owner: attendees, meetings, messages, scans, booth leads. The role the application connects with has no right to bypass them, and the application refuses to start if it is given one. What that means in practice: a programming error cannot leak data from one event into another, because the query returns no rows — it is not a check someone can forget to write. The boundary, so you know it exactly: platform tables — accounts, the list of events, organizations, our admin logs — have no per-event policies, because they are not event data.
I cannot get my list back out
Exporting the attendee list is available on every plan, including the free one, and is not gated by anything. It exports the whole list, with email addresses. The only limit is rate — 30 requests per minute — so that a stolen console session cannot pull the catalogue indefinitely. Booth leads and the scan log export separately.
I do not know where the data goes
To a rented server in Germany, at Contabo GmbH: the application, the database, the backups and the mail server. There is no second processing location. In front of it sits Cloudflare, a US company, through whose network requests to the site pass while in transit; the transfer relies on the EU–US Data Privacy Framework. The full supplier list, with what each one processes, is public.
If I pay late, I lose my event
No. Beyond 30 days late we may suspend access to paid features, after a notice sent five days in advance. Suspension does not delete the event’s data.
The data stays there forever
It does not. Twenty-four months after the event ends, attendees’ personal data is anonymised automatically; the scan log at 12 months. Anonymisation is irreversible and uses exactly the same operation as an erasure requested by an attendee, so the word “deleted” cannot have two meanings. An attendee can download their data and request erasure themselves, from the app, without going through you and without writing to us.
Someone on your team looks at my list
There is no standing access. When you ask for help, a support session is opened for your organization specifically, with the reason written down — it is required — and it expires by itself after two hours. The opening is recorded in two places: in our admin log and in your organization’s log. Consulting an event’s scan log is recorded before the data is returned, with the author, the event and the filter used. What you can see yourself, today: changes made in an event’s console — who changed what and when — under Settings → Advanced, inside that event. The organization’s log, where support sessions live, is under “My account”, if you are its owner.
There is an incident and I am the last to know
We have a written procedure and a register of all incidents, including those that are not notified. If there is a personal data breach in data we process for you, we tell you without undue delay and within 48 hours of becoming aware — so you can meet your own 72-hour deadline towards the authority. Reports sent from the site get an answer within 1–48 working hours, counted Monday to Friday, 10:00–16:00 Romanian time.
You lose the data and have nowhere to get it from
The database is backed up in full every night and the copies are kept for 14 days. Restoring is not assumed: we rebuilt the database from a daily copy on a separate system and checked not only that the data was there but that the application can read it — the runtime role’s grants and a real read in an event’s context. The weak part is below, under “what we do not have”.
My account is one weak password away from trouble
We use no passwords at all. You sign in with an access link or a one-time code sent by email, and the code is never stored in the clear. The session lives in a cookie that page scripts cannot read, is sent only over a secure connection, and lasts at most 30 days. Access to the site is HTTPS only, with the transport security header declared for two years and entered in browsers’ preload list — meaning the browser refuses an unencrypted connection before opening it.
My attendees’ data ends up in who knows what services
We use no external analytics, error monitoring, bulk email or file storage services. We have no ads and no tracking tools. We do not sell or lend lists. The scan log does not keep IP addresses.
What we do not have
If you have read this far, you are checking. Then you need this part too — and you would find it anyway, better from us.
- We have no ISO 27001 or SOC 2 certification, and we are not externally audited. We compensate with transparency: the supplier list by name, the technical measures and the data processing agreement, all public.
- We do not claim encryption at rest. It is not confirmed in the stack we use, so we do not state it.
- The backups sit on the same server as the database. A total loss of the server would mean losing the copies along with the data. It is the most serious limitation on this list.
- We have no external availability monitoring, so we promise no availability level and cannot guarantee that we learn of an outage immediately. A nine-minute incident went unnoticed.
- We do not require two-factor authentication for platform administrators. Administrative access is protected by a separate, 12-hour, logged session — not by a second factor.
What comes next
In this order: a backup in a second location, and only then the conversation about certifications. If you need something specific in order to sign, write to us — it helps to know what blocks you, not only what is missing.
The documents
The technical and organisational measures are the technical annex to the data processing agreement and contain the same facts, written for someone verifying compliance. From there you also reach the data processing agreement, the privacy policy and the subprocessor list. Questions about any of them: salut@emisar.ro.