Privacy policy
Draft updated September 4, 2026 · Not legally reviewed
Who is responsible
The supplied business name is beesolo and the country is Romania. The registered operator identity and address still need confirmation. Contact support@beesolo.app about this draft or privacy questions. This proposed notice must be checked against production configuration before it becomes the final privacy notice.
Account and business information
Running the owner account may involve a name, email address, account identifiers, authentication records, business details, and settings. Public page information can include the professional's name, service descriptions, prices, location, and chosen images. Public information is visible to visitors and may be indexed by search engines.
Booking and communication information
Booking workflows use the client's contact information, chosen service, appointment time, booking status, and records of confirmations or changes. Support correspondence contains what you choose to send. Avoid adding health information or other sensitive details to general booking notes or feedback; this draft does not authorize their collection.
How information is used
The proposed purposes are to operate accounts and booking workflows, deliver appointment messages, answer support requests, protect the service, and meet applicable obligations. Account administration may rely on performance of a contract; security and support may rely on legitimate interests where properly assessed; statutory records may rely on legal obligations. Any optional marketing that requires consent must have its own choice. These purposes and legal bases require validation before launch.
Professional and platform roles
The professional generally decides why client appointment information is used for their business. Where beesolo processes it only on the professional's instructions, the proposed role is processor under a data processing agreement. beesolo may separately act as controller for its own account administration, security, and support. The final role allocation and agreement must reflect actual processing.
Providers and disclosures
The architecture uses Cloudflare infrastructure and supports external delivery and subscription providers. Which providers receive personal data depends on the enabled configuration. Before launch, publish the actual recipient/subprocessor list, processing locations, and safeguards. Do not interpret this draft as a promise that all information stays in Romania or the EU. Necessary disclosures may also occur to comply with law or protect legitimate legal rights.
International transfers
If information is transferred outside the EEA, the final notice and agreements must identify the relevant transfer mechanism and safeguards, such as an applicable adequacy decision or standard contractual clauses. The production provider configuration must be assessed before stating which mechanism applies.
Retention and deletion
Keep information only as long as needed for its stated purpose, applicable legal obligations, or justified dispute and security needs. The final schedule must specify periods or meaningful criteria for account, appointment, notification, support, log, and backup data. No fixed deletion deadline is promised in this draft. Contact support to discuss access or deletion, and contact the professional for information they control.
Cookies and similar technologies
Authentication and security may require technical storage. The final cookie/storage inventory must identify what is actually used, its purpose, and lifetime. Any non-essential analytics or marketing storage must be assessed and, where required, remain off until consent. This draft is not a cookie audit or consent mechanism.
Your choices and rights
Depending on the processing and applicable conditions, you may request access, correction, erasure, restriction, or portability, and object to processing. Where consent is used, you can withdraw it without changing the lawfulness of earlier processing. Contact support@beesolo.app; we may need enough information to verify the request. For records controlled by a professional, direct the request to them, with beesolo assisting as appropriate.
Complaints and updates
You can raise a concern with a competent data protection authority. In Romania this is ANSPDCP. The links below explain complaints and EU data protection rights. A final notice will include an effective date and describe how material changes are communicated.
Items still requiring review
Confirm the registered controller identity, lawful bases, data categories, provider inventory, international safeguards, retention schedule, cookie behavior, rights-handling process, and processor agreement. Neither this draft nor the software layout substitutes for legal or operational review.
Review references: EDPB guidance on individual rights, controller and processor roles, and ANSPDCP complaints.