eveRater
Privacy

What we store, and what we refuse to.

Everater exists to tell an organiser what happened at their event without telling them what any individual did. That is a product decision before it is a legal one, and most of this page is the consequences of it.

In effect 10 September 2026 · Everater is operated by Oxvelo, Freeport, New York, United States · hello@everater.com · This English text is the authoritative version.

If you are reading this page

The public site sets no cookies and runs no analytics, no advertising tags and no third-party trackers.

On your device
Two items in your browser's local storage, and nothing else. everater.lang remembers which of the twelve languages you chose. everater.event remembers which event you opened, so the app goes straight there instead of asking you again — it holds the event's public short name, nothing about you, and the Not your event? link at the foot of any guide clears it. Neither ever leaves your device, and you can clear both with your browsing data.
Fonts
The page loads typefaces from Google Fonts, so Google receives your IP address and browser details in order to serve them. That is the only third party involved in this page.
Our own logs
Cloudflare serves the site and keeps standard request logs on our behalf, which include IP addresses, for a short operational retention period. We do not query them for anything other than diagnosing faults and abuse.

If you use the contact form

We store what you type — your name, email address, your event, where its programme is published, and your message — plus the country Cloudflare reports for the connection. We use it to reply to you and to prepare your event, and for nothing else. We do not sell it, share it, or add you to a mailing list. Ask and we delete it.

If you are an attendee at an event

This is the part that matters most, because it is where a schedule app would normally start collecting.

You do not need an account, and there is nothing to sign up to. Your plan is held against a short random code generated in your browser — something like BSC-4K2P-9XQF. The code is not derived from anything about you and is not linked to a name, an email address or a device.

Your plan
The sessions you added, stored against that code.
Ratings
A score and, if you write one, a comment. The ratings table has no column for who wrote them and never will. Stopping you rating the same class twice is done with a one-way hash of your plan code, which works without knowing whose code it is.
Counting opens
Per event, per day: how many times the guide was opened, the language your browser asked for, and the country of the connection. These are counters, not records — there is no row that represents a visit, so there is nothing to trace back to a person.
Location
If you rate a session, your browser may ask permission to confirm you are at the venue. The coordinates are compared against the venue's own position and discarded in the same request. No location is written to the database, ever.
Email, only if you ask
You may optionally give an address to get your plan on another device or to receive reminders. That is the only place an attendee's email exists, it is entirely optional, and removing it is one tap in the app — after which your plan and ratings remain, still anonymous.

What the organiser sees

Aggregates. How full a room was against what it holds; which slots were quiet; how sessions were rated. Ratings are suppressed below a threshold, which is both a privacy rule and an honesty one — an average of three ratings is not worth printing.

An organiser cannot buy an individual profile from us. That rule has to survive the first time somebody offers real money for one, so it is enforced in the database rather than in a policy: the columns that would make it possible do not exist.

If you are an organiser

Your account
Your email address, which is how you sign in — there is no password to leak or reset. A sign-in cookie is set on docs.everater.com and your own subdomain, lasting fourteen days.
Reading records
When a gated document is served we record which address opened which document and when. This is how we know a link we sent was received.
Your programme
The factual content of a timetable you published: who is teaching what, when, in which room. Not your prose, images or design.

Programmes we read before you were a customer

We build events from timetables organisers have already published on the open web, so that we can show an organiser their own event working rather than describe it. If that is your event and you would rather we did not hold it, write to us and it is removed — you do not have to be a customer, and you do not have to give a reason.

The same applies to the comparison we draw between events. It is a median across at least five comparable programmes, never a named one, and any organiser can ask to be excluded from it.

What we never collect

  • No advertising identifiers, and no advertising.
  • No attendance record of which person went to which session.
  • No stored location, of anyone, at any time.
  • No payment card, bank or account numbers — the database refuses them outright.
  • No purchase of personal data from anybody else.
  • No sale or sharing of anything above with anybody, for any purpose.

Where it is held, and for how long

Data is stored on Cloudflare's platform. Cloudflare and Google Fonts are our only processors; both may serve requests from outside your country, and for readers in the UK and EEA that means personal data may be processed in the United States under the transfer safeguards those providers publish.

Counters
Kept indefinitely. They describe days and events, not people.
Plans and ratings
Kept while the event is on the platform, so an organiser can see what happened at their own event afterwards.
Enquiries
Kept while we are talking, and deleted on request.
Sign-in sessions
Fourteen days, then expired.

Your rights

Wherever you are, you can ask us what we hold about you, ask for it in a readable form, ask us to correct it, or ask us to delete it. If you are in the UK or the EEA those are rights under the GDPR, and you may also complain to your national data protection authority; if you are in California you have comparable rights under the CCPA, including the right not to be discriminated against for using them.

One address handles all of it: hello@everater.com. We answer within thirty days.

For attendees this is usually simpler than it sounds. If you never gave us an email address, we hold nothing that identifies you — which means there is no account to close and, honestly, nothing for us to look up. To remove your plan, delete it in the app or stop using the code.

Children

Everater is not directed at children and we do not knowingly collect information from anyone under 16. Events on the platform are attended by people of all ages; the app asks nothing of them either way, because it asks nothing of anybody.

Changes

If this policy changes materially we will change the date at the top and, where the change affects data already held, say so on the front page rather than quietly revise the text.