privacy policy
Privacy Policy
Privacy Policy pursuant to the General Data Protection Regulation
Last updated: 2 July 2026
Provider: SchelloLabs – Marcus Schellstede
This Privacy Policy explains the nature, scope and purpose of the processing of personal data in connection with the SchelloLabs website and the apps offered by SchelloLabs.
SchelloLabs develops practical software solutions and technical apps for planning, documentation, organisation and calculation. The protection of personal data is an essential part of the technical and organisational design of our services.
This Privacy Policy applies in particular to the following services:
* SchelloLabs website
* HOAI-Rechner
* E|Rechner
* AbÄppelApp
* ÜbergabePro
* PrüfPro
* future apps and digital services provided by SchelloLabs, insofar as they refer to this Privacy Policy
⸻
1. Controller
The controller within the meaning of the General Data Protection Regulation is:
Marcus Schellstede
Pirschweg 22
26160 Bad Zwischenahn
Germany
Email: support@schellolabs.de
Phone: +49 4486 3684202
⸻
2. Scope of this Privacy Policy
This Privacy Policy applies to the use of the website and to the use of the SchelloLabs apps.
The SchelloLabs apps are generally designed in such a way that personal data is processed as locally as possible on the respective device. Where functions such as iCloud synchronisation, CloudKit Sharing, App Store purchases, subscriptions, PDF export, CSV export, camera access, photo library access or sharing functions are used, additional data processing may be carried out by the operating system, Apple services or third-party applications selected by the user.
SchelloLabs currently does not operate its own user accounts, its own cloud servers or its own server-side user database for app data. Where app data is synchronised or shared, this is carried out via Apple iCloud or Apple CloudKit.
⸻
3. Definitions
This Privacy Policy uses the terms of the General Data Protection Regulation.
Personal data means any information relating to an identified or identifiable natural person. This may include, for example, names, contact details, project data, image data, documents, device data or technical access data.
Processing means any operation performed on personal data, such as collection, storage, use, transmission, deletion or provision.
Device means, in particular, an iPhone, iPad, Mac or any other device on which an app or the website is used.
iCloud synchronisation means the synchronisation of data via Apple iCloud or Apple CloudKit between the user’s own devices.
CloudKit Sharing means the option provided by Apple to share selected app data with other iCloud users, for example within a stable community or a team.
Controller means the natural or legal person who determines the purposes and means of the processing of personal data.
Processor means a service provider that processes personal data on behalf of the controller.
⸻
4. Legal bases for processing
Where personal data is processed, this is done on the basis of the General Data Protection Regulation, in particular on the following legal bases:
* Article 6(1)(a) GDPR – consent, for example in the case of voluntary contact or certain optional functions.
* Article 6(1)(b) GDPR – performance of a contract or pre-contractual measures, for example in connection with the provision of apps, app functions, support or digital services.
* Article 6(1)(c) GDPR – legal obligation, insofar as statutory retention, documentation or disclosure obligations exist.
* Article 6(1)(f) GDPR – legitimate interests, for example in the secure, stable and technically functional operation of the website and apps.
In the case of access to information on the device or the storage of information on the device, the provisions of the German Telecommunications Digital Services Data Protection Act also apply, in particular Section 25 TDDDG.
⸻
Part A – Website
5. Hosting
The SchelloLabs website is hosted by the following provider:
STRATO AG
Otto-Ostrowski-Straße 7
10249 Berlin
Germany
When the website is accessed, the hosting provider processes technically required data in order to deliver the website, ensure system security and identify disruptions.
This may include in particular the following data:
* IP address of the accessing device
* date and time of access
* page or file accessed
* amount of data transferred
* browser type and browser version
* operating system
* referrer URL
* host name of the accessing computer
* technical status and error messages
The processing is carried out for the technical provision of the website, to ensure IT security and for error analysis. The legal basis is Article 6(1)(f) GDPR.
⸻
6. Server log files
When visiting the website, server log files are automatically processed. These data are technically necessary to provide the website securely and reliably.
SchelloLabs generally does not combine these data with other data sources. The data are not evaluated for marketing purposes.
Server log files may be stored temporarily for technical security reasons. Longer storage only takes place insofar as this is necessary to investigate attacks, malfunctions or misuse.
⸻
7. SSL/TLS encryption
The website uses SSL/TLS encryption. An encrypted connection can be recognised by the fact that the browser address line begins with “https://”.
Encryption protects data transmitted between the device and the website against unauthorised access by third parties.
⸻
8. Cookies and TDDDG
The SchelloLabs website is generally designed so that it can be used without non-essential tracking cookies.
Where technically necessary cookies or comparable technologies are used, they serve exclusively to provide the website function expressly requested. The legal basis for this is Article 6(1)(f) GDPR and Section 25(2) TDDDG.
If non-essential cookies, analytics functions, marketing services or comparable technologies are used in the future, this will only take place after prior consent where such consent is legally required.
The user can also restrict, delete or completely deactivate cookies via the browser settings. If technically necessary cookies are deactivated, the functionality of the website may be restricted.
⸻
9. Contact
When contacting SchelloLabs, for example by email or telephone, the data provided by the user are processed in order to respond to the enquiry.
This may include in particular:
* name
* email address
* telephone number
* content of the message
* technical or organisational information relating to the enquiry
* information about the relevant app or version
* voluntarily submitted attachments or screenshots
The processing is carried out for the purpose of handling the enquiry. The legal basis is Article 6(1)(b) GDPR where the enquiry relates to a contractual or pre-contractual service, and otherwise Article 6(1)(f) GDPR.
Contact enquiries are stored only for as long as this is necessary for processing or statutory retention obligations apply.
⸻
10. External links
The website and apps may contain links to external websites, for example to the Apple App Store, Apple legal information, support pages or other information services.
SchelloLabs is not responsible for the content or privacy practices of external providers. When external links are accessed, the privacy policies of the respective provider apply.
⸻
Part B – SchelloLabs Apps
11. General information on data processing in the apps
The SchelloLabs apps generally process data on the user’s respective device. Depending on the app and the way it is used, personal or personally identifiable data may be created, particularly if the user enters names, project data, contact details, photos, documents, notes or other content.
SchelloLabs generally has no access to locally stored app content. Where the user exports, shares, synchronises via iCloud or shares data with other persons via CloudKit Sharing, the user decides on the scope and recipients of such data.
The apps do not use SchelloLabs’ own user accounts. Where required, authentication or processing is carried out via Apple system functions, in particular Apple ID, App Store, StoreKit, iCloud and CloudKit.
⸻
12. HOAI-Rechner
HOAI-Rechner is used to calculate and document fee estimates under the German HOAI. The app may process in particular the following data:
* project names
* project data
* chargeable costs
* service phases
* fee zones
* fee rates
* conversion or renovation surcharges
* ancillary costs
* discounts
* templates
* calculation histories
* PDF outputs
* office or customer data, insofar as the user enters such data
Processing is generally carried out locally on the device. The user decides which information is stored in the app.
PDF documents are generated from the data entered by the user. The user may store, export, print or share these documents locally via system functions.
Where iCloud synchronisation is activated or technically used, app data may be synchronised between the user’s own devices via Apple CloudKit. Processing is then carried out using Apple’s iCloud infrastructure.
SchelloLabs does not operate its own cloud database containing project content for HOAI-Rechner.
⸻
13. E|Rechner
E|Rechner is used for electrical calculation, assessment and documentation. The app may process in particular the following data:
* calculation values
* project data
* saved calculations
* favourites
* technical table values
* notes
* PDF documents
* project names
* optional photos or documentation content, insofar as these functions are used
The calculations are generally carried out locally on the device. Technical tables and calculation values are used to provide professional support to the user and are not evaluated for advertising or tracking purposes.
Where the user saves calculations or projects, they are stored locally on the device or, if iCloud synchronisation is enabled, processed via Apple CloudKit.
PDF documents are generated from the data entered or stored by the user. The user decides whether and to whom these documents are disclosed.
⸻
14. AbÄppelApp
AbÄppelApp is used to organise stable communities, tasks, members, horses, calendars, absences, documents and shared processes.
Depending on its use, the app may process in particular the following data:
* name of a stable community
* names or designations of members
* roles and permissions, for example administrator or member
* invitations and invitation codes
* horse names
* horse data
* tasks and duties
* feeding, pasture, paddock, arena or other stable appointments
* calendar data
* absences
* swap or substitute requests
* notes
* photos
* documents
* reminders
* synchronisation data
* technical assignments within a stable community
AbÄppelApp may process both local data and data synchronised or shared via CloudKit.
Stable communities
The user may create a stable community and manage members, horses, tasks, appointments or organisational information within it. These data are used to provide the app’s functions.
Members
Member data may include names, roles, responsibilities, tasks, absences or other organisational information. These data are entered by the user or by authorised administrators within the respective stable community.
Horses
Horse data may include names, assignments to members, appointments, documents, photos or other information. Users are responsible for entering only such information whose processing is necessary or desired for the organisation of the stable community.
Tasks and calendar
Tasks, duties and calendar data are processed in order to display duty rosters, bookings, reminders, substitutes and organisational processes.
Absences
Absences may be stored in order to support task planning, substitutions and calendar functions. Absences may allow conclusions to be drawn about personal availability and should therefore only be entered and shared with appropriate care.
Photos and documents
Photos and documents may be used for documentation or organisation within the stable community. The user decides which photos or documents are added.
Before uploading, storing or sharing photos and documents, the user should check whether they contain personal data, licence plates, persons, health information, contract data or other sensitive content.
Administrators
Administrators of a stable community may, depending on the app function, manage, modify, delete or invite members to certain data of the stable community. Administrators should use their permissions responsibly and process only such data as are necessary for the organisation of the stable community.
Invitations
Invitations may be sent via invitation codes or system-based sharing functions. The recipient of an invitation thereby receives access to the data of the stable community that have been released.
CloudKit Sharing
Where CloudKit Sharing is used, selected data of the stable community are shared with other iCloud users via Apple CloudKit. The technical provision is carried out by Apple. SchelloLabs does not operate its own servers for this purpose.
Participants in a shared stable community may, depending on their role and the app functions, view, edit or add shared data.
Synchronisation
Where iCloud synchronisation or CloudKit Sharing is enabled, data are synchronised between devices and participants via Apple iCloud or Apple CloudKit. Assignment is carried out via Apple ID and Apple’s iCloud infrastructure.
⸻
15. ÜbergabePro
ÜbergabePro is used to create, manage and document handovers, objects, projects, photos, documents and PDF protocols.
The app may process in particular the following data:
* object data
* project data
* handover protocols
* names or designations of involved persons or companies
* rooms, systems, components or technical installations
* defects, notes or findings
* photos
* documents
* signatures, insofar as this function is used
* PDF documents
* appointments or organisational information
Processing is generally carried out locally on the device. Where CloudKit or iCloud synchronisation is used, data may be synchronised via Apple iCloud or Apple CloudKit.
PDF protocols are generated from the data entered by the user. The user decides whether they are stored locally, exported, sent by email, shared via AirDrop or stored in a files app.
SchelloLabs generally has no access to locally stored handover protocols or project data.
⸻
16. PrüfPro
PrüfPro is used to create, manage and document inspection protocols, inspection findings, projects, photos, documentation and PDF outputs.
The app may process in particular the following data:
* project data
* object data
* inspection protocols
* names or designations of inspectors
* names or designations of clients, customers or contact persons
* technical inspection data
* findings
* defects
* notes
* photos
* documents
* PDF outputs
* appointments or organisational information
Processing is generally carried out locally on the device. Where the user uses CloudKit or iCloud synchronisation, the data may be synchronised via Apple iCloud or Apple CloudKit.
Inspection reports and documentation may contain personal or confidential information. The user decides at their own responsibility which content is entered, exported or disclosed.
SchelloLabs does not operate its own servers for storing inspection protocols or project data for PrüfPro.
⸻
Part C – Apple Services, App Store, StoreKit, iCloud and CloudKit
17. Apple App Store
The SchelloLabs apps are provided via the Apple App Store. When downloading, purchasing, updating or managing apps, Apple processes personal data under its own responsibility.
This may include in particular:
* Apple ID
* device data
* App Store purchase history
* payment status
* country or region of the App Store
* technical download and update information
* subscription status
* information on restoring purchases
SchelloLabs does not receive complete payment data from Apple, such as credit card numbers or bank details.
⸻
18. StoreKit, one-time purchases and subscriptions
Where SchelloLabs apps offer paid functions, one-time purchases or subscriptions, the technical processing is carried out via Apple StoreKit and the Apple App Store.
The app may receive information as to whether a purchase, subscription or Pro entitlement is active. This information is used to unlock purchased or subscribed functions.
SchelloLabs generally processes only the entitlement status required for the app function, for example:
* purchase active
* subscription active
* subscription expired
* purchase restored
* Pro function unlocked
Payment processing is carried out by Apple. SchelloLabs does not receive complete payment information of the user.
⸻
19. Restoring purchases
The “Restore Purchases” function is used to re-check purchases or subscriptions already acquired via the App Store and unlock them again in the app.
For this purpose, the app communicates with Apple StoreKit. The app receives the transaction or entitlement status required for unlocking.
⸻
20. Apple payments
Payments in the App Store are processed by Apple. Apple is responsible for payment data, billing information, payment methods, App Store accounts and payment verification.
Apple’s privacy policies and terms apply in addition.
⸻
21. iCloud and CloudKit
Some SchelloLabs apps may use iCloud synchronisation or CloudKit Sharing.
In this context, app data may be stored, synchronised or shared with other users via Apple’s iCloud infrastructure.
Depending on the app and its use, this may include in particular the following data:
* projects
* calculations
* protocols
* stable communities
* members
* horses
* tasks
* calendar data
* photos
* documents
* templates
* settings
* synchronisation and change information
The technical processing is carried out via Apple CloudKit. Assignment is carried out via the user’s Apple ID or iCloud account.
SchelloLabs does not operate its own servers for this synchronisation. SchelloLabs generally has no direct access to the user’s private iCloud data.
The user may control iCloud functions via the settings of their device or Apple ID.
⸻
Part D – Documents, Exports and Sharing Functions
22. PDF documents
Several SchelloLabs apps can generate PDF documents. These PDFs are created from the data entered or stored by the user.
PDF documents may contain personal data, project data, contact details, photos, technical information, defects, notes or other confidential content.
The user decides whether a PDF is:
* stored locally
* printed
* sent by email
* shared via AirDrop
* stored in the Files app
* stored in a cloud storage service
* disclosed to third parties
Once a PDF is shared via system functions or third-party apps, the further processing is governed by the privacy policies of the respective recipient or service.
⸻
23. CSV export
Where an app offers CSV exports, structured data from the app are transferred into a CSV file.
CSV files may contain personal or confidential information. The user is responsible for disclosing CSV files only to authorised recipients and protecting them appropriately.
⸻
24. Sharing, AirDrop, Files and Mail
The apps may use system sharing functions of iOS, iPadOS or macOS. These include in particular:
* AirDrop
* Messages
* Files app
* printing
* saving to cloud storage
* sharing with other apps
SchelloLabs has no influence over which third-party apps or services the user selects for sharing. Once a recipient or service has been selected, further processing takes place outside the sphere of influence of SchelloLabs.
⸻
Part E – Photos, Camera and Photo Library
25. Camera
Some SchelloLabs apps may allow access to the camera, for example to document inspections, handovers, objects, horses, stable areas or other circumstances.
Camera access only takes place if the user grants permission via the operating system. The permission can be changed or withdrawn at any time in the device settings.
Depending on the app function, photos taken may be stored locally in the app, in the photo library, in a file or, where iCloud synchronisation is enabled, via Apple CloudKit.
⸻
26. Photo library
Some apps may allow access to the photo library so that the user can select existing images and add them to documentation, a project, a stable community, a protocol or an object.
Access only takes place after approval by the user via the operating system.
Before adding photos, the user should check whether they show personal data, persons, licence plates, confidential documents or other information requiring protection.
⸻
27. Photo documentation
Photos may be used within the apps for documentation purposes. Depending on the app, photos may become part of projects, protocols, inspection reports, handovers, stable information or PDF outputs.
Where such content is exported or shared, the user decides on the recipient and disclosure.
SchelloLabs does not evaluate photos for advertising purposes and does not use them for profiling.
⸻
Part F – Synchronisation and Collaboration
28. Local storage
The apps are generally designed for local processing on the device. Locally stored data remain on the device unless the user uses synchronisation, export or sharing functions.
The user is responsible for protecting their device against unauthorised access, for example by device lock, Face ID, Touch ID, passcode, current system versions and suitable backups.
⸻
29. iCloud synchronisation of own devices
Where iCloud synchronisation is enabled, app data may be synchronised between the user’s own devices via Apple iCloud or CloudKit.
This serves to make data available on multiple devices and to synchronise changes between devices.
The technical provision is carried out by Apple. SchelloLabs does not operate its own servers for this purpose.
⸻
30. CloudKit Sharing and collaboration
Some apps may use functions for collaboration or data sharing. In this case, selected records may be shared with other iCloud users via CloudKit Sharing.
This may be relevant in particular for:
* stable communities in AbÄppelApp
* jointly used projects
* joint protocols
* team functions
* future collaboration functions
The user or administrator decides which persons are invited and which data are shared. Invited persons may, depending on their role, permissions and app function, gain access to shared content.
Before sharing, the user should check whether the content contains personal, confidential or otherwise protected information.
⸻
31. No own servers for app content
SchelloLabs currently does not operate its own servers for the central storage of app content such as projects, calculations, protocols, photos, documents, stable communities or inspection reports.
Where app data are synchronised or shared, this is carried out via Apple iCloud or Apple CloudKit or via export and sharing functions selected by the user.
⸻
Part G – Device Permissions
32. App permissions
Depending on the app and its use, device permissions may be requested, in particular for:
* camera
* photo library
* files
* notifications
* iCloud
* network access
* calendar or sharing functions, insofar as technically used
Permission is granted via the operating system. The user can change or withdraw permissions at any time in the device settings.
If a permission is withdrawn, the respective app function may be restricted or unavailable.
⸻
33. Notifications and reminders
Some apps may offer local notifications or reminders, for example for tasks, appointments, inspections, absences or organisational processes.
Notifications are used only if the user permits them. The permission can be changed at any time in the system settings.
Where notifications are processed locally on the device, no transmission to SchelloLabs takes place.
⸻
Part H – Support, Error Analysis and Communication
34. Support enquiries
If the user contacts SchelloLabs for support, errors, questions or suggestions for improvement, the data provided are processed to handle the enquiry.
This may include:
* name
* email address
* app name
* app version
* device information
* operating system version
* error description
* screenshots
* voluntarily submitted files or protocols
SchelloLabs uses support data exclusively to process the enquiry, analyse errors and improve app quality.
When submitting support enquiries, the user should not transmit personal data of third parties, confidential project data or sensitive information unless this is necessary for handling the enquiry.
⸻
35. Error reports and diagnostics
Where Apple or the operating system provides error reports, crash reports or diagnostic data, this information may be used to improve the stability and quality of the apps.
Whether and to what extent such data are made available to developers depends on the user’s settings with Apple or in the operating system.
⸻
Part I – Data Categories and Purposes
36. Categories of data processed
Depending on use, the following categories of personal or personally identifiable data may be processed:
* contact data
* project data
* calculation data
* organisational data
* protocol data
* photo and documentation data
* calendar and appointment data
* role and permission data
* purchase and entitlement status from the App Store
* technical device and access data
* support communication
⸻
37. Purposes of processing
Processing is carried out in particular for the following purposes:
* provision of the website
* provision of the apps and app functions
* local storage of user entries
* synchronisation via iCloud
* collaboration via CloudKit Sharing
* creation of PDF and CSV documents
* export and sharing of documents
* management of purchases, subscriptions and Pro functions
* handling of support enquiries
* error analysis and technical improvement
* ensuring IT security and stability
⸻
38. No advertising, no tracking, no profiling
SchelloLabs generally does not create user profiles for advertising purposes based on app content.
App content such as projects, calculations, inspection protocols, stable communities, photos or documents is not evaluated for personalised advertising.
Automated decision-making, including profiling within the meaning of Article 22 GDPR, is not carried out by SchelloLabs.
⸻
Part J – Retention Period and Deletion
39. Retention period
Personal data are stored only for as long as is necessary for the respective purpose or statutory retention obligations apply.
Data stored locally in apps remain on the device until the user deletes them, removes the app data or uninstalls the app.
Data stored or synchronised in iCloud may be deleted via the app, iCloud settings or Apple ID management, insofar as Apple and the respective app function allow this.
Support enquiries are deleted once they are no longer required for processing and no statutory retention obligations prevent deletion.
⸻
40. Deletion by the user
The user can generally delete locally stored content in the apps themselves, insofar as the respective app function provides for this.
In addition, the user may influence app data by deleting the app, removing local data or changing iCloud settings.
In the case of shared data, for example via CloudKit Sharing, deletion or modification may affect other participants or depend on roles and permissions.
⸻
Part K – Recipients and Third-Party Providers
41. Recipients of personal data
Personal data are disclosed only insofar as this is necessary for the provision of the website, the apps, App Store functions, iCloud synchronisation, processing of support enquiries or due to legal obligations.
Recipients may include in particular:
* hosting provider of the website
* Apple in connection with App Store, StoreKit, iCloud and CloudKit
* recipients selected by the user when exporting, sharing, using AirDrop, Mail or Files
* legally authorised bodies, insofar as a legal obligation exists
⸻
42. Apple as third-party provider
When Apple services are used, Apple’s privacy policies apply in addition.
This applies in particular to:
* Apple ID
* App Store
* StoreKit
* in-app purchases
* subscriptions
* payment processing
* iCloud
* CloudKit
* CloudKit Sharing
* TestFlight, insofar as used
SchelloLabs does not have full influence over data processing by Apple.
⸻
43. Transfers to third countries
Where personal data are processed by Apple, hosting providers or other services, processing outside the European Union or the European Economic Area cannot be completely excluded.
In such cases, processing is carried out in accordance with the applicable legal requirements and safeguards.
Apple’s privacy information and contractual terms apply to data processing by Apple.
⸻
Part L – Data Security
44. Technical and organisational measures
SchelloLabs takes appropriate technical and organisational measures to protect personal data against loss, misuse, unauthorised access, alteration or disclosure.
These include in particular:
* data-minimising app design
* local processing where possible
* use of Apple’s system security functions
* SSL/TLS encryption of the website
* limitation of own server-side processing
* no own app user accounts unless expressly introduced
* no own central app database for user content
⸻
45. Responsibility of the user
The user also bears responsibility for protecting their data. This includes in particular:
* secure device lock
* up-to-date operating system
* careful selection of shared content
* checking PDF, CSV, photo and document exports
* responsible use of CloudKit Sharing
* protection of the Apple ID
* regular backups where required
⸻
Part M – Future Functions
46. Expansion of apps and new functions
SchelloLabs continuously develops its apps further. Additional functions may be added in the future, for example:
* team functions
* additional CloudKit Sharing functions
* additional export formats
* additional documentation functions
* optional AI support
* new apps
* new Pro or subscription functions
Where new functions process additional personal data, this Privacy Policy will be supplemented or updated accordingly.
The use of new optional functions generally takes place only if the user uses or activates them.
⸻
47. AI support
At present, the described apps do not carry out independent AI-based evaluation of app content by SchelloLabs.
If AI-assisted functions are introduced in the future, SchelloLabs will provide transparent information on which data are processed, for what purpose this is done, which providers are involved and which choices the user has.
⸻
Part N – Rights of Data Subjects
48. Access
Data subjects have the right to request information as to whether SchelloLabs processes personal data concerning them.
Where such processing takes place, there is a right of access to these data as well as to further information, in particular processing purposes, data categories, recipients, retention period and rights of the data subject.
⸻
49. Rectification
Data subjects have the right to request the rectification of inaccurate personal data.
Where data are stored locally in an app, the user can in many cases rectify them directly within the app.
⸻
50. Erasure
Data subjects have the right to request the erasure of personal data where the statutory requirements are met.
Erasure may in particular be requested where the data are no longer necessary for the purposes for which they were collected, consent has been withdrawn or the processing is unlawful.
Statutory retention obligations may prevent immediate erasure.
⸻
51. Restriction of processing
Data subjects have the right to request restriction of processing where the statutory requirements are met.
This may be the case in particular where the accuracy of the data is contested or processing is no longer required, but the data are needed for the establishment, exercise or defence of legal claims.
⸻
52. Data portability
Data subjects have the right to receive personal data that they have provided to SchelloLabs in a structured, commonly used and machine-readable format, where the statutory requirements are met.
Where apps offer export functions such as PDF or CSV, these may additionally be used for personal documentation and data transfer.
⸻
53. Withdrawal of consent
Where processing is based on consent, such consent may be withdrawn at any time with effect for the future.
The lawfulness of processing carried out before withdrawal remains unaffected.
Device permissions, for example camera, photo library, notifications or iCloud, can be changed or withdrawn in the system settings.
⸻
54. Objection
Data subjects have the right, on grounds relating to their particular situation, to object to the processing of personal data where the processing is based on Article 6(1)(e) or Article 6(1)(f) GDPR.
SchelloLabs will then no longer process the personal data unless there are compelling legitimate grounds for the processing or the processing serves the establishment, exercise or defence of legal claims.
⸻
55. Right to lodge a complaint with a supervisory authority
Data subjects have the right to lodge a complaint with a data protection supervisory authority.
The authority generally responsible for SchelloLabs is:
The State Commissioner for Data Protection of Lower Saxony
Prinzenstraße 5
30159 Hannover
Germany
Phone: +49 511 120-4500
Email: poststelle@lfd.niedersachsen.de
Data subjects may also contact another competent data protection supervisory authority.
⸻
Part O – Special Notes on Third-Party Content
56. Responsibility for entered content
Users decide for themselves which data they enter, store, synchronise, export or share in the apps.
If users enter personal data of third parties, for example names of customers, contact persons, members, inspectors, project participants or stable members, they are responsible for ensuring that there is a legal basis for doing so.
This applies in particular to:
* photos of persons
* contact details of third parties
* project data with personal reference
* inspection and handover protocols
* stable communities and member data
* calendar and absence data
* documents containing personal data
⸻
57. Confidential and sensitive content
The apps may be used for professional, organisational or private documentation. Confidential information may arise in this context.
Before storing, exporting or sharing, the user should check whether content is particularly sensitive, for example:
* personal data
* health data
* contract data
* customer data
* trade and business secrets
* security information
* photos showing persons or licence plates
* inspection reports or defect documentation
SchelloLabs recommends storing or sharing sensitive content only where this is necessary and appropriate protective measures have been taken.
⸻
Part P – Changes to this Privacy Policy
58. Updates
SchelloLabs may amend this Privacy Policy if legal requirements, technical functions, app offerings or data processing operations change.
The current version will be made available on the website.
In the event of material changes, additional information may be provided within the apps or by other appropriate means.
⸻
59. Data protection contact
For questions about data protection, this Privacy Policy or the exercise of data subject rights, SchelloLabs can be contacted at:
Marcus Schellstede
Pirschweg 22
26160 Bad Zwischenahn
Germany
Email: support@schellolabs.de
Phone: +49 4486 3684202
© 2026 Marcus Schellstede - SchelloLabs . Alle Rechte vorbehalten.
APPS MADE IN PETERSFEHN - GERMANY