Security
How Xeler protects your data.
For IT and procurement teams that review Xeler. Everything below describes what is in place today.
In short
- The database and uploaded files are stored in the EU, in Frankfurt.
- Personal fields are encrypted one by one with AES-256-GCM.
- Every read is filtered to one customer, and roles decide access inside it.
- Sign-in by emailed code, with an optional authenticator app as second factor.
- Every change is written to an append-only audit log.
- A DPA, a public subprocessor list, data export and deletion are built in.
Hosting and data location
The database runs on Neon in AWS region eu-central-1 (Frankfurt, Germany). Uploaded files are stored in AWS S3 in the same region. The server functions run on Vercel, pinned to the Frankfurt region (fra1); static assets are served from Vercel's global edge network.
Error reports go to Sentry's EU region. Email addresses are masked, and request bodies, query strings, cookies and authorization headers are removed before a report is sent.
Some services process data outside the EEA, under Standard Contractual Clauses: email delivery (Resend, US) and payments (Stripe, EU and US). The subprocessor list names every service, what it processes and where.
Encryption
Personal fields, such as names, email addresses, phone numbers, addresses and notes, are encrypted one by one with AES-256-GCM before they are written to the database. Each value gets a fresh random IV and a 16-byte authentication tag, so a value that was tampered with fails to decrypt.
The keys are kept outside the database, in the hosting environment. The code reads a current and a previous key, so a key can be replaced while older values stay readable.
Where an email address is needed for a lookup, a salted SHA-256 hash is stored next to the encrypted value.
Uploaded files sit in a private S3 bucket with server-side encryption (AWS KMS). Uploads and downloads use signed links that expire after a few minutes.
All traffic uses HTTPS. The site sends HSTS with includeSubDomains and preload, and a Content Security Policy.
Access control and customer separation
Each customer's data is separated in the application: every database read carries an explicit filter for that customer. Automated tests fail the build when a query on a customer table has no such filter, or when a lookup by ID does not also check the owner.
Inside a business, roles decide access: owner, admin, member, marketer and viewer, plus custom roles. Members and marketers are denied sales and finance: leads, proposals, invoices, expenses and bank. Every API route that serves business data checks the role on the server; a hidden button is never the only check. Every API route is also rate limited.
The clients of a business see nothing until something is shared or sent to them, and each client sees only their own work.
Removing a team member ends their access to the business. Permissions cached on other servers expire within 60 seconds.
Sign-in and sessions
Xeler has no passwords. You sign in with a one-time code sent to your email address. Code attempts are limited per mailbox, and sign-in answers the same whether an account exists or not.
Two-factor authentication with an authenticator app (TOTP) can be turned on under Settings > Security, with single-use recovery codes. Once it is on, signing in needs the app code as well, and those attempts are limited too.
Sessions are stored on the server and identified by a random token in an httpOnly, Secure cookie. Every sign-in issues a new token, and a session expires after 7 days. Settings > Security lists your active sessions and trusted devices, and you can end a session there.
Audit log
Every create, update and delete is written to an audit log: who, what and when. The database blocks changes and deletes on that table, each entry gets an integrity hash, and every entry is also written to a separate append-only copy.
New entries store a hashed identity instead of the person's email address. Data exports are recorded as well.
Backups and retention
The database is backed up continuously by Neon with point-in-time recovery, in the same Frankfurt region. The restore procedure is documented and has been tested.
Data marked for deletion is deleted or anonymised by a daily job, 30 days after the request. Issued invoices and signed proposals are kept unchanged for 7 years from their date, as Dutch tax law requires.
GDPR
The Data Processing Agreement (Art. 28 GDPR) is accepted at signup together with the Terms. You are the controller of the personal data you put into Xeler; Xeler, operated by RAWWW, is your processor. The subprocessor list is public.
Export: every user can download their data from their profile as a JSON file, with encrypted fields decrypted. It covers the profile, contacts and contact persons, leads, proposals, invoices, purchase invoices, expenses, subscriptions and recurring contracts. Uploaded files are not part of the download.
Deletion: owners and admins request it from their profile; other users email support@rawww.online. Sign-in sessions and two-factor settings are removed at once. For an owner, the profile, contacts, leads, proposals, invoices, purchase invoices, expenses, subscriptions and recurring contracts are then deleted or anonymised after 30 days. A single contact can be deleted at any time.
Breaches: if a personal data breach affects your data, we inform you without undue delay and no later than 48 hours after we become aware of it, with what you need to notify the supervisory authority. Incidents are recorded in a breach register.
The full terms are in the documents below.
Reporting a vulnerability
Found a security issue? Email security@rawww.online, in English or Dutch, with the steps to reproduce it.
Please give us time to fix it before you publish anything, and do not access or change other people's data while testing. The contact details are also in our security.txt (RFC 9116).
Automated security checks
Every push to the main branch, every pull request and a weekly scheduled run go through the security pipeline:
- 406 security test files that read the code and fail the build on a missing sign-in check, rate limit, input validation, customer filter, encryption call or audit log entry
- A dependency audit that fails on moderate and higher advisories, plus a package signature check
- An OSV vulnerability scan
- Static analysis with Semgrep
- Two secret scans, one of them Gitleaks
- A TypeScript check and tests on the financial calculations
- Third-party actions are pinned to a commit hash, and packages install without running install scripts