Privacy notice

What we store

Your account: sign-in email or the identity you signed in with (ORCID, GitHub, Google), display name, year of birth (to apply the minimum age), locale. Your card: headline, bio, links, interests you declared and interests we imported from your public papers and repositories, the papers and repositories themselves (titles, links, years). Event data: which events you joined, what you said you were looking for there, your jam role, the people you said yes to, your matches, teams, meetings and messages with people you matched or connected with. Safety data: blocks, reports you filed, moderation outcomes. Technical data: session records (browser, IP, time), an immutable audit log of administrative actions. Private notes you write about people are visible only to you and are never used for matching.

Why we store it

To run the service you asked for: joining events, suggesting people with a stated reason, chat between people who both said yes, keeping your network afterwards (contract, GDPR art. 6(1)(b)). To keep people safe: blocks, reports, moderation, rate limits (legitimate interest, art. 6(1)(f)). To send you a digest if you keep it on (consent you can withdraw on the Me page). Matching is profiling in the GDPR sense. It only changes what you see, it never takes decisions with legal effect, and every suggestion shows its reason. You can object by deleting imported or inferred interests.

Who sees what

Other attendees see your card only inside events you both joined, unless you widen your visibility. Nobody can message you until you both said yes. Blocking makes you invisible to each other everywhere. Organizers see counts, never who matched whom. Moderators see a reported message only when a report targets it. Organizers may also post their announcements to everyone in their own community chat (Discord, Slack or Teams). Only the announcement, the event's name and a link go there, never who is attending, chats or reports. Those services have their own privacy terms. We do not sell data, show ads, or rank anyone higher for money.

Where it lives

Servers in the EU. Backups are encrypted and stored with a second European provider. Card imports read public data from Crossref, OpenAlex and GitHub using only the identifier you linked; embeddings for matching are computed from your card text with an opaque id, never your name or email.

How long

For as long as you have an account. Sessions expire after 30 days of inactivity. When you delete your account we remove your card, identities, sessions, event participations, blocks, posts and notifications at once; reports and moderation records are kept without your identity; the audit log keeps the fact that an account was deleted.

Your rights

Export everything about you as one file from the Me page. Delete your account from the Me page, immediately, no email required. Correct anything on your card yourself. Object to matching by removing interests. For anything else, or to complain, write to us; you may also complain to your data protection authority (in Norway, Datatilsynet).

Cookies

Two first-party cookies keep you signed in (a short-lived access token and a rotating refresh token). No tracking cookies, no third-party analytics.

Controller and contact

The controller is the Ekimeet project (operator details to be completed before launch). Contact: privacy@[network-domain].

Changes

Changes that affect your data are also listed on What's new:

• You'll hear when the rules or the privacy notice change (Oct 15, 2026)
• Organizers can add helpers for one event (Oct 15, 2026)
• "Got it" on important announcements (Oct 15, 2026)