SanTask – Privacy whitepaper
Published on November 16, 2026
This document summarizes how SanTask protects personal data. It is intended for decision-makers in customer organizations (local associations, district organizations, commercial providers) who want to evaluate whether SanTask meets their data protection requirements before entering into a contract.
Note: This whitepaper is a summary, not a legally binding commitment. The binding documents are the Data Processing Agreement (DPA, German: AVV) with its annexes, the Terms and Conditions and the Special Terms for SanTask. All contract documents are available in German only; the German text is the binding version. We deliberately avoid claims such as “100% GDPR compliant.” Instead, we explain in concrete terms what we do.
1. Who Processes Your Data
Provider: Patrick Altenburger, sole trader operating under the name “Novoris”, An den Mühlwegen 41, 55129 Mainz, Germany (info@novoris.io).
For the data your organization records in SanTask about volunteers and other individuals, your organization is the data controller within the meaning of the GDPR, and we act as your data processor (Article 28 GDPR). We do not use this data for our own purposes.
For a small number of processing activities we are the controller ourselves — for example user accounts and sign-in, records of concluded contracts, billing, and consent-based usage analytics (see Section 4). These are described in our Privacy Policy.
2. Hosting Location
Customer data is stored and processed exclusively in Amazon Web Services data centers in the eu-central-1 region (Frankfurt am Main, Germany) — application, database, and backups. We also run the identity service used for sign-in (ZITADEL) ourselves on this infrastructure, so no other provider receives data when you sign in.
No routine transfer of customer data to third countries takes place. AWS belongs to a group of companies headquartered in the United States; access from the US therefore cannot be completely ruled out and is safeguarded by EU Standard Contractual Clauses in the AWS data processing agreement.
For church-affiliated customers, the DPA also serves as a contract under § 29 KDG or § 30 DSG-EKD; customer data is processed exclusively within the EU/EEA.
3. Subprocessors
This list corresponds to Annex 3 of the DPA:
| Subprocessor | Service | Location of processing | Third-country link and safeguard |
|---|---|---|---|
| Amazon Web Services EMEA SARL, Luxembourg | Hosting of servers, database, and backups | Frankfurt am Main (eu-central-1) | US parent company; EU Standard Contractual Clauses |
| IONOS SE, Montabaur | Delivery of system emails | Germany | none |
We announce any new or replaced subprocessor in writing at least 30 days in advance. You may object on legitimate data protection grounds and, if no agreement is reached, terminate for cause (DPA Section 6).
4. Processing Under Novoris’s Own Responsibility
The following providers are not subprocessors for your customer data, because they are used only for processing activities for which we are the controller ourselves:
- Stripe Payments Europe, Ltd. (Ireland) — payment processing for paid plans. You enter payment details directly with Stripe; they are not stored on our servers. Stripe acts partly on our behalf and partly as an independent controller; Stripe’s US entities are certified under the EU-U.S. Data Privacy Framework.
- PostHog Cloud EU — usage analytics, only with the consent of the individual user. Without consent, the analytics script is not loaded. Text, URLs, and IP addresses are masked before storage, so no content from the application — such as people’s names — reaches PostHog; session recording is disabled. Data is stored in Frankfurt am Main and deleted after 12 months.
5. Technical and Organizational Measures (Summary)
- Encryption: All connections use TLS 1.2 or higher with HSTS; storage volumes, the database, and backups are encrypted at rest.
- Access control: Role-based permissions (Administrator, Manager, Responder); sign-in via the self-hosted ZITADEL identity service; rate limiting against brute-force attacks; secure session cookies.
- Multi-factor authentication: Mandatory for all of the provider’s administrative infrastructure and service-provider accounts; optionally available to your organization’s administrators and all other users.
- Infrastructure access: Least privilege, without long-lived access keys.
- Tenant isolation: Every data query is restricted on the server side to the signed-in user’s organization; isolation is verified by automated tests. No production data in development or testing.
- Logging: Sign-ins, administrative actions, and changes to organizations, memberships, invitations, and personnel records are logged in tamper-resistant form — as metadata only (timestamp, user ID, type of action, affected record), without the content of the changed data. Logs are deleted after 90 days.
- Support access: We access your data only where necessary to handle your request or resolve a malfunction; such access is logged.
- Backups: Daily encrypted backups, stored separately from the production system and overwritten after 30 days. Maximum data loss of 24 hours, target recovery within one business day. Restore tests at least quarterly, with documented results.
- Monitoring: Availability and system health are monitored with automatic alerting.
- Secure development: Automated vulnerability scanning of software dependencies (Dependabot), development aligned with the OWASP Top 10, server-side input validation, security headers.
- Data minimization: No fields for health or medical fitness information. The “meals” field offers only content-based options, so no religious or health information (Article 9 GDPR) can be derived from it.
The complete list of technical and organizational measures is Annex 2 of the DPA.
6. Concluding the DPA
The DPA is concluded electronically (Article 28(9) GDPR) when a person authorized to represent your organization accepts it in SanTask and confirms that authority. We record the version, timestamp, acting person, and their role in the organization. All administrators of your organization can view and download the concluded agreement and the proof of acceptance in the application at any time.
New versions of the DPA only become part of the contract with your consent; until then, the most recently concluded version continues to apply. All versions remain permanently available at novoris.io/avv.
7. Self-Service for Data Subject Rights, Export, and Deletion
As the data controller, your organization needs tools to handle requests from your volunteers (access, rectification, erasure, data portability). SanTask provides:
- Rectification and deletion of individual records directly in the application.
- Data export: A complete export of all organizational data in JSON format, with personnel data additionally as CSV or XLSX — available on demand and free of charge. Data structures and formats are described in the export register (German).
- Switching providers: Switching to another provider or to your own infrastructure under the EU Data Act, without switching charges (Terms § 12).
- Deleting your organization: If you delete your organization yourself, it is first locked for 14 days and can be restored by an administrator during that time; afterwards the data is deleted from the production system.
- After the contract ends: You can still export your data for 30 days; after that we delete it automatically. Backups are overwritten no later than 30 days after that, and security logs are deleted after 90 days. On request, we confirm deletion in writing.
- Per-shift change log: See who changed what on a shift, and when.
- Requests from data subjects that reach us directly are forwarded to you without undue delay, and we assist you in handling them.
Auto-planning only produces staffing suggestions. Every assignment requires explicit confirmation by an authorized person in your organization — there are no automated individual decisions within the meaning of Article 22 GDPR.
8. Personal Data Breach Notification
If a personal data breach occurs, we notify you without undue delay, typically within 24 hours of becoming aware of it, at the email address designated by your organization — enabling you to meet your 72-hour notification obligation to your supervisory authority. Where known, the notification describes the nature of the breach, the categories of data affected, the approximate number of individuals affected, the likely consequences, and the measures taken.
9. Contact
For data protection inquiries, please contact us at info@novoris.io.
As of November 2026, based on DPA version 2.0. This whitepaper is updated whenever significant changes are made to subprocessors, technical and organizational measures, or the DPA. It does not replace an individual assessment by your organization’s Data Protection Officer or legal advisor.