Last updated September 2026

Security

This page sets out how Apraiz protects the data you give us: where it is stored, who inside the company can reach it, how the site and the apps are built and shipped, and how to tell us about a problem you have found.

1. Where your data lives

Apraiz is built in Europe and runs in Europe. The site and the API run on Google Cloud Run in the europe-west1 region in Belgium, and the waitlist data is stored in a BigQuery dataset pinned to the EU multi region. Neither can silently move somewhere else: the region is fixed in the infrastructure definition, so changing it is a reviewed code change rather than a setting somebody can toggle.

Where a supplier we use processes data outside the EEA, the transfer is covered by the safeguards named in the Privacy Notice, which also lists every recipient of your data.

2. Data in transit

Every connection to Apraiz is encrypted with TLS. Plain HTTP requests are redirected to HTTPS at the load balancer, before they reach the application, and the certificate is issued and renewed automatically through Google Certificate Manager with DNS based validation. The mobile apps talk to the same HTTPS endpoints and reject a connection that cannot be verified.

3. Data at rest

Data stored on Google Cloud is encrypted at rest by the platform, with keys managed by Google, and that applies to the database, the logs and the build artifacts alike. We do not keep copies of production data on laptops, and we do not export it to spreadsheets for analysis.

4. Who can reach it

Access is granted per person and per role rather than shared. Production access is deliberately narrow: a single named account can deploy the site, and the application itself authenticates as its own service account with permission to write waitlist rows and nothing more. When somebody leaves a role, their access is revoked rather than left in place, and we keep no shared logins or shared passwords for production systems.

5. How we build and ship

Changes reach the live site through one path: a reviewed change on the main branch, a container image tagged with the exact commit it was built from, and an automated check that the deployed site is serving real content. Because every image maps back to a commit, a bad release can be rolled back to the previous known good build in seconds. Dependencies are pinned and updated deliberately, not pulled fresh at deploy time.

6. What we deliberately do not collect

The strongest control over data is not holding it. Apraiz asks for the minimum it needs, and in particular:

  • We never ask for your bank credentials, and no part of Apraiz will ever ask you to log in to your bank.
  • We do not store card numbers ourselves. Where payments exist, they are handled by a payment provider that is certified to take them.
  • We do not sell or rent personal data, and we do not pass your details to estate agents or brokers so they can approach you.
  • Support staff cannot see your password. Nobody at Apraiz will ever ask you for it, by email or otherwise.

7. Reporting a vulnerability

If you think you have found a security problem, please tell us before you tell anyone else, and send it to support@apraiz.eu with Security in the subject line. A useful report says what you found, the exact address or screen where you found it, and the steps to reproduce it.

What you can expect from us: an acknowledgement within two working days, an assessment and a plan within ten, and credit for the finding if you would like it. What we ask of you: give us a reasonable chance to fix it before you publish, do not access or alter data that is not yours, and do not run tests that degrade the service for other people. We will not pursue a researcher who reports in good faith and stays within those limits.

8. If something does go wrong

No system is perfect, so the honest commitment is about what happens next. If a breach affects your personal data, we notify the Estonian Data Protection Inspectorate within 72 hours of becoming aware of it, as Article 33 of the GDPR requires, and we tell you directly, without undue delay, when the breach is likely to put your rights at risk. We will say what happened, what data was involved and what you should do, rather than wait until we have a comfortable story.

9. Certifications

Apraiz does not hold ISO 27001 or a SOC 2 report today, and we would rather say so than imply otherwise. The controls above are what is actually in place. Formal certification is planned as the company grows, and this page will be updated when there is something real to point at.

10. Questions

Security questions, questionnaires from a prospective partner, and anything else on this page go to support@apraiz.eu. For what data we hold and why, read the Privacy Notice; for the rules of using Apraiz, read the Terms of Service.

This is a pre-launch draft for information only. It is not legal advice and will be reviewed by counsel before Apraiz opens.