Security
Last updated: October 2026
darji is operated by Nicolas David, trading as darji. This page describes how darji protects the data it holds, as things are today.
darji is a small team. It holds no security certification, such as ISO 27001 or SOC 2: what follows is what we do, and nothing more.
1. Where the data is
- The database, PostgreSQL hosted by Neon, is in London, United Kingdom. It holds accounts, learning progress and, for companies, their teams and seats.
- The site's server code runs on Vercel, in its London region. Pages that are the same for everyone are also served from Vercel's network around the world, and Vercel stores the site's audio files.
- Analytics, by PostHog, are hosted in the European Union.
- The services we use, and what each one does, are listed in section 8.
2. Encryption in transit
Every connection to darji uses HTTPS, and the site tells browsers to use nothing else (HSTS). The site's server talks to its database over an encrypted connection too.
3. Who can access the data
- Only darji's staff can open the Studio, darji's back office, with an account that has an editor or admin role. Every page and action of the Studio checks that role on the server.
- A staff member whose role is removed loses access within minutes.
- What staff do in the Studio is recorded in an audit log, including each time an admin opens the app as a learner to help them with a problem.
- The site reaches its database with a login that can read and write rows but can't change the tables. Changes to the tables are made separately, by hand, with another login.
- Passwords and keys live in the hosting's settings, never in the code.
- darji's team works remotely, including from outside the United Kingdom and the European Union. For companies, the Data Processing Agreement says how these transfers are covered.
4. Accounts
- Passwords are stored hashed with bcrypt, never as they were typed.
- Sign-in attempts are limited per address and per network.
- Signing in with Google is optional. darji then receives the person's name and e-mail address from Google, and nothing else.
5. Analytics and error reports
- No e-mail address goes to analytics: there, a person is an account number. Links that carry a secret, such as a password reset, are cut before anything leaves the browser.
- The Studio and other private screens are never recorded, and what people type is hidden in session replays.
- Anyone can turn analytics off on their device, from our Privacy Policy.
- Errors are reported to Sentry so that we can fix them.
6. Backups
The database is hosted by Neon, which can restore it to an earlier moment within the restore window of our plan.
7. Deleting data
Anyone can delete their darji account at any time, in the app (the Me tab, at the bottom) or by e-mail. It happens at once; what stays, and for how long, is on Delete your account.
For a company, what happens at the end of its order is in the Data Processing Agreement.
8. The services we use
darji uses these services (sub-processors). Each one receives only what its job needs:
- Vercel hosts the site, runs its server code in London (United Kingdom) and stores its audio files.
- Neon hosts the database, in London (United Kingdom).
- Resend sends darji's e-mails, invitations included.
- PostHog measures how darji is used (analytics), hosted in the European Union.
- Sentry receives error reports, so that we can fix what breaks.
- Paddle sells darji Pro and the seats as merchant of record: it takes payments, issues invoices and handles VAT. Card details go to Paddle, never to darji.
If someone chooses “Continue with Google”, Google signs them in.
Before adding or replacing a service that processes a company's data, we tell that company, as the Data Processing Agreement says.
9. Reporting a problem
Found a security problem? Write to hello@darji.ma. We answer, and fix what we can as fast as we can.
Companies can send us their security questionnaire at the same address.
10. Changes
We update this page when what it describes changes; the date is at the top.