Privacy Policy
Effective date: November 2, 2026
This policy explains how Incredevo Sp. z o.o. (“we”, “us”) handles personal data in connection with TheFuneralPlatform: the website thefuneralplatform.com, the application at app.thefuneralplatform.com and demo requests. TheFuneralPlatform is software for funeral transport and care companies.
Questions about this policy or about your data: privacy@quantdivision.com.
1. Who we are
2. Scope and our role
This policy covers:
- the website thefuneralplatform.com, including the demo request form;
- the application at app.thefuneralplatform.com, used by funeral transport and care companies (our customers), their staff and drivers, and the funeral directors they invite to the portal.
We have two different roles:
- Controller. For the website, for demo requests, and for the data we need to run and secure user accounts and to bill our customers for the platform. This policy describes that processing in full.
- Processor. For the data our customers enter in the application about their work: cases, the deceased, next of kin and other contacts, staff and drivers, funeral directors and their staff, the invoices they issue, documents and photos. The customer (the funeral company) is the controller for this data and decides what is recorded and why. We process it only on the customer's instructions, under a data processing agreement.
Are your details in a case or in the records of one of our customers, for example as next of kin? Then that company is responsible for your data. Please contact them first. If you contact us, we pass your request on to them (see section 8).
3. Personal data we process
a) Visits to the website
- When you open a page, the web server receives your IP address, details of your browser and the page you asked for. It uses them to deliver the page.
- For the demo form, the server keeps your IP address in memory for a short time to limit the number of requests per address (5 per 15 minutes).
- The website sets no cookies and loads no analytics, advertising or other third-party tools.
b) Demo requests
- The name, work e-mail address, company and message you enter in the form, and the language of the page you used.
- We send this by e-mail to our team at support@quantdivision.com and send you a confirmation. The confirmation has a fixed text and does not repeat what you typed.
- To prevent misuse of the form, the server keeps your e-mail address in memory for up to one day, so that each address gets at most one confirmation per day.
- Any further e-mails between you and us about the demo.
c) User accounts in the application
This applies to the users of our customers' own organisations, such as office staff and drivers. Funeral directors' staff who use the portal have a separate login; see the last item.
- Name, e-mail address and password (stored only as a bcrypt hash). Your language and display choice are stored in your browser (see section 10).
- Sign-in and security data: last sign-in, failed sign-in attempts and account lock, active sessions with IP address and browser (user agent), trusted devices with IP address, browser and when they were first and last seen, and two-step verification settings (an encrypted secret and hashed backup codes).
- Links for confirming your e-mail address, resetting your password and changing your e-mail address. They are stored only as hashes, together with the e-mail address they were sent to.
- Which in-app notifications you have read.
- Records of e-mails the application sent you: address, type, language, the case or invoice it concerned and whether delivery succeeded.
- Access log entries when you export data, download a document or anonymise records: who, when, IP address, browser and what it concerned.
- Portal logins for funeral directors' staff: name, e-mail address, password (stored only as a bcrypt hash), the invitation link (stored only as a hash) and last sign-in.
d) Data our customers enter in the application (we are processor)
The customer decides what is recorded. Depending on how it uses the platform, this can include:
- The deceased: name and title, dates of birth and death, weight class, height, condition, special handling, whether a pacemaker is present, belongings and notes.
- Next of kin and contacts: the family contact (a name or phone number), pickup and drop-off addresses with coordinates (often a home address), and the name of the person who signs at handover.
- Case records: documents such as the death declaration (A-verklaring) and permits, the case log, care tasks, the day programme (ceremony, cremation, burial, reception) and mortuary stays.
- Driver app: photos and signatures recorded during a ride.
- Funeral directors (our customer's customers) and their contacts: names, roles, phone numbers, e-mail and billing addresses, and ride requests from the portal, which can include the name of the deceased.
- Staff and drivers: name, phone number, driving licence, hourly rate, photo, role, rosters, availability including sick days, hours worked and ride assignments.
- Address book entries, which can include private addresses.
- Invoices the customer issues: recipient name and address, payments, and references and line descriptions that can include the name of the deceased.
- Uploaded photos of staff and vehicles, logos and product images.
Some of this data is sensitive, such as sick days of staff, and much of it concerns people at a difficult time. We protect it with the measures in section 11.
e) Billing for the platform
- If your organisation pays for the platform through Stripe: the organisation name, the administrator's e-mail address, and the billing address, tax ID and payment method entered in Stripe Checkout. We store the Stripe customer and subscription IDs and an overview of each Stripe invoice. Stripe receives no case data.
- The usage we count for billing (assignments), which carries the case reference.
f) Connected services
- WhatsApp (Meta): if your organisation connects its own WhatsApp Business account, we store the account and phone number IDs, the display number, the verified business name, and the access token and PIN in encrypted form. For each message we store Meta's message ID and the delivery status. We do not store the content of WhatsApp messages: incoming messages are read only to see whether a driver accepted or declined a job.
- e-Boekhouden.nl: if your organisation connects its e-Boekhouden account, we store the API token in encrypted form and, for each synchronisation, the invoice concerned and any error.
4. Purposes and legal bases
Where we are controller, we process personal data for these purposes, on these legal bases under the General Data Protection Regulation (GDPR):
- Delivering the website and protecting it and the demo form against misuse: our legitimate interest in a working and secure website (Art. 6(1)(f)).
- Answering demo requests and following them up: steps taken at your request before entering into a contract (Art. 6(1)(b)) and our legitimate interest in answering business enquiries (Art. 6(1)(f)).
- User accounts, sign-in, two-step verification and service e-mails (confirming your e-mail address, password reset, e-mail change, welcome, portal invitation, change of account status, and a notice when two-step verification is switched off): performance of our contract with your organisation (Art. 6(1)(b)) where you are our contract party; otherwise our legitimate interest in providing the service your organisation has agreed with us (Art. 6(1)(f)).
- Security, fraud prevention and audit logs (sessions, trusted devices, sign-in attempts, access log): our legitimate interest in protecting accounts and the data in the platform (Art. 6(1)(f)).
- Running the platform and finding faults with technical logs: our legitimate interest (Art. 6(1)(f)).
- Billing our customers for the platform: performance of the contract (Art. 6(1)(b)). Keeping invoices and accounting records: legal obligation (Art. 6(1)(c)).
- Handling legal claims and lawful requests from authorities: legal obligation (Art. 6(1)(c)) or our legitimate interest (Art. 6(1)(f)).
Where we rely on legitimate interest, you can object (see section 8).
Where we are processor, the customer determines the purposes and the legal basis. We use that data only to provide the platform to that customer, including the e-mails the application sends on its behalf: ride assigned, job not yet accepted, ride delayed, ride withdrawn (driver recalled or replaced), invoice sent, payment reminder and ride request received. E-mails to drivers and staff carry the case reference, not the name of the deceased.
5. Service providers
We use the providers below. They process personal data to provide their service to us, except where we say that the data goes to the customer's own account or that the provider's own terms apply.
- Microsoft Azure hosts the website and the application (App Service), the database (Azure SQL Database), files (Blob Storage: case documents and staff photos in private containers; logos, product images and vehicle photos in a container that is readable by link) and keys (Key Vault). Region: Sweden Central, in the EU. Database backups are stored geo-redundantly.
- Microsoft Azure Communication Services sends the e-mails of the application and of the demo form. It processes the recipient's address and name and the content of the message. Data location: Europe. Open and click tracking is switched off.
- Microsoft Azure Monitor (Application Insights) receives technical logs, traces and metrics of the application. E-mail addresses are masked before logs are sent, and IP masking is switched on.
- Microsoft 365 (Exchange Online) hosts our support mailbox, which receives demo requests and the e-mails you send us.
- Cloudflare provides DNS for our domains. Traffic to the application passes through Cloudflare's network, which processes IP addresses and request details to deliver and protect that traffic.
- Stripe handles payments for platform subscriptions, where your organisation pays through Stripe (see section 3e). Stripe also processes payment data under its own terms and privacy policy.
- Meta (WhatsApp Cloud API), if a customer connects WhatsApp. Meta receives the driver's phone number, the values in the message templates (company name, case reference, time and route, or the delay in minutes) and the confirmation we send after the driver taps accept or decline. Never the name of the deceased. The customer uses its own WhatsApp Business account, so the customer's terms with Meta also apply. When an administrator opens the WhatsApp settings under Admin before WhatsApp is connected, the page loads Meta's JavaScript SDK, so Meta receives the administrator's IP address and browser details under its own terms.
- e-Boekhouden.nl, only if a customer connects its account. It receives the invoice recipient (name, address, postal code, city, country and invoice e-mail address), the invoice number and date, the case reference and the line descriptions, which can include the name of the deceased. We send this data on the customer's instruction to the customer's own e-Boekhouden account, under the customer's agreement with e-Boekhouden.
- Google Maps. When a driver opens navigation or the map for a stop, the address or coordinates of that stop are sent to Google, which also receives the driver's IP address and browser details. Google handles this under its own terms and privacy policy.
We do not sell personal data and do not use it for advertising.
6. Transfers outside the EEA
The website and the application are hosted in the EU (Microsoft Azure, Sweden Central), and e-mail through Azure Communication Services is processed in Europe. Cloudflare, Stripe, Meta and Google also operate outside the European Economic Area (EEA), so personal data handled by them may be processed there.
Where personal data is transferred outside the EEA, the transfer relies on an adequacy decision of the European Commission, such as the EU-U.S. Data Privacy Framework for providers certified under it, or on the Standard Contractual Clauses adopted by the European Commission. You can ask us for more information about these safeguards.
7. Retention
Website and demo requests
- IP address for the form limit: in memory only, cleared within about half an hour.
- E-mail address for the confirmation limit: in memory only, cleared within about a day.
- Demo requests and our e-mails with you: as long as we need them to handle your request and any follow-up, and longer only where the law requires it.
Application (where we are controller)
The periods below are the retention periods we apply. The scheduled clean-up that deletes data automatically once these periods have passed is still being set up. Until it runs, older records stay in the database, and we delete them when you ask (see our Delete your data page).
- Sessions last up to 7 days. Expired sessions: 24 hours after they expire.
- Links for e-mail confirmation, password reset, e-mail change and invitations: 24 hours after they expire or are used.
- Trusted devices: 180 days.
- Records of e-mails sent: 395 days. The content of an e-mail is kept only while it is waiting to be sent.
- Access log (exports, document downloads, anonymisation): 730 days.
- User accounts: as long as the account exists. When an administrator removes a user, the user's sessions, trusted devices, links and two-step verification secret are deleted at once. The name and e-mail address stay on the record so that the history in the customer's records stays correct. You can ask us to remove them too (see our Delete your data page).
- Technical logs: as long as needed to run the platform and find faults.
- Database backups: deleted data can remain in backups for up to 12 months, after which the backup expires.
- Invoices and accounting records for the platform: as long as the law requires. Dutch tax law generally requires seven years.
Data our customers enter (where we are processor)
The customer decides how long this data is kept, within what is agreed in the data processing agreement. Customers can anonymise archived cases and staff records in the application. Amounts and invoices are kept, because invoices have to be retained for tax purposes.
8. Your rights
Under the GDPR you have the right to:
- Access: get a copy of the personal data we hold about you.
- Rectification: have incorrect or incomplete data corrected.
- Erasure: have your data deleted, unless we have to keep it.
- Restriction: have the processing of your data limited in certain cases.
- Data portability: receive data you provided to us in a common, machine-readable format.
- Objection: object to processing based on our legitimate interest.
To use these rights, e-mail privacy@quantdivision.com. We may ask you to confirm your identity first. We aim to respond within one month, as required by the GDPR. For complex requests this can be extended by two months; if so, we tell you why.
If your request concerns data that one of our customers has entered, such as a case or a staff record, that customer is the controller. We pass your request on and help the customer respond. In the application, customers can export their organisation's data, or the data of a single case or staff member, and anonymise archived cases and staff records.
How to have data deleted is explained step by step on our Delete your data page.
9. Complaints
If you think we handle your data incorrectly, please contact us first so we can look into it. You also have the right to lodge a complaint with the data protection authority in the EU member state where you live or work, or where you believe the infringement took place. In the Netherlands this is the Autoriteit Persoonsgegevens.
10. Cookies and browser storage
Website
The website thefuneralplatform.com sets no cookies and stores nothing in your browser. It loads no analytics, advertising pixels or embedded content from other companies. That is why there is no cookie banner.
Application: cookies
The application uses only cookies that are needed for it to work. It uses no analytics or advertising cookies.
Two parts of the application load content from other companies, which may set their own cookies under their own policies. If a driver taps Show map, Google Maps is loaded. When an administrator opens the WhatsApp settings under Admin before WhatsApp is connected, Meta's JavaScript SDK is loaded (see section 5).
app-auth-token: keeps you signed in (7 days).app-portal-token: keeps you signed in to the portal for funeral directors (24 hours).app-csrf-token: protects forms against requests from other websites (24 hours).app-device-token: remembers a trusted device for two-step verification (1 year).NEXT_LOCALE: your language (1 year).sidebar_state: whether the side menu is open or closed (7 days).
All of these cookies except sidebar_state can only be read by the server (HttpOnly). In production, app-auth-token is sent only over HTTPS.
Application: browser storage
The application also stores a few values in your browser. They stay on your device.
- Local storage:
fop.sessionSlideCheckedAt(when your session was last extended),i18nLanguage(your language) andtheme(light or dark display). - Session storage, cleared when you close the tab:
fop:intake-draft:…(an unfinished intake, up to 12 hours),fop.handoverSignature.…(a copy of a handover signature that has not yet been sent, up to 12 hours) andapp-global-error-retried(prevents repeated reloads after an error).
Because these cookies and values are needed for the service you use, they do not require consent. If you block cookies in your browser, you cannot sign in to the application.
11. Security
We protect personal data with technical and organisational measures, including:
- Encrypted connections (HTTPS with HSTS) for the website and the application, and encrypted connections to the database.
- Passwords stored as bcrypt hashes, with a minimum length of 8 characters.
- Two-step verification with an authenticator app, backup codes and trusted devices. The secrets for it are encrypted (AES-256-GCM).
- Session tokens and the links in e-mails stored only as hashes.
- Limits on sign-in attempts and an account lock after repeated failed attempts.
- Protection against cross-site request forgery (CSRF), a strict Content Security Policy and a ban on showing the application inside other websites.
- Access by role, and separation of each customer's data by organisation.
- Tokens for connected services (WhatsApp, e-Boekhouden) stored in encrypted form (AES-256-GCM).
- Case documents and staff photos in private storage containers, and photos from the driver app available only to signed-in users.
- An access log for exports, document downloads and anonymisation, and a case log that is only ever added to; identifying details are removed from it only when a case or staff record is anonymised.
- E-mail addresses masked in technical logs.
No system is completely secure. You can help by using a strong, unique password, switching on two-step verification and telling us straight away at privacy@quantdivision.com if you suspect that someone has accessed your account.
12. Children
The website and the application are meant for businesses and their staff. We do not knowingly collect personal data from children under 16 through the website, and we do not create accounts for them.
13. Contact
Incredevo Sp. z o.o.
ul. Ksawerów 3, 02-656 Warszawa, Poland
E-mail: privacy@quantdivision.com
Website: thefuneralplatform.com
14. Changes to this policy
We may update this policy when our services or the law change. We publish the new version on this page with a new effective date. For significant changes we also inform our customers directly.
TheFuneralPlatform