BeautyCRM Pro privacy policy
Developer and software provider: Developertech
Application: BeautyCRM Pro
Android identifier: com.developertech.beautycrmpro
Distribution platform: Google Play
Paid plan purchases and payments: Google Play Billing
Support: jordiphonedeveloper@gmail.com
Privacy: jordiphonedeveloper@gmail.com
Effective date and last update: 6 October 2026
1. Scope and operating model
BeautyCRM Pro is a management application for professionals and businesses in aesthetics, beauty, hairdressing, massage and wellness. It helps organise clients, services, appointments and income and, depending on the plan, vouchers, workers, invoices and treatments.
Each professional user or business manages its own database and the information about its clients and workers. Developertech provides the software, its features, access plans and support; it does not provide its own hosting or centralised administration service for businesses' databases.
Working data is stored locally on the device. The application uses the authorised Google account for sign-in and Google Drive backup and restore features. Paid plans are purchased exclusively through Google Play Billing. The business's database is not sent to Google Play Billing to purchase or validate a subscription.
Purchasing a plan does not give Developertech general access to the business's calendar, records or documents, or authorise advertising uses of their contents. This policy is supplemented by the Terms of use and subscription and the Account and data deletion information.
2. Who is responsible for each processing activity
The professional user or business using the application
The self-employed professional or organisation using BeautyCRM Pro is the controller of the data about clients, workers and other people entered into its database. If a worker uses the application on behalf of a business, that use does not, by itself, make the worker an independent controller: they act in accordance with the business's instructions and permissions.
The professional or organisation decides which information is recorded, what it is used for, who may access it, how long it is retained and when it is changed, exported or deleted. It is also responsible for informing data subjects, having a valid legal basis, managing the necessary authorisations and responding to their rights.
Developertech as the application provider
Developertech does not determine the commercial or care-related purposes for which each business uses its records or administer its client records. Providing the software and managing plans does not turn that database into a Developertech database.
Developertech is responsible for the processing it actually performs for its own purposes when handling support or privacy enquiries, managing its relationship with users and subscription issues, and meeting its legal obligations. That processing is limited to the necessary information received through those channels or Google Play's purchase management tools, rather than the full contents of the CRM.
Support does not require sending complete databases. If an exceptional support intervention required processing personal data on behalf of the business, its scope would be defined in advance and any required safeguards and data processing agreement would be put in place. A support enquiry does not grant permanent access to the business's information.
Google and services chosen by the user
Google is involved in identification, authorised storage in Google Drive, and payment and subscription management in Google Play. Each service is governed by its own terms and privacy policy. Using Google Play Billing does not make Google responsible for the decisions the business makes about its clients, or remove Developertech's obligations concerning processing it performs for its own purposes.
3. What data the application uses
Account and business settings
The application uses the necessary details from the selected Google account, such as name, email address and identifier, together with the business information completed by the user: contact details, address, tax information, settings and preferences. Business data forms part of its workspace; it is not sent to Developertech simply by being saved.
Authentication is handled through Google. Developertech does not request Google passwords, verification codes or banking credentials.
Client and worker database
Depending on the features and fields used, the database may contain names, telephone numbers, email addresses, addresses, VIP status, appointments, services, vouchers, sessions, expiry dates, treatments, notes, assigned workers, amounts, recorded payment methods and generated documents. The business decides what information to enter and is responsible for its necessity and lawfulness.
Recording a client's payment as “cash” or “card” is a management entry. It does not mean Developertech processes that payment or that the full card number needs to be stored. Passwords and financial credentials must not be entered in free-text fields.
Subscriptions and access to features
Google Play Billing communicates technical purchase information to the application: product, plan, status, references or tokens, and the data needed to recognise, verify or restore purchased access. Developertech may consult the order information, issues and reports that Google Play makes available to the developer.
Payment details are entered and processed in Google Play. Developertech does not receive the full card number or its security code from Google Play Billing. Subscription data is separate from the client records managed by each business.
Support and privacy requests
When you write to Developertech, your email address, message contents and any files you voluntarily attach are received. If you report a purchase issue, identifying the Google Play order may be necessary. Provide only essential information; avoid sending databases, clients' health data, passwords or purchase tokens.
4. What data is used for and on what basis
The business uses the data in its database to organise its activities. It must determine the legal basis for each purpose, such as managing appointments, providing services, meeting invoicing obligations or sending communications. Purchasing the application does not replace clients' consent where that consent is necessary.
For Developertech's own processing, the data needed to handle a request or provide the service is processed to perform the contractual relationship or take requested pre-contractual steps. Compliance with legal obligations is based on those obligations. Handling complaints and preventing fraudulent use of subscriptions may be based on the legitimate interest in protecting the service and the parties' rights, subject to necessity, proportionality and respect for data subjects.
Processing that requires specific consent is not authorised by general acceptance of these terms or this policy. Consent may be withdrawn without affecting prior lawful processing or features that do not depend on it.
Developertech does not use businesses' records to sell databases, run advertising campaigns or profile their clients. Checking the plan serves to enable purchased features, rather than assess the people listed in the calendar.
5. Health information and data about minors
Allergies, contraindications and certain treatment notes may reveal health data. The existence of a text field does not authorise its collection. Before recording such information, the business must verify its necessity, the applicable legal basis and the additional condition required for special categories of data, and adopt measures appropriate to the risk.
Where explicit consent is necessary, it must be validly and separately obtained from the person concerned. Acceptance of the application by the professional does not replace it. BeautyCRM Pro's management features do not provide diagnoses or replace professional healthcare judgement.
The application is intended for professional management. If a business records information about clients who are minors, it is responsible for applying any necessary safeguards and authorisations and limiting data to what is needed.
6. Storage, backups and restoration
The working database is kept on the user's device. Backup and restore features use BeautyCRM Pro's application data space in the authorised Google Drive account, with the drive.appdata permission. This access is limited to the application's data space, rather than all personal documents in Drive.
When the user uses backup, export or restoration, the data included in that operation is transferred to the selected destination. Drive authorisation and access processes may also be involved during sign-in to locate and retrieve an existing backup for that account. Users should check the account and the options displayed for each operation.
Developertech does not receive a copy of that database on its own server. The subscription does not include centralised custody by Developertech, a guaranteed backup schedule or indefinite retention. Users must check the available backups and maintain those they need in accordance with their obligations.
A Drive backup is not equivalent to real-time collaborative synchronisation. Restoration may replace local data in accordance with the confirmation displayed in the application. Exports saved or shared outside the application remain under the management of the user and the selected recipient.
Revoking Google permissions and deleting stored data are different operations. A backup must not be assumed to have been deleted merely by signing out, revoking access or uninstalling the application.
7. Permissions and external integrations
Sign-in and Drive features use the Google permissions displayed when authorising the account. Reminders depend on Android notification permissions and restrictions. If a device contact is imported, the selected information is incorporated into the record managed by the business through the access mechanism displayed by Android.
When opening a call, WhatsApp or a sharing feature, users select the recipient and external service. They are responsible for checking the content before sending it. These actions do not, by themselves, transfer the entire database to Developertech.
The providers used for these features are Google — identification, Drive, Play Billing and support email through Gmail — and the services expressly chosen by the user to communicate or share files. Google describes its processing in its privacy policy.
The use of information obtained from Google APIs is limited to the disclosed and authorised features and complies with Google's User Data Policy, including applicable Limited Use requirements. Permissions do not authorise Developertech to use databases for purposes unrelated to the service.
Developertech's disclosures of data to authorities or advisers are limited to what is legally necessary and to information actually under its control, with the relevant confidentiality safeguards.
8. Website and technical browsing information
These informational pages do not include forms that receive databases or payments, first-party tracking cookies, embedded analytics or advertising resources. Email links open the visitor's email application: they do not send messages automatically.
The platform serving the website may process technical connection data, such as IP address, date and requested resource, to deliver the page and protect its infrastructure. For a website published under github.io, GitHub's privacy information applies; for one published under pages.dev, Cloudflare's applies. These references distinguish possible hosting providers for the pages and do not mean that businesses' databases are hosted there. To find out the hosting provider for a custom address, you may contact Developertech.
Website and assistant information updated on 27 October 2026. The frequently asked questions assistant offers predefined informational answers processed in the browser. It does not use an artificial intelligence service, transmit or store entered messages, or access accounts, databases or payments. To contact support, the email link opens your email application; you decide whether to send the message.
9. International processing
Google services and website hosting may use international infrastructure. Processing is not guaranteed to take place exclusively in Spain or the European Economic Area.
Transfers subject to the GDPR must rely on legally applicable mechanisms, such as adequacy decisions or contractual safeguards, together with any appropriate measures. Google publishes its mechanisms in its information about data transfers. The business must assess the suitability of the account and storage service conditions it uses for its own processing.
10. Retention
Local records remain for as long as users retain them or until they use deletion features. The business determines retention according to the purpose and its applicable obligations. Drive backups and exports remain at their respective destinations until deleted using the available mechanisms or in accordance with that service's terms.
Messages received by Developertech are retained to handle the enquiry or issue. Once it is closed, only information needed to meet legal obligations or establish, exercise or defend legal claims is retained for the applicable periods, with restricted access. Messages and attachments that are no longer needed are not retained indefinitely.
Purchase information that Developertech receives from Google Play is retained according to contractual necessity and applicable legal obligations. Google may keep its own payment records. An obligation to retain a receipt does not justify retaining the business's entire database.
If a deletion request cannot cover certain data because of a legitimate retention reason, the categories retained, the reason and the period or retention criteria will be explained.
11. Account deletion and control
Users can initiate deletion through Settings → Delete account and data or the Account and data deletion page, without needing to reinstall the application to send a request.
The scope distinguishes between local device storage, BeautyCRM Pro backups in Drive, support or purchase information actually retained by Developertech, and files saved outside the application. Support handles requests concerning data under its control and provides the instructions and assistance needed for data managed by the user or providers.
Developertech does not have general remote access to devices or the user's personal Drive account. An email does not automatically delete those contents; any necessary authorisation steps or user actions will be explained. Total deletion will not be confirmed if only part of it has been completed.
Deleting BeautyCRM Pro data does not delete the Google account or automatically cancel or refund a Google Play subscription. Renewal is managed separately in Google Play.
12. Rights and requests
To exercise rights concerning a client or worker record, contact the business or professional maintaining it as controller. Developertech cannot directly locate or modify a record that exists only on the business's device or in its Drive account.
For data processed under Developertech's responsibility, you may request access, rectification, erasure, objection, restriction or portability, where applicable, and withdraw consent by writing to jordiphonedeveloper@gmail.com. A paid plan is not required to send a privacy request.
Where there are reasonable doubts about identity, only proportionate information needed to verify it will be requested. Requests will be answered without undue delay and, as a general rule, within one month. Any lawful extension due to complexity or the number of requests will be communicated within that first month, together with the reasons.
You may lodge a complaint with the Spanish Data Protection Agency or the competent supervisory authority for your habitual residence, workplace or the place of the alleged infringement.
13. Security
The separation between the business's local data, the authorised Drive space and the purchase system limits access to their respective features. Google permissions are granted through its authorisation process; support does not require sharing passwords. Developertech limits the use of messages and attachments received to handling the request and meeting applicable obligations.
Users must protect their device with a screen lock, keep their accounts and applications up to date, restrict third-party access and review export destinations. Documents sent to other applications may fall outside BeautyCRM Pro's protection environment.
No guarantee of absolute security or end-to-end encryption is offered. Local storage or the existence of a private space in Drive does not, by itself, constitute certification of additional encryption of all information.
14. Changes and contact
This policy may be updated when the service or applicable obligations change. Material changes will be communicated by an appropriate means. No change retroactively authorises new incompatible purposes or replaces consent that must be obtained specifically.
Developertech — BeautyCRM Pro
Support and privacy: jordiphonedeveloper@gmail.com.
See also the Terms of use and the Account deletion page.