Privacy Policy
UNPUBLISHED DRAFT · legal-review-2026-10-22 · For legal review. Does not replace the public policy. Open decisions: ../REVIEW-NOTES.md. Translations do not certify national compliance; no prevailing language has been designated.
P01. Identity and contacts
Proposed provider: [ФИРМА], company identification number [ЕИК], [СЕДАЛИЩЕ И АДРЕС], represented by [ПРЕДСТАВИТЕЛ], VAT number [ДДС НОМЕР, АКО Е ПРИЛОЖИМО]. General contact: [КОНТАКТЕН ИМЕЙЛ]. Data questions and rights: [КОНТАКТ ЗА ЛИЧНИ ДАННИ]. This contact does not imply an appointed DPO. The need for one and the actual identity must be confirmed before publication.
P02. Different roles
For its own contractual contacts, administration of SaaS relationships, accounting obligations and protection of the platform, the provider may be controller depending on the particular purpose. For business-entered orders, reservations, staff and loyalty, the business ordinarily determines the purpose and the provider follows instructions as processor under a DPA. The role for a shared customer profile, cross-business linking, identification and fraud prevention depends on the actual decisions; neither processing on instructions nor joint controllership is assumed automatically. Joint decisions require a separate assessment and arrangement under Article 26 GDPR.
P03. Data and sources
The scope includes names and contact details of representatives and users, business and billing details, identifiers and authentication data, roles and locations, orders, delivery addresses, reservations, customer profiles, loyalty, ratings and correspondence. The platform exchanges payment statuses and identifiers with relevant providers; storage of full card details was not established in the reviewed frontend. Data come from individuals, the business and services used. Technical metadata and logs must be described conclusively after a backend/infrastructure inventory. Do not enter health or other special-category data in free text without separately established grounds and safeguards.
P04. Controller purposes and grounds
For an individual who is party to the SaaS contract, necessary performance and pre-contractual steps may rely on Article 6(1)(b). For representatives/employees of a legal person, the company contract does not automatically supply that basis: contact management and security require assessment of legitimate interests under Article 6(1)(f), necessity and balancing. Accounting and legally required disclosures rely on the specific applicable obligation under Article 6(1)(c). Voluntary marketing and optional technologies require a separate valid basis and, where necessary, prior consent. Consent is not inferred from acceptance of the terms. The business determines its own grounds for processing under the DPA.
P05. Recipients and services
Authorised persons have access only for the relevant purpose; data may be disclosed to actual infrastructure, payment and other providers and lawfully competent authorities. The code contains Paddle for SaaS and Google Maps for a selected delivery map; this does not establish production activation, the exact data set or each organisation's role. Twilio is only a planned integration. Recipients, subprocessors and external services' own policies must be confirmed in a register before publication.
P06. Locations and transfers
Data storage locations and the locations from which support access occurs have not been confirmed. EU-only processing is not promised. Any transfer outside the EEA requires identification of the country, recipient, applicable Chapter V GDPR mechanism and necessary supplementary measures. Information about safeguards and an accessible copy may be requested at [КОНТАКТ ЗА ЛИЧНИ ДАННИ] once the actual mechanism has been determined.
P07. Retention and security
Data are limited to what is necessary for the purpose, relationship and applicable obligations/legal claims. The specific schedule for accounts, logs, orders, accounting records and backups has not yet been confirmed; no invented periods are stated. The business determines instructions for its data within the law. Measures and export/deletion require technical verification; this draft does not certify any accreditation, absolute security or guaranteed recovery period.
P08. Rights and complaints
Depending on the role and basis, individuals may request access, correction, erasure, restriction and portability, object and withdraw consent without affecting earlier lawfulness. Responses follow GDPR procedures and deadlines; identity verification must be proportionate. For processing on instructions, requests are directed to the business with the necessary assistance. For the provider's own purposes, write to [КОНТАКТ ЗА ЛИЧНИ ДАННИ]. A complaint may be lodged with the Bulgarian CPDP (https://cpdp.bg/) or another competent supervisory authority, and judicial remedies remain available; contacting the provider first is not a prerequisite.
P09. Required data and automation
Fields necessary for registration/provision of the service must be marked; without them the relevant function may be unavailable. Voluntary data should not become a condition for an unrelated service. No solely automated decision with significant effects under Article 22 was established; this is not confirmation that none exists in the backend. Profiling in loyalty and fraud prevention requires a separate assessment.
P10. Devices and changes
The cookie policy describes established technologies and the review's limits. Any new processing requires information and legal bases to be updated before activation. The version and public effective date are determined after open decisions have been confirmed, not by the date of this draft.