Privacy Policy
This policy is written to match how this site and the Metrica application actually work — not to describe a hypothetical business. Every statement below can be checked against the running system.
Who is responsible
Metrica is a product of Arcana Noctis (“we”, “us”). Arcana Noctis is the controller of the personal data described here: it decides why and how that data is used. Write to andrei@metricahq.com with “Metrica privacy” in the subject line.
If you have an account through your employer, your organisation decides what is entered into Metrica and is the controller of that content; we process it on their instructions. Ask them first — they can answer most requests, including access and deletion, without involving us.
The short version
- The public site sets no cookies, runs no analytics and loads nothing from a third party — the security policy makes external requests impossible, not merely unused.
- The application sets one cookie, to keep you signed in.
- We do not sell data, we do not advertise, and we do not build profiles.
What the public site collects
- Nothing you type — the site has no forms.
- No cookies. A response from this site carries none.
- Nothing stored in your browser beyond the copy of the site's own pages that the service worker keeps so it opens offline. That copy stays on your device, contains no personal data, and disappears when you clear site data.
- Ordinary server data. A request reaches our server the way it reaches any server: IP address, browser identification, time and the address requested. Our hosting provider keeps standard server logs under its own policy. We do not use them to profile anyone or to target advertising.
What the application collects
The application at /app/ is metrica's working tool, so it has to
hold real business records. This is the complete list.
| What | Why |
|---|---|
| Your name, email address, role, organisation and language | To sign you in and to decide which records and pages you may see. |
| A one-way hash of your password — never the password itself | To check your password at sign-in without storing it. Weak hashes are upgraded automatically at the next sign-in. |
| The time you last signed in | To show an honest session and audit history. |
| Invitation records: the invitee's email address, the role offered, an expiry time, and a hash of the one-time link token | To let an administrator add a colleague. We do not send email — the administrator copies the link and sends it. A stolen database cannot be used to redeem an invitation. |
| What your organisation enters: vehicles, suppliers, companies, business contacts (name, job title, email, phone, LinkedIn address), activities, follow-ups, opportunities and notes | That is the product. Your organisation decides what is entered, and is responsible for having a basis to enter it. |
| An audit trail: who changed what, when, on which record, with a short written summary | So a change can be attributed to a person. Field-level before and after values are not stored. |
| Failed sign-in attempts: the email address and a salted hash of the IP address | To slow down password guessing. The raw IP address is not stored, and the records are deleted after at most 24 hours. |
What the application does not collect
- Passwords in readable form, or any password that can be recovered.
- Raw IP addresses in the database.
- Payment card data — no payment is taken on this site.
- Location, contacts, microphone, camera or any device permission. The site forbids them in policy.
- Special-category data. Notes fields are free text, so please do not put health, belief or similar details in them.
Why we are allowed to process it
- To provide the service you or your organisation asked for — the account, the session and the records you enter.
- To keep it secure — the audit trail, the sign-in throttle and abuse prevention, on the basis of our legitimate interest in protecting the service and the data in it.
- To meet a legal obligation, where one applies to us.
Nothing here depends on advertising consent, because there is no advertising.
Cookies
The public site sets none. The application sets exactly one — the Cookie Policy lists it in full:
| Name | Where | Purpose | Lasts |
|---|---|---|---|
metrica_session |
Set at /app/ (cookie path /) |
Keeps you signed in between pages | 8 hours of inactivity, or until you sign out |
It is marked HttpOnly (unreadable by scripts),
Secure (sent only over HTTPS) and SameSite=Lax
(not sent by other sites). It identifies a session, not a person, and is not
used for tracking. There are no third-party cookies.
Who else sees the data
- The hosting provider, site.eu, which runs the server and stores the database. It is the only external party that handles the data.
- Nobody else. There is no analytics service, no advertising network, no content delivery network, no error tracker, no email service and no payment provider connected to this site.
- We do not sell, rent or trade personal data, and we do not share it for advertising or profiling.
We do not transfer personal data to any third country ourselves: there are no integrations and no third-party services in the application, and the server is in the Netherlands.
Where it is stored, and how it is protected
- The deployment runs on a shared hosting account provided by site.eu, in Amsterdam, the Netherlands (European Union).
- The database is a single SQLite file kept outside the public web
root, with permissions
0600; session files sit beside it with0700. Neither can be fetched over HTTP. - The site and the application are served over HTTPS only, with a strict transport-security header and a content-security policy that permits no external scripts, styles or connections.
- No scheduled backup copies are made. Snapshots taken during maintenance are deleted as soon as they have been used.
How long we keep it
| Record | Kept for |
|---|---|
| A signed-in session | 8 hours of inactivity, or until sign-out |
| Failed sign-in records | At most 24 hours; cleared on a successful sign-in |
| Account, records and audit trail | While the account exists |
| Server logs | According to the hosting provider's own policy |
When a deployment is removed, its database and session files are deleted with it. If you ask us to delete something, we do so within one month unless we are required by law to keep it.
Your rights
You have the right to:
- be told what we hold about you, and to receive a copy;
- have inaccurate data corrected;
- have data deleted;
- restrict or object to how it is used;
- receive your data in a portable form;
- complain to a supervisory authority — in Romania, the ANSPDCP, or the authority where you live.
Write to the address at the top and we will answer within one month. There is no charge. If your account is managed by your employer, contact them first.
Children
Metrica is a business tool and is not intended for children. We do not knowingly hold data about anyone under 16.
Changes to this policy
If this policy changes in a way that matters, we update the version and date at the top, and account holders are told inside the application. The date above is always the date of the current version.