Controller
PAJA Software UG (haftungsbeschränkt)
Stauffenbergstraße 37, 28844 Weyhe, Deutschland
support@paja-software.de
Website, downloads, updates and operational logs
- Purpose
- Providing the website, maintaining technical operation and preventing abuse.
- Data
- Website requests process technically necessary connection data. The contact form logs technical request identifiers, processing outcomes and error reasons on failure. Name, email address, subject and message content are not intended as regular log fields. Server-side errors may additionally be recorded in the upstream proxy's access log; request headers are excluded from it.
- Legal basis
- Article 6(1)(f) GDPR: legitimate interest in providing and securing the website and preventing abuse.
- Recipients and providers
- PAJA Software UG (haftungsbeschränkt); IONOS
- Processing locations
- Germany
- International transfers and safeguards
- No data transfers outside Germany.
- Retention and erasure criteria
- Centrally collected operational logs are configured for seven days of retention followed by automatic cleanup. Local operational logs are additionally bounded by size-based rotation; this does not establish a fixed time-based erasure period.
Support
- Purpose
- Handling support requests and requests concerning your data protection rights. Contact us at support@paja-software.de.
- Data
- Name, email address, subject and content of your request, and technical request identifiers. Where connection forwarding is configured, the connection address is used to limit abuse. Please provide only information needed to handle your request and avoid health information in messages or screenshots.
- Legal basis
- Article 6(1)(f) GDPR for general enquiries: legitimate interest in answering them and assisting with app use. Article 6(1)(b) GDPR applies to contractual or pre-contractual enquiries. Statutory data protection requests are handled under Article 6(1)(c) in conjunction with Articles 12 to 22 GDPR.
- Recipients and providers
- PAJA Software UG (haftungsbeschränkt); IONOS
- Processing locations
- Germany
- International transfers and safeguards
- No data transfers outside Germany.
- Retention and erasure criteria
- We retain personal data only for as long as necessary for the stated purposes. The data are then erased unless statutory retention obligations prevent erasure.
App server functions
- Purpose
- Providing and securing preventive-care catalog retrieval. Technical access data serve this purpose and are not used for advertising. Retrieval does not activate personal cloud synchronization.
- Data
- Catalog retrieval processes technical access, session and connection data. Date of birth, sex, care-plan entries, appointments and reminder state are stored only locally on your device. These details may allow conclusions about your health; the app does not transfer them to us or to third parties. Reminders are displayed locally through the operating system; depending on device settings, their contents may be visible on the lock screen. If you explicitly export an appointment to the device calendar, its date, time, title and, where provided, doctor or practice are passed to that calendar. Depending on your calendar settings, its provider may synchronize the entry.
- Legal basis
- Article 6(1)(f) GDPR for technical catalog-retrieval data: legitimate interest in providing an up-to-date and reliably accessible preventive-care catalog.
- Recipients and providers
- PAJA Software UG (haftungsbeschränkt); IONOS
- Processing locations
- Germany
- International transfers and safeguards
- No data transfers outside Germany.
- Retention and erasure criteria
- Technical access data are retained only as long as needed for catalog access. Inactive guest accounts follow the 30-day rule described under “Pseudonymous guest identity”; logs and backups follow the periods stated in their sections. “Reset care plan” deletes your local profile, plan, appointments and reminder state, and cancels scheduled app notifications. Previously exported calendar entries are not deleted by this reset and must be removed in the calendar if desired.
Backups
- Purpose
- Restoring server-side data after data loss or technical incidents.
- Data
- Copies of the server-side database, including technical guest identifiers, authentication, session and activity data, and associated change data needed for recovery. Profile, care plan, appointments and reminder state are stored locally on the device and are not included in this server-side database backup.
- Legal basis
- Article 6(1)(f) GDPR: legitimate interest in service availability and recoverability after data loss or technical incidents.
- Recipients and providers
- PAJA Software UG (haftungsbeschränkt); IONOS
- Processing locations
- Germany; backup storage in Berlin.
- International transfers and safeguards
- No data transfers outside Germany.
- Retention and erasure criteria
- Daily database backups and ongoing change records support a configured recovery window of 14 days. Older base backups needed for that window may be retained longer. Backup objects have seven-day deletion protection. Noncurrent object versions are scheduled for automatic deletion 30 days after becoming noncurrent. Erasure of individual records from the active database therefore does not immediately remove them from existing backups.
API operational logs
- Purpose
- Maintaining technical API operation, investigating errors and preventing abuse.
- Data
- Technical operational and error data relating to server requests and their processing. Server-side errors may additionally be recorded in access logs; request headers are excluded from those logs. Database queries with longer execution times may appear in database operational logs.
- Legal basis
- Article 6(1)(f) GDPR: legitimate interest in a secure and functioning catalog service and preventing abuse.
- Recipients and providers
- PAJA Software UG (haftungsbeschränkt); IONOS
- Processing locations
- Germany
- International transfers and safeguards
- No data transfers outside Germany.
- Retention and erasure criteria
- Centrally collected operational logs are configured for seven days of retention followed by automatic cleanup. Local operational logs are additionally bounded by size-based rotation; this does not establish a fixed time-based erasure period.
Pseudonymous guest identity
- Purpose
- Pseudonymous guest access for catalog retrieval without email and password registration. A guest identity is provisioned when needed on the first catalog request, not during welcome or onboarding.
- Data
- Technical guest and user identifiers, access and session data, and timestamps for provisioning, validity and last activity. Access is pseudonymous and does not require registration with a name or email address. The technical identifier can associate repeated requests with the same guest identity; use is therefore not anonymous. Personal profile and care-plan data are not transferred during catalog retrieval.
- Legal basis
- Article 6(1)(f) GDPR: legitimate interest in managing and securing technical access to the catalog service.
- Recipients and providers
- PAJA Software UG (haftungsbeschränkt); IONOS
- Processing locations
- Germany
- International transfers and safeguards
- No data transfers outside Germany.
- Retention and erasure criteria
- Inactive guest accounts become eligible for deletion by the hourly cleanup after 30 days without activity. Authenticated catalog requests update the activity timestamp. This period does not apply to backups or operational logs; their periods are stated in their sections.
Your rights
Subject to the statutory conditions, you have rights of access, rectification, erasure, restriction, portability and objection. You may withdraw consent for the future and complain to a data protection supervisory authority. Contact the controller above for requests.