Legal
Privacy Policy
SafeLead is software that a clinic uses to handle its own enquiries. The clinic decides what is collected and why, and is the data controller. Akis Software Inc. hosts the software and processes data on that clinic's instructions, as its processor.
This notice describes how data is handled. It is not a contract, forms no part of one, and creates no rights or obligations beyond those the applicable data-protection law already imposes.
01Who this is
SafeLead is operated by Akis Software Inc., a corporation formed under the laws of the State of New York, United States. Contact: privacy@safelead.app.
Because the clinic is the controller, it — not Akis Software Inc. — determines and answers for the lawful basis for collecting your data, any consent that basis requires, which features it switches on, what its own privacy notice tells you, and how long records are kept. This notice supplements the clinic's own notice and does not replace it.
Akis Software Inc. is the controller only for the accounts of clinic staff who sign in, for its own service logs, and for the usage data, anonymised data and clinic instruction record described in section 05.
02What is collected
Through the clinic's account: the contact details a person gives (name, phone number, email address, country), the messages exchanged between that person and the clinic including any files sent, notes and status recorded by clinic staff, and records of calls placed through the system. In the current beta, calls placed through the system are recorded, and the recordings and their transcripts are kept with the enquiry. For staff: name, work email, role, sign-in events and a log of actions taken on records.
03Data received from Meta platforms
A clinic administrator may connect the clinic's own Facebook Page, Instagram professional account or WhatsApp Business account, through Meta's own login and permission screens. Only the permissions below are requested, and the connection can be removed at any time.
| Permission | What is received | Why |
|---|---|---|
| pages_show_list | Names and IDs of the Pages the administrator manages. | To choose which Page to connect. |
| pages_manage_metadata | No personal data — permission to subscribe that Page to webhooks. | So new messages and leads reach the clinic. |
| pages_messaging | Messenger conversations with the Page: sender's Page-scoped ID, public name and picture, message content, attachments, timestamps. | To show the conversation and let staff reply. |
| pages_read_engagement | Page information Meta requires alongside lead access. | Meta's stated companion requirement for reading Page lead data. |
| leads_retrieval | Answers submitted in the clinic's own lead forms — typically name, phone, email and the clinic's own questions. | To create the enquiry so staff can respond. |
| ads_read | Read-only list of the clinic's ad accounts, campaigns and lead forms. | To choose which forms to receive and label where an enquiry came from. |
| instagram_basic | ID, username and picture of the Instagram professional account linked to the Page. | To confirm the right account is connected. |
| instagram_manage_messages | Instagram Direct conversations: sender's Instagram-scoped ID, username, message content, attachments, timestamps. | To show the conversation and let staff reply. |
| business_management | The WhatsApp Business Accounts in the clinic's business portfolio. | To select the right account. |
| whatsapp_business_management | That account's registered phone numbers and approved message templates. | So only approved templates can be sent. |
| whatsapp_business_messaging | WhatsApp messages to and from the clinic's number: sender's phone number and profile name, message content, media, timestamps. | To deliver the conversation both ways. |
Data received from these platforms is used only to deliver SafeLead to the clinic that connected them. It is not sold, not rented, not shared with data brokers, not used for advertising or to build advertising audiences, not used to train artificial-intelligence models, and not combined with any other clinic's data. Access tokens are stored encrypted.
04What it is used for
To deliver messages between a person and the clinic and keep the history staff need to answer them; to assign enquiries and show how long they have been waiting; to send the clinic's campaign messages, which by default go only to people recorded as having consented; to keep the service running and secure; and to meet legal obligations.
Some content is processed automatically to operate features such as transcription of recorded calls. Where that happens it runs by default on the servers that host the service, rather than being sent to an outside AI service, and it is not used to train any model. Automated output is information for a person to review, not a decision.
05Usage data and anonymised data
Usage data. Akis Software Inc. collects, as controller, information about how the software is used and performs: feature usage counts, error rates, volumes and timings. It contains no message content and does not identify any patient or enquirer. It is used to operate, secure and improve the software and is kept for no longer than that needs.
Anonymised data. On the clinic's instruction, Akis Software Inc. may derive anonymised data and aggregated statistics from a clinic's records, so that no person, patient or clinic can be identified from them, by the standard of the Turkish Personal Data Protection Board's guideline on anonymisation and Recital 26 of the GDPR. Akis Software Inc. owns and may use such data for any purpose, including to develop, test and improve its products. It does so only by a documented method tested against re-identification, never attempts to re-identify anyone, and does not create such data from content received from Meta platforms (section 03) unless Meta's terms permit it. Data that is merely pseudonymised is not anonymised and stays the clinic's data under section 02.
Clinic instruction record. Akis Software Inc. keeps a record of the settings, confirmations and choices a clinic's administrators make in the software, with the staff member's identity and the time. It holds no patient data. Akis Software Inc. keeps it as controller for establishing or defending legal claims for a limited period after a clinic leaves, then deletes it.
06Who it is shared with
The clinic and its authorised staff; the messaging, telephony, email, payment and hosting providers needed to deliver the service, each under contract and only to provide it; and anyone we are legally required to disclose to. Card details are entered on a payment provider's own page and are not stored by Akis Software Inc. Personal data is not sold, and is not disclosed for any third party's marketing.
Akis Software Inc. is established in the United States and the service is hosted in Frankfurt, Germany (EU). Data collected through it is stored in the European Union. Akis Software Inc. staff in the United States can access it to run and support the service, which is a transfer to the United States. Further transfers occur because messaging, telephony and payment providers operate internationally.
Where a clinic is established outside the United States, or deals with people who are, the clinic decides whether it may lawfully use a service hosted in Germany and supported from the United States, and is responsible for putting in place whatever transfer mechanism the law applying to it requires and for describing it in its own privacy notice. A data-processing agreement, including standard contractual clauses, can be put in place where a clinic requires one.
07How long it is kept
For as long as the clinic's account holds it. The beta applies no automatic deletion schedule: records are kept until the clinic instructs their deletion, a person's deletion request is actioned, or the clinic's access ends. The clinic decides how long its records should be kept, including where law requires a minimum period, as it can for treatment records under health legislation and for payment records under tax law. The conversation history is append-only: staff cannot edit it, and an administrator's redaction requires a written reason and is itself recorded.
08Deleting your data
You can ask for your data to be deleted at any time. No account is needed. Any of these works:
- Email privacy@safelead.app with the subject Data deletion request, giving the email address, phone number or username you used to contact the clinic, and the clinic's name. Those details are used only to locate the records and confirm the request is yours.
- Ask the clinic directly. It controls its records and instructs their deletion.
- Remove the connection from the platform. On Facebook: Settings & privacy → Settings → Apps and websites (or Business integrations) → select the clinic's integration → Remove. On Instagram: Settings → Website permissions → Apps and websites → Remove. For WhatsApp, the clinic's administrator disconnects the account in WhatsApp Manager → Business Settings → Apps. A clinic administrator can also disconnect any channel inside SafeLead, which deletes the stored access token.
Requests sent to Akis Software Inc. are passed to the clinic that holds the records and actioned on its instruction, with a reply within the period the law applying to that clinic allows. On deletion, contact details, conversation history, attachments, recordings and enquiry records are removed from live systems and from backups as those age out on their normal cycle. Where a legal retention obligation covers part of a record, that part is restricted from operational use and deleted when the period expires; the reply identifies which records those are.
09Your rights
What rights you have depends on where you live and on the law applying to the clinic you contacted. They commonly include asking whether data about you is held and requesting a copy, having it corrected, objecting to or restricting processing, requesting portability, and withdrawing consent.
These rights are exercised against the clinic, which is the controller and decides what happens to its records; a request sent to privacy@safelead.app is forwarded to it. You may also complain to the data-protection authority for your own country, where one exists.
10Security
The measures applied include encryption in transit, encryption at rest for access tokens and other secrets, separation of each clinic's records, role-based staff access with phone numbers shown to staff in masked form, and logging of access to records. These are the measures in place, not a guarantee; no system is perfectly secure. If a personal-data breach occurs, the clinic is notified without undue delay so that it, as controller, can notify affected people and the authority where the law requires.
The software is in beta and under active development. It should not be relied on as a system of record.
11Children, cookies, changes
SafeLead is not directed at children and data is not knowingly collected from one. Only the storage strictly necessary to keep clinic staff signed in is used; there is no advertising cookie and no third-party cross-site tracking. This notice may be updated as the software or the law changes, with the date above updated; a change does not waive any right you have under data-protection law.
12Contact
Akis Software Inc. d/b/a SafeLead · privacy@safelead.app
For anything about your own records, contact the clinic directly — it holds them, and a request sent to us is forwarded to it.