Staging: test data only. Payments are in sandbox mode.

Privacy Policy

Last updated 18 October 2026

Elargi helps accounting and bookkeeping firms (“firms”) collect documents from their clients. This policy explains what we collect and why. Questions: hello@elargi.com.

Two kinds of data

  • Firm accounts: name, firm name, email, password (stored hashed), and billing status. Payments are processed by Polar, our merchant of record; we never see card numbers.
  • Client uploads: files, answers and notes that a firm's client submits through a request link, plus the client's name and email entered by the firm. For this data the firm is the controller and Elargi acts as its processor.

How we use it

  • To run the service: store uploads, show them to the firm that requested them, and send request and reminder emails the firm has set up.
  • To send account emails (verification, password reset, billing).
  • We do not sell data, use uploads for advertising, or train AI models on them.

Where it's stored

Account data is stored in a PostgreSQL database and uploaded files in encrypted object storage. Emails are delivered by Resend. Each provider processes data only to provide its service to us.

Access and security

Uploaded files are never public. Only the signed-in firm can download them, through short-lived signed links. Client request links are long random tokens; anyone with a link can upload to it and see file names, but cannot download files.

Retention and deletion

Firms can delete a request at any time, which permanently deletes its files. If a firm closes its account, we delete its data within 30 days, except where we must keep billing records by law. Clients who want their data removed should contact the firm that requested it, or email us.

Your rights

Depending on where you live you may have rights to access, correct or delete your data. Email us and we'll respond within 30 days.

Operator note: set VITE_LEGAL_NAME and VITE_LEGAL_COUNTRY to show who runs Elargi here, and have this page reviewed for your jurisdiction (e.g. GDPR if you serve UK/EU firms) before taking payments.