Effective 9 October 2026

Privacy Policy

We built Delshe so companies keep control of their data. This policy describes, in plain language, what we collect, why, who helps us process it, and the choices you have. See also our Terms of Service.

1. Who we are

Delshe is operated by [Operator legal name], [Registered address] (“Delshe”, “we”, “us”). This policy explains how we handle personal data when you visit our website, create an account, or use the Delshe workspace.

Questions or requests about your data can be sent to legal@delshe.app.

2. Our role: controller and processor

Account data. For your account (name, email, password, profile picture) and for how you use the service, we decide how the data is used and act as the controller.

Workspace content. The records, files and data sources a company puts into Delshe belong to that company. For this content the company is the controller and we act as its processor, handling it only to provide the service on its instructions. If your details appear in a company’s CRM, please contact that company first; we will help them respond. A data processing agreement is available on request.

3. Data we collect

  • Account details: name, email address, a hashed password, email-verification status and an optional profile picture.
  • Workspace details: the companies and teams you belong to, your role, invitations you send or receive, and the CRMs shared with you.
  • Content you add: CRM records, notes, record history, imported files, company themes and logos.
  • Data source settings: spreadsheet links, database connection strings and queries. Database credentials are stored encrypted and used only to read the data you asked for.
  • Technical data: IP address, browser and device information, and request logs created when you use the service, used for security, rate limiting and troubleshooting.
  • Messages: anything you send us by email.

4. How we use data and our legal bases

  • To provide the service — creating your account, running workspaces, importing and syncing data, sharing CRMs and sending invitations and verification codes (performance of our contract with you).
  • To keep Delshe secure and reliable — authentication, access control, abuse prevention, rate limiting and debugging (our legitimate interest in a safe service).
  • AI-assisted features — when you ask Delshe to draft a CRM or answer a question about your records, the text you enter and the relevant field names are sent to the AI model to produce a result (performance of contract). We do not use your content to train AI models.
  • To meet legal obligations — for example responding to lawful requests and keeping required records.

5. Service providers

We do not sell personal data. We share it only with providers that help us run Delshe, under contracts that protect it:

  • Neon — database and authentication. Data is stored in the AWS Frankfurt (eu-central-1) region.
  • Cloudflare — hosting, network delivery, request logs, file storage for logos and profile pictures, and the AI models (Workers AI) behind drafting and questions.
  • Resend — delivery of invitation and account emails.
  • Bunny Fonts — when a company theme uses a web font, your browser loads it from fonts.bunny.net, which receives your IP address.
  • Sources you connect — when you link a Google Sheet or a database, Delshe connects to that service on your behalf to read the data. Their own privacy terms apply to them.

Within a workspace, content is visible to the people the company gives access to, including guests a CRM is shared with.

6. International transfers

Our primary database is in the European Union. Some providers, such as Cloudflare and Resend, may process data outside the EU, including in the United States. Where that happens we rely on appropriate safeguards such as the EU Standard Contractual Clauses or an adequacy decision.

7. How long we keep data

  • Account data is kept while your account exists and deleted within 30 days after you ask us to delete it.
  • Workspace content is kept until the company deletes it or closes its workspace, then removed from active systems.
  • Request logs are kept for a short period for security and troubleshooting, normally no longer than 30 days.
  • Backups are overwritten on a rolling basis and may hold deleted data for a limited time.

8. Security

Access to data is enforced by the database on every request with row-level security, so people only see the companies, teams and CRMs they belong to or were given. Traffic is encrypted in transit, database credentials for connected sources are encrypted at rest, and external databases are queried read-only. No system is perfectly secure; if a breach affects your data, we will notify you and the authorities as the law requires.

9. Cookies and local storage

Delshe uses only what it needs to work. We do not use advertising or third-party analytics cookies.

  • Session cookies keep you signed in and protect your account.
  • A workspace cookie remembers which company you last had open.
  • Local storage remembers your light or dark mode preference on your device.

10. Your rights

Depending on where you live, you can ask to access, correct, delete or export your personal data, object to or restrict certain uses, and withdraw consent where we rely on it. You can update your name, email and profile picture yourself in account settings. For anything else, email legal@delshe.app; we answer within one month.

You also have the right to complain to your local data protection authority. We would appreciate the chance to address your concern first.

11. Children

Delshe is a business tool and is not intended for anyone under 16. We do not knowingly collect children’s data.

12. Changes to this policy

We may update this policy as Delshe changes. The effective date at the top shows the latest version. If a change materially affects how we use your data, we will tell you by email or in the app before it takes effect.