Privacy Policy
Last updated: 26 October 2026
This Privacy Policy explains what personal data MOLTRIC LTD (company number 517359857, Beit Hillel 6, Tel Aviv, Israel - "Moltric", "we", "us") collects, why, how long we keep it, who we share it with, and the rights available to you. It covers the website moltric.ai and the Moltric platform: the console at app.moltric.ai, and the calls, WhatsApp messages and SMS messages sent and received through it.
1. Two roles
- For our website and for our own customers' accounts, Moltric decides how data is used (we are the "controller").
- For the people our business customers contact through the platform, Moltric processes data on behalf of that business and on its instructions (we are the "processor"). The business that contacted you is responsible for having a lawful basis to do so and is your first point of contact. We help it answer your request, and you can also write to us directly (section 11).
2. Data from our website
When you submit the demo request form we collect what you provide: first and last name, position, company email address, phone number (optional), preferred date and time for a call (optional), your message (optional), and the interface language and time of your submission. We use it only to answer your enquiry and arrange a demo.
3. Data of our business customers' users
To run a customer's account we keep the names, work email addresses and roles of the people the customer invites to the console, and a log of important actions in the account, for security.
4. Data processed for our business customers
Depending on what the business uses, the platform processes:
- Contact details of the people the business contacts: name, phone number and, where provided, email address.
- Calls: the time and outcome of each call and, where the business has enabled it and the law allows, the recording, the transcript and an automatic summary. A recorded call opens with a recording notice.
- WhatsApp and SMS messages: the text of messages sent and received, the time, and the delivery status. WhatsApp messages are sent from the business's own WhatsApp Business account through the WhatsApp Business Platform operated by Meta, and are also subject to WhatsApp's own terms and privacy policy. SMS messages are sent through the SMS provider the business has chosen.
- Stop requests: if you reply with a stop word (for example "STOP"), we record it and no further WhatsApp or SMS messages are sent to your number by that business - not by its staff, not automatically, not surveys and not meeting reminders - until you yourself reply with a start word (for example "START").
- Meetings and surveys: meetings booked with you, your answers to them, and your answers to surveys the business sends.
5. Why we process it
To provide the service the business uses (placing and answering calls, sending and receiving messages, booking meetings, running surveys, producing reports), to keep the service secure, and to meet legal obligations. We do not sell personal data. We never use it for our own advertising, and never for anyone's advertising except the business that holds it, and only if that business turns it on (section 6).
6. Customer lists for the business's own ads
A business that uses the platform may choose to connect its own advertising account (for example on Meta, Google, LinkedIn, X or Microsoft), so that it can show its own ads to people already in its customer list, or leave them out of its ads. This happens only if the business connects an account and turns it on. We do it on the business's instructions, as its processor.
- What is sent: names, email addresses and phone numbers only, and never of a record the business has deleted. Before anything leaves our servers, each detail is normalised and scrambled one way (SHA-256), so the network receives no readable name, email address or phone number. Call recordings, transcripts, messages and all other data are never sent.
- What the network does with it: it compares the scrambled details with the scrambled details of its own users, only to find the matches that make up the business's audience.
- Where it goes: only to the ad account the business itself connected. We never send one business's list to another, and never combine lists of different businesses.
- Kept current: the list is updated once a night. A person whose record is deleted is removed from the audience at the next update.
- Disconnecting: when the business disconnects, sending stops at once and we delete our copy of the access permission. Where the network allows it, we also withdraw the permission at the network. An audience already created stays in the business's own ad account until the business removes it there.
- What we receive from the network: an access permission and the list of the business's ad accounts. We keep the permission encrypted and use it only to create and update these lists - never to create, change or pay for ads - and we do not share it. Our use of information received from a network's API follows that network's developer policies, including the Google API Services User Data Policy and its Limited Use requirements.
If you do not want to be shown such ads, you can ask the business, or us (section 11), to delete your details, and you can also use the ad settings of the network itself.
7. Google Calendar
A business that books meetings through the platform may connect its own Google Calendar. This happens only if the business connects it, on its instructions, as its processor.
- What we ask Google for: one permission, to see, create, change and delete events in calendars the business owns. We do not ask to read its email, contacts, files or any other calendar data.
- What we use it for: to find the business's free times, and to book, move or cancel the meetings its AI agent arranges on a call, or that the business changes in the console. When a meeting is moved or deleted directly in the calendar, we read that change back so the person is told. We read back only the events we created.
- What we keep: the meetings we booked (time, place, the person's name and contact details) and an encrypted copy of the access permission.
- What we never do: sell this data, use it for advertising, use it to train AI models, or let a person read it except to keep the service secure, to comply with the law, or when the business asks us to.
- How we protect it: the access permission is stored encrypted (AES-256-GCM) with a key kept apart from all other keys and bound to the business and the connection; all data travels encrypted (TLS 1.3); from the calendar we read only the start and end time, free/busy marking and status of events - never the titles, descriptions or attendees of the business's own events; inside the platform only people the business's administrator allows can see meetings, and important actions are recorded in a log.
- AI and Google user data: free times found in the calendar are passed to the language-model and text-to-speech providers that power the AI agent only to run the call in progress - to offer a time and to say it. These providers are used under terms and settings that exclude training on this data. Google Workspace APIs are not used to develop, improve, or train generalized AI and/or ML models. The use of raw or derived user data received from Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.
- Disconnecting: when the business disconnects the calendar, we delete our copy of the permission and withdraw it at Google. Meetings already in the calendar stay there until the business removes them.
Moltric's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Google API Services User Data Policy
8. Automated processing
Calls and messages may be handled by an AI agent acting for the business and following its instructions. Transcripts and summaries are produced automatically. No decision with legal or similarly significant effect on you is made by automated means alone.
9. Who we share data with
Only with service providers we need to run the service, and only for that purpose: hosting and infrastructure; telephone carriers; messaging providers (Meta's WhatsApp Business Platform and the SMS provider chosen by the business); speech-to-text, text-to-speech and language-model providers that power the AI agent; and email delivery. Where a business connects its own ad account, its scrambled list goes to that account's advertising network (section 6). We share data with authorities only where the law requires it.
We undertake not to pass the customer's credit card details to any third party. Card details are entered only on the secure payment page of our licensed payment provider, which meets the PCI DSS card-security standard. Moltric does not see or store full card numbers.
10. Where data is stored, and for how long
Platform data is stored on servers in the United States. Website form data is stored by our website hosting provider.
- Demo requests: up to 24 months from your last contact with us.
- Platform data: for as long as the business keeps it in its account. When the business deletes it or closes its account, we delete it, except where the law requires us to keep it.
- Backup copies are overwritten on a rolling basis.
11. Your rights, and how to ask for deletion
You may ask for access to your data, correction, deletion, restriction of processing, a copy of your data, or object to processing. You may also complain to your local data protection authority (in Israel: the Privacy Protection Authority).
To ask for deletion, follow the steps on our Data deletion page, or email support@moltric.ai with the subject "Data deletion" and the phone number or email address the data is kept under. We confirm receipt and complete the request within 30 days. If the data is held for one of our business customers, we tell that business and delete it on its instructions, unless the law requires otherwise.
12. Cookies
Our website uses essential cookies (security and operation), functional cookies (for example your language choice) and anonymised analytics. We do not allow third-party advertising or profiling cookies. The console uses only the cookies it needs to keep you signed in.
13. Contact
MOLTRIC LTD, Beit Hillel 6, Tel Aviv, Israel - support@moltric.ai