Business and visitor data
For visitor booking data, the business generally acts as controller and Promtys as processor. Visitors should direct requests to the business operating the website.
Understand what you are connecting, what appears publicly and who handles the information. The Privacy Policy is the source for the full legal details.

For visitor booking data, the business generally acts as controller and Promtys as processor. Visitors should direct requests to the business operating the website.
Integrations may involve services, staff, availability, prices and appointment records. Payment processing uses third parties; Promtys states it does not store full card details.
The Privacy Policy describes encryption in transit, access controls and monitoring. Subprocessor information can be requested from the team.
| Review area | What to check |
|---|---|
| Public content | Which records and fields are intended for customers to see? |
| Account access | Who can connect, edit and revoke each provider account? |
| Sensitive information | Does the planned form collect data that needs additional safeguards? |
| AI-generated content | Has a responsible person reviewed the output for accuracy before publication? |
| Retention & transfers | Does the provider arrangement meet your specific requirements? Request details where needed. |
| Incident handling | Who will investigate a connection or data issue, and how will you contact them? |
Do not assume fixed data residency. Review the Privacy Policy and request details for your intended setup.
No. Specific certifications or contractual requirements should be verified directly with the team.
Read the Privacy Policy and Terms of Service. This page is an orientation to the questions a business should review, not a replacement for those documents.