Privacy by design
Privacy is a constraint on how neine is built, not a step after it. These are the promises every part of the product keeps.
Nothing tracks anyone
The app carries no tracker, no analytics script, no pixel and no asset loaded from a third party. Its pages load their scripts, styles, fonts and images from the app's own address.
The email neine sends carries nothing that reports its opening, and no link in it is rewritten to report a click.
An environment of its own
Each customer runs in an environment of its own. Your records are not held in a database shared with another customer, and no cloud resource carries your company's name in a tag.
Your data stays in its region
Your environment's data at rest, its database, its stores and its backups, stays in the region your environment is set up in. Two things cross that line, and only these:
- Email is sent through one email service in the EU, in Ireland, so the content of a message passes through it, and an address suppressed after a bounce or a complaint is kept there.
- Pages are delivered through a global network of edge locations. No personal data rests there, and no answer the app gives about your records is stored there or in any other cache, your browser's included.
Only what a function needs
neine collects a field of personal data only for a purpose one of its functions serves. Only contact details and the history of interactions are held about the people you work with.
Logs carry no names, no email or postal addresses, no telephone numbers and nothing a person typed. A log line identifies a request by its id, its route and the records it touched. The request log of a page a browser reaches also holds the network address, the browser string, the city and country the request came from and the fingerprint of its encrypted connection, for troubleshooting and for tracing abuse, and it is removed after a limited time.
An address in your browser's bar carries a record's id, never a name or anything a person typed.
Every change audited, without the data
Every change to personal data writes an audit row naming who did it, what they did, the record and the time. Where it says what changed, it names the fields and never their values, so the audit trail is not a second copy of the data. No one can change or delete an audit row.
Erasure that sticks
When a person asks to be erased, the request is accepted at once and closes them to contact there and then. Everything attached to them is removed in the nightly run. What remains is an anonymous note that an erasure happened and a one-way fingerprint of each identifier erased, which refuses any attempt to add the same LinkedIn URL or email again. Lifting that block is an administrator's action, so no one can quietly undo their own erasure.
People untouched for 13 months are deleted in the same nightly run, unless an open or won opportunity or a pending draft protects them. A person who lapses this way can be added again if they show fresh interest.
Encrypted at rest and in transit
Personal data at rest is encrypted under your environment's own key, and personal data travels only over an encrypted connection.
This website
This website is the one place we measure, so we know how people find neine. It uses cookieless analytics, sets no cookie and is covered by the privacy policy, which names the provider and what it collects.