EasySLU
Privacy

Privacy Policy

This policy explains what EasySLU collects, where user data is stored, and how we use it to operate the service.

Data location
Production app data is stored in SQLite and S3-backed document storage; private installations may use client-controlled infrastructure.
AI processing
AI workflows use only the context needed for the action you request or approve.
Access control
Workspace, company, team, and agent scopes control access to company data.

Questions or requests

Contact us to request access, correction, deletion, export, or restriction of your personal data.

Contact EasySLU

Last updated: 17 May 2026

How EasySLU Handles Data

What We Collect

Account and identity data

We process your name, email address, authentication state, workspace membership, roles, team invitations, two-factor authentication status, and support contact details so you can sign in and manage access.

Company and accounting data

We process company profile details, NRT/tax identifiers, invoice and customer data, bank-import rows, receipts, supplier bills, filings, reminders, CRM records, agent approvals, and activity logs you create or upload.

Uploaded documents

Documents you upload or forward to an EasySLU inbox are stored for vault, extraction, bookkeeping, filing-pack, support-bundle, and review workflows.

AI and automation data

When you use AI-assisted classification, matching, notice explanation, posting, or agent chat, relevant document and accounting context may be sent to the configured AI provider to produce the requested result.

Where Data Is Stored

Primary app database

Application data is stored in the EasySLU SQLite database. Production deployment is configured for /var/lib/easyslu/easyslu.db with WAL replication and snapshots to S3.

Document storage

Uploaded files are stored on the configured storage backend. Production configuration uses an AWS S3 document bucket in eu-central-1 unless a private installation uses a client-controlled backend.

Secrets and provider tokens

Service secrets are kept server-side in environment or secret-store configuration. Connected email OAuth tokens are encrypted before they are stored.

Operational logs

Operational logs and monitoring events are used to diagnose failures, maintain security, and prevent abuse. We minimize personal data in logs and redact secrets, tokens, cookies, and API keys.

How We Use Data

We use data to provide authentication, workspace access, bookkeeping, document management, invoicing, tax and compliance workflows, support, security monitoring, abuse prevention, product reliability, and customer-approved AI or agent actions.

Sharing

We share data only with service providers needed to operate EasySLU, such as hosting, storage, email delivery, monitoring, and AI providers, or when required by law. We do not sell user data.

Retention and Deletion

We keep account, company, document, accounting, and audit data while your account or workspace is active and as needed for legal, tax, security, backup, and dispute-resolution purposes. You can request deletion or export by contacting us.

Contact

EasySLU is operated by MVP Foundry SLU in Andorra. Privacy requests can be sent to [email protected].