Privacy notice

Effective 1 September 2026. The short version: anonymous files stay in memory for at most 30 minutes; account data exists only to run the reporting service.

Controller and contact

Dali AI GmbH, Wassergrabe 4, 6210 Sursee, Switzerland · kontakt@dali-ai.ch.

Data we process

• Anonymous validator: the uploaded transactional rows in temporary process memory, plus anonymous aggregate telemetry: the date, row and error counts, and an allowlisted intent label. This telemetry never contains a search query, browsing history, filename, identity or email address, IP address, or file contents. The label is associated with an account only if you voluntarily create one.
• Account: email, password hash, contracts you enter, saved mappings, item data, produced files and report totals.
• Monthly close: keyed one-way fingerprints of normalized SRP rows for exact-match comparison, report revisions, and the submission date and optional confirmation number you enter after using the GSA portal. We do not receive portal credentials or portal status.
• Subscription: consent time and terms version; when card payment is enabled, Stripe customer/subscription identifiers and payment status. Full card numbers stay with Stripe.
• Advertising attribution: if you arrive from one of our own ads, the click identifier and campaign name carried in the link are held in your own signed session cookie. They are written to the database only if you create an account, so we can tell which campaign produced a customer. The click identifier and campaign name themselves are not recorded for visitors who do not sign up. An allowlisted label such as “fas-srp” or “transactional-data-reporting” may likewise be stored with an account so we can measure which of our own guides led to signup; the search query and browsing history are not stored.
• Operations: short-lived security and server logs needed to detect abuse and diagnose failures. Rate-limit identifiers are one-way, process-local and never written to the application database.

Purpose and basis

We process data to provide the validator and account, keep the saved report record, authenticate users, collect an agreed subscription and protect the service. Account and subscription processing is necessary to perform the contract; abuse prevention and minimal operational measurement serve our legitimate interest in a reliable service.

Where data goes

The application and database run on Fly.io in Ashburn, Virginia, United States. When enabled, card payments run through Stripe. Transactional email uses the configured mail provider. We do not sell data, run third-party advertising or analytics scripts on this site, or use uploads to train models. Where an account began with an ad click we may report that signup back to the ad platform using the click identifier alone; no email address, file content or other personal data is sent with it.

Retention

• Anonymous upload bytes and generated downloads expire from memory after 30 minutes.
• Account mappings, item data and report records remain while the account is active or until you request deletion.
• If you never subscribe, produced workbook bytes and keyed row fingerprints are erased 30 days after each report is produced. During a subscription they remain available until 30 days after the subscription ends. The reporting month, production date, revision, line count and totals remain as the account record. A submission date and optional confirmation number remain only if you recorded them.
• Payment and consent records are retained as required for accounting and legal proof.
• Expired password-reset records may be removed at any time and cannot be reused.

Your choices and rights

Write to kontakt@dali-ai.ch to request access, correction, export or deletion. You may also object to or ask us to restrict processing where applicable. You may complain to the Swiss Federal Data Protection and Information Commissioner.

Upload boundary

Send transactional lines only. Do not upload contracts, price lists, agency correspondence, CUI, FOUO or classified material. See the terms and imprint for the contractual boundary.