Privacy policy
Last updated 5 November 2026
This policy explains what personal data we process, what we use it for, how long we keep it and what rights you have. It covers our service, apps and Badges, as well as our website and the handling of customer relationships.
1. Data controller
Ninja-Tech Oy (Business ID 3652975-8), Kalliopääntie 4, 10300 Karjaa, Finland. We make electronic e-ink name Badges and the software that runs them, and rent the Badges to event organizers, our partners ("Organizers"), for their Events.
Privacy questions and requests: info@ninjatech.fi. We have not appointed a data protection officer, as the law does not require one for us; the address reaches the person responsible.
2. What this policy covers
This policy covers:
- the web app (app.ninjatech.fi), where Organizers book Events, upload attendee lists and design Badges
- the Event app (Apple devices and Android), used on site to hand out and fix Badges after entering an Event code
- the Warehouse app (Apple devices) and Ops, used only by our own staff
- the Badges themselves, which show an attendee's details during an Event
- our website (ninjatech.fi), its contact form and email with us.
For attendee data, the Organizer decides what is collected and why; we handle it on their behalf (section 5).
3. What data we process
| Who you are | What we process | Where it comes from |
|---|---|---|
| Contact form user or customer | Name, organisation, email address and phone number; the event's date, venue, attendee count and whatever you describe in your message; quotes, orders, invoicing details and correspondence history | You |
| Website visitor | Technical server logs such as IP address and browser identifier, to keep the service running and secure | Your browser |
| Organizer user (web app) | Name, email address, your Google or Microsoft account identifier if you sign in with one, your passkey if you add one, your language choice, your organisation and role; the IP address and browser identifier of your sign-in session | You, your browser, and Google or Microsoft if you sign in with them |
| Event attendee | What the Organizer uploads: typically first and last name, company, title, email, an external ID and any custom fields the Organizer adds; which Badge you were given and changes made on site | The Organizer; on site, the person using the Event app |
| Walk-in attendee | First name and the details above, plus your phone number, so we can reach you if the Badge is not returned | You, through the person using the Event app |
| Person using the Event app on site | The first name you enter (you can skip it); a random identifier for your installation; a one-time check that the phone is at the venue when the Event code is entered (kept only as near, far or unknown); a check that the app is genuine (Apple App Attest or Google Play Integrity); the network address of wrong Event code attempts; a problem you report and its technical details | Your phone |
| Person an Event code is sent to | Email address and the details of the send | The sender: our staff, or someone using the share link |
| Everyone using our apps | Which screens are opened and which features are used, app version and platform, without cookies and without what is shown on screen; error reports with the technical state of the app | The apps |
| Our staff | Name, email, role and a log of actions in Ops and the Warehouse app | Our staff |
The Badges store only what is drawn on their screen and are cleared to white when they come back from an Event. We do not track attendees' movements: Gateways and phones listen for Badges to write to them, check their battery and find them for return.
Providing your details is not a legal requirement. An Organizer needs an account to book Events; an attendee who gives no details gets no name on their Badge.
4. Why we use it, and on what legal basis
| Purpose | Legal basis (GDPR art. 6) |
|---|---|
| Preparing quotes and answering enquiries, giving Organizers an account, taking bookings, invoicing | Preparing and performing a contract (6(1)(b)) |
| Managing the customer relationship and securing the service | Our legitimate interest (6(1)(f)) |
| Producing and fixing attendees' Badges for an Event | On the Organizer's behalf, under our processing agreement (section 5) |
| Contacting a walk-in whose Badge was not returned | On the Organizer's behalf; the Organizer's legitimate interest in getting its rented Badges back |
| Checking that the Event app is genuine and at the venue, and stopping wrong Event codes | Our legitimate interest in keeping Events and attendee data safe from misuse (6(1)(f)) |
| Usage statistics and error reports | Our legitimate interest in fixing faults and improving the apps (6(1)(f)) |
| Bookkeeping and accounting records | Legal obligation under the Finnish Accounting Act (6(1)(c)) |
We do not sell or rent personal data, use it for advertising or make automated decisions that have legal or similar effects on you. Where we rely on legitimate interest, you can object (section 9).
5. Attendee data: the Organizer is in charge
When an Organizer uploads an attendee list, the Organizer is the controller of that data and we are its processor (GDPR art. 28). We use it only to produce Badges and run that Event, under our Data Processing Agreement.
Attendees should ask the Organizer first about how their data is used; we help the Organizer answer and pass on any request we receive.
We delete attendees' personal data 30 days after the Event is archived (an Organizer can choose up to 90 days). An Event is archived once all its Badges are returned or marked lost. Counts with no personal data, such as how many Badges an Event used, are kept.
6. Who we share it with
Only with service providers that run parts of our service for us, under contracts that limit them to our instructions:
| Provider | What they do for us | Data they handle |
|---|---|---|
| Cloudflare | Hosting, database, file storage and network | Everything stored in our service |
| Sign in with Google; Google Play Integrity for the Android Event app; our company email (Google Workspace) | Your Google identifier and email; an app integrity check; email between you and us | |
| Microsoft | Sign in with Microsoft | Your Microsoft identifier and email |
| Apple | App Attest for the Apple Event app; TestFlight and the App Store | An app integrity check |
| Sentry (EU region) | Error reports | Technical state of the app at the error, app version |
| PostHog (EU region) | Usage statistics | Screen and feature names, app version, random or hashed identifiers |
| Brevo | Sending the service's email, such as sign-in and invitation links and Event codes, and passing website contact form messages to us | Name and email address; what you write on the form |
We also disclose data when the law requires it, for example to the authorities. Organizers see their own Events' data in the web app.
7. Transfers outside the EU/EEA
Sentry and PostHog store our data in the EU. Brevo is a French company and stores our data in the EU. Cloudflare, Google, Microsoft and Apple are US companies and may process data outside the EU/EEA. They are certified under the EU–US Data Privacy Framework, which the European Commission has found adequate, and also use the Commission's standard contractual clauses.
If another provider processes data outside that area, the transfer relies on a Commission adequacy decision or on standard contractual clauses. Ask us for a copy of the safeguards at the address in section 1.
8. How long we keep it
Deletions run as a daily job, so data can go slightly after the time shown.
| Data | How long |
|---|---|
| Enquiry data | 24 months from the last contact, if it doesn't lead to a customer relationship |
| Customer relationship data | For the duration of the agreement and afterwards for as long as the law requires |
| Attendee personal data, including walk-ins' phone numbers and names drawn for Badges | 30 days after the Event is archived (up to 90 if the Organizer chooses). The drawing of a finished Badge write goes 90 days after the write was made, if that is sooner. |
| Backups | Deleted after about 30 days, so data removed from our live systems can stay in a backup for about 30 days more |
| Event app first name and installation identifier | Removed from our live systems 90 days after being recorded; a phone still paired to a long Event keeps its own record until 7 days after its access ends |
| Attendee data on a phone using the Event app | Until 2 days after the Event |
| The on-site activity log, reported problems and Event code sends with their addresses | 90 days |
| Network address of wrong Event code attempts | 1 hour |
| Organizer user accounts and their sign-in sessions | While the account is in use, then 12 months after the last sign-in (or after it was created, if you never signed in) |
| Logs of changes made by our staff and by Event apps | 2 years |
| Invoices and bookkeeping records | 6 years after the end of the financial year; financial statements 10 years, as the Accounting Act requires |
| Error reports | 30 days |
| Usage statistics | 12 months; they identify no named person |
9. Your rights
Under the GDPR you have the following rights:
- The right to access your data and request a copy.
- The right to have incorrect or incomplete data corrected.
- The right to erasure once there is no longer a basis for processing.
- The right to restrict processing and to object to processing based on legitimate interest.
- The right to data portability for the data you provided.
- The right to withdraw consent at any time where processing is based on consent.
Send your request to info@ninjatech.fi. We respond within one month. We may ask you to verify your identity before releasing data. A request about attendee data goes to the Organizer, who decides on it (section 5).
If you believe we process your data unlawfully, you can lodge a complaint with the Finnish Data Protection Ombudsman (tietosuoja.fi) or the authority where you live or work.
10. Security
Data is encrypted in transit and at rest. Only our staff with a need can see it. Changes our staff and Event apps make to an Organizer's data are logged with who made them, and an Event app installation can see only its own Event.
11. Children
Our service is for businesses and organisations. Organizers decide who attends their Events; we do not knowingly collect children's data for any other purpose.
12. Cookies
This site uses no tracking or advertising cookies and does not profile visitors. It uses only cookies strictly necessary for it to function, which do not require consent. If we add analytics to the site later, we will ask for consent separately and update this policy.
The web app and Ops use only cookies needed for signing in and, in the web app, for remembering which organisation you are looking at. The apps send usage statistics without cookies or advertising identifiers.
13. Changes to this policy
We update this policy when our service or our data processing changes. The current version is always on this page, and the update date is shown at the top. We tell Organizers by email about significant changes.