Privacy policy
Last updated: 29 October 2026
How Azorly collects, stores and protects information about business owners and the people who call them, under Israel's Privacy Protection Law and Amendment 13.
Who we are
Azorly operates an AI-based phone answering service for businesses in Israel. This policy explains what information we collect, why, how it is stored and what rights you have under the Privacy Protection Law 5741-1981, including Amendment 13, in force since 14 August 2025.
It applies to business owners who use the service (customers) and to people who call those businesses and speak with the digital assistant (callers).
Information about callers
When someone calls a business that uses Azorly, the call is documented: the caller's phone number, a recording, a transcript, a system-generated summary and the details the caller chose to share (for example a name, preferred appointment time, description of the request).
By default the assistant opens the call with a short greeting and her name, without a recording notice. The business owner can switch on a recording notice in the greeting in the settings, and is responsible for informing callers of the recording and of the collection of their details wherever the law requires it. A caller who asks whether they are speaking with a person, or whether the call is recorded, is told honestly that they are speaking with a digital assistant and that the call is recorded. Callers can stop at any time, leave a message or ask for a person to call back.
Callers to healthcare businesses may share medical information. Such information is "information of special sensitivity" under the law and receives a high security level.
Food orders and payment by phone
For a business that takes orders on the phone (a pizzeria, a restaurant), we keep the order on the business's behalf: the dishes and choices, the name, the phone number, the delivery address, notes, the total and the payment method. A year after the order, the name, phone, address and notes are deleted, and only the dishes and totals remain for statistics.
If the business chose to take cards over the phone, the caller gives the card number, expiry, the three digits on the back and, when the business requires it, the cardholder's ID number, solely to charge the order. The details are encrypted on our server before they are stored, open only for the business's staff to charge at the terminal (each opening is logged), and are deleted the moment the business marks the charge as done or declined, and 24 hours after the order at the latest. Calls on a line that takes cards over the phone are recorded, and the recording holds what the caller gave, the card details included. So the recording and the transcript are kept by the voice provider for three days only and then deleted, the recording isn't played in the business's dashboard, and the payment details are hidden in the transcript and summary we keep. The kitchen ticket shows only the last four digits. The business itself charges the card, with its own payment processing.
Menu photos a business owner uploads are sent to Anthropic to read the dishes and prices, and we don't keep them after the reading.
Information about customers
Registration details (name, email, phone), business details entered in the characterization (services, hours, handling rules), dashboard usage data, and billing details: the plan, usage, payments and invoices. Payments themselves are processed by Polar; card details never reach our servers.
Cookies and site analytics
We measure use of the website and the dashboard ourselves: which pages were viewed, where you came from (a referring site or campaign tags), device and browser type, country (derived from your IP address, which itself is not stored), time on page and loading speed. This measurement stays with us and is not shared with third parties.
Two cookies make this work: az_aid, a random id kept for up to a year to recognize a returning visit, and az_sid, which marks a visit and expires after 30 idle minutes. After you sign up, the id is linked to your account so we know which channel brought you and where the signup flow needs work. You can delete these cookies at any time in your browser settings.
To measure our ads on Facebook and Instagram, the website also runs the Meta Pixel, from Meta. It sends Meta the pages viewed on the website, in the signup and in the assistant setup, and the steps of signing up: the signup form shown, a verification code sent, a new account opened, and a payment started and completed (the product and the amount). Your phone number and what you type into forms are not sent, and from the dashboard only the payment is. Along with this Meta receives your IP address and browser details, and keeps the cookies _fbp and _fbc (up to 90 days; _fbc only when you came from an ad) to connect the ad you saw with what you did on the site afterwards.
We use this to learn which ads bring signups and to show our ads to people like them. Meta also processes this data for its own purposes, under its data policy (facebook.com/privacy/policy). You can block these cookies in your browser settings or with an ad blocker, and choose which ads you see in the Ad preferences of your Meta account.
Controller and processors
The business owner is the controller of the call database for their business; Azorly holds and processes that data on the owner's behalf, on the owner's instructions and only to provide the service. Azorly is the controller of its own customer data.
Sub-processors: ElevenLabs (voice processing, transcription and running the conversation), OpenAI and Google (the language models ElevenLabs' voice platform uses during the call), Twilio (telephony, verification codes, and SMS and WhatsApp delivery), Meta (the WhatsApp platform), Supabase (data storage), Vercel (website and server hosting), Anthropic (text processing for the dashboard copilot and for setup suggestions, and reading menus from photos), Resend (sending and receiving email), Polar (payments, invoices and VAT; Polar acts as merchant of record and receives payment details directly from the customer). Each is contractually bound to protect the data and use it only to provide the service.
The Meta Pixel, described under "Cookies and site analytics", is the exception: Meta also processes the data it sends for its own purposes, as an independent controller, under its own terms and policy.
Why we use the data
To answer calls, summarize them and deliver requests to the business; to improve the assistant's answers for that business; to provide support and bill by usage; to measure our ads (see "Cookies and site analytics"); and to meet legal duties. We do not sell data and do not use recordings to train general models.
Retention
Call recordings, transcripts and summaries, together with the caller details stored with them (name, phone number, request details, notes and the text of the messages sent about it), are deleted automatically 365 days after the call. After that only statistics remain: when the call took place, how long it lasted and why. For now the business owner cannot change the retention period or delete a single call in the dashboard; requests for earlier deletion go to privacy@azorly.co.il, and we handle them. The owner can export the data from the dashboard before it is deleted. Businesses that must keep calls longer under the Consumer Protection Law are responsible for keeping their own copy, for example by exporting it.
Security
Data is encrypted in transit and at rest, access is limited to the business's own users and to Azorly staff who need it to provide the service and support, and changes to the assistant's settings are kept in a history. We follow the Privacy Protection (Data Security) Regulations 5777-2017 at the level required for databases of this kind. Privacy and data-security questions: privacy@azorly.co.il.
Where data is stored
Our sub-processors' servers are in the EU and the US. Transfers follow the Privacy Protection (Transfer of Data Abroad) Regulations. Israeli data residency is on our roadmap for customers who need it.
Your rights
Everyone may access the information held about them, ask to correct or delete it, and object to its use for direct marketing. Callers may contact the business they called or us at privacy@azorly.co.il; we forward the request to the business and help resolve it within 30 days.
Messages
Messages sent to callers through Azorly (an appointment confirmation once the business owner approves it, and a short acknowledgement when a caller replies to it) are service messages, not advertising. Businesses may not send advertising through Azorly without prior explicit written consent, per section 30A of the Communications Law.
Changes and contact
We will update this policy as the service changes and notify customers of material changes. Questions: privacy@azorly.co.il.