Privacy Policy
1. Introduction
Eliza ("we", "us", "our") is an AI-powered telephone receptionist for service businesses of any kind: it answers calls, books and manages appointments, and can also act as an information line that answers questions without booking anything.
Eliza is operated by BAUM Engineering, Arad, Romania. We are the data controller for the account data of Business Users. For the personal data of Callers we act as a processor on behalf of each Business User: the business decides why an appointment is taken and what is done with it, and we handle that data on their instructions. Questions and requests about your data go to info@baum.ro.
This Privacy Policy explains what personal data we collect, why we collect it, how we use and protect it, and what rights you have over it. It applies to all users of the Eliza platform, including business owners who register an account ("Business Users") and their customers who interact with Eliza over the phone ("Callers").
By using Eliza, you agree to the practices described in this policy.
2. Information We Collect
Business Account Data
When you register and configure your Eliza account, we collect:
- Your email address and hashed password — or, if you sign in with Google, the email address of your Google account. From Google we use only that address; we do not store your name or picture
- Business name, phone number, email address and timezone, and whatever else you choose to enter: your address, a description, a number to forward calls to, and the messages and texts you write for your line
- Staff member names, phone numbers and email addresses; where your type of business uses them, their specialty, the areas they cover and the languages they speak; and their time off, with any reason you enter
- Working hours and schedule configurations
- Service names, durations and prices, and any products or property listings you add
Caller Data
When a customer calls your business number and interacts with Eliza, we may collect and store:
- The caller's phone number (provided automatically by the telephone network via Twilio)
- The caller's name, as stated during the conversation
- Appointment details: requested service, preferred staff member, and chosen date and time
- A short numeric PIN generated for appointment verification or cancellation
- Depending on your type of business, the details that kind of appointment needs — for example a vehicle's registration and model, a pet's name and species and what is wrong with it, the address of a job and notes on access (never door codes or keys), or the number of guests. A one-sentence reason for the visit, a description of a legal matter or the name of the other party in it is recorded only if the business has chosen to ask for it. Eliza never asks for anything a type of business does not use.
- The text of a message, when a caller leaves a voicemail or asks to be called back, together with any name and number they give in it
Call Logs and Metadata
We retain metadata about each call handled by Eliza, including:
- Origin and destination phone numbers
- Call start time, duration, and final status
- Whether an appointment was booked, rescheduled, or cancelled
- A one-sentence AI-written summary of how the call went, shown in your dashboard. It is generated without the caller's name, phone number, e-mail address or PIN
Voice and Conversation Data
Visits to This Website
When you open one of this website's public pages — the home page, the FAQ, this policy or the terms — our server records your IP address, the country that address is registered to, the page, the time, and the identification string your browser sends with every request (its user agent). The country is looked up on our own server, from a database kept there; your address is not sent to anyone else for this. We use these records to see how many people visit the website and from where, and to tell people apart from automated traffic. No cookie is set for this, and nothing follows you to any other website.
Google Calendar
If you connect a Google Calendar, we store the address of the Google account you connected, an encrypted permission that lets Eliza reach your calendar, and which calendar belongs to which staff member. To know when you are busy, Eliza reads the events in those calendars and keeps the start, end and title of each one; the titles are shown only to you, on your dashboard. Every booking Eliza makes is added to your calendar with the customer's name, the service and, for a restaurant, the number of guests — never the caller's phone number, PIN, address or the reason for their visit.
Businesses We May Contact
To find businesses that might want Eliza, we keep a list compiled from public business directories: each business's name, category, city and county, and the phone number and e-mail address published there. We may e-mail those businesses or call them. Our calls are made by Eliza itself, which says at the start that it is an AI. We keep a record of each e-mail and call — for a call, its written transcript and a short summary — and the same applies when anyone calls our own sales line. If you tell us not to contact you again, through the unsubscribe link, during the call or by writing to info@baum.ro, we record that and do not e-mail or call that address or number again.
Signup Codes
If you sign up with a code — from a partner's link, an advertisement, or typed in yourself — your account stores which code it was, how it arrived (a link, the registration form, Google sign-up, the Account page, or set by us) and when. The code travels in the page's web address; nothing is stored in your browser for it and no cookie is set. When a code link is opened we count one click for that code on that day, and record nothing about who clicked. If the code belongs to a partner who introduced you to Eliza and is paid a share of what you pay, we give that partner a statement listing your business's name, your plan and the amounts you have paid, so that they can check what they are owed. They may use it for nothing else, and they never see your calls, your callers, your appointments or anything else in your account.
3. How We Use Your Information
We use the data we collect to:
- Operate the Eliza service — answering calls, booking and managing appointments
- Display appointment and call-log history in your business dashboard
- Authenticate and manage your account securely
- Determine staff availability and match callers to the right team member
- Improve reliability and diagnose technical issues within the platform
- Contact businesses that might want Eliza, as described in Section 2
- Apply signup-code offers, see which partners and campaigns bring customers, and work out what partners are owed, as described in Section 2
We do not sell personal data to third parties. We do not use Caller data for advertising or any purpose beyond operating the appointment scheduling service for the business you called.
4. Legal Basis for Processing
We process personal data only where the law gives us a basis for doing so. Which basis applies depends on what the data is for:
- Running the service — answering calls, checking availability, and creating, moving or cancelling appointments. Performance of a contract with the Business User (Article 6(1)(b) GDPR) and, as regards the caller, the legitimate interest that both they and the business have in the appointment actually being arranged (Article 6(1)(f)).
- Your account and subscription — registering you, signing you in, taking payment. Performance of a contract (Article 6(1)(b)) and, for invoicing and accounting records, a legal obligation (Article 6(1)(c)).
- Keeping the platform working and safe — rate limits, the PIN attempt budget, blocking abusive callers, diagnosing faults. Our legitimate interest in a service that is neither abused nor broken (Article 6(1)(f)).
- Publishing your business details, if you switch it on. Your consent (Article 6(1)(a)), which you can withdraw at any time using the same switch.
- Knowing who visits this website — counting visits to our public pages and where they come from. Our legitimate interest in understanding how our website is used and keeping it safe (Article 6(1)(f)). You can object to it at any time (see Section 10).
- Contacting businesses that might want Eliza — the list, e-mails and calls described in Section 2. Our legitimate interest in offering our service to businesses (Article 6(1)(f)). You can object at any time, and we will stop.
- Signup codes and partners — recording which code an account came with, counting clicks on code links, and telling a partner what they are owed. Our legitimate interest in knowing which partners and campaigns bring us customers and in paying partners correctly (Article 6(1)(f)). Applying a code's discount to your subscription is part of our contract with you (Article 6(1)(b)).
We do not rely on consent for caller data, and Eliza does not ask callers for it. At the start of every call Eliza says what it is and that the caller's name, number and appointment details are stored in order to make the booking. That is the information Articles 13 and 14 require us to give, not a consent request, and the call does not stop to wait for an answer — the caller has rung up precisely so that those details will be used. If a caller does object, we do not process them anyway: Eliza hands the call to a human instead, or, if there is no one to hand it to, apologises and ends the call.
Sensitive details. Some businesses can choose to have Eliza ask the reason for a call — a health practice the reason for the visit, a law firm what the matter is about. The answer may reveal health data or other sensitive information. Whether to ask is that business's decision as controller, and so is its legal basis (Article 9 GDPR for health data). Eliza records only the caller's own short answer and asks no follow-up questions about it; a business that does not choose this has nothing of the kind recorded.
5. Third-Party Services
Eliza relies on the following third-party infrastructure providers. Each has its own privacy policy that governs how they handle data passed through their systems.
Twilio
All telephone calls are routed through Twilio's voice platform. Twilio receives call metadata (phone numbers, timestamps, duration) and may retain records in accordance with their own retention policies. Please review Twilio's Privacy Policy.
Google Gemini API
Real-time voice understanding and AI responses are powered by Google's Gemini API, which is the default for every account. Audio streams are sent to Google's servers for processing. We do not receive or store the raw audio after the call ends. Please review Google's Privacy Policy.
Google Sign-In and Google Calendar
If you sign in with Google, Google tells us the e-mail address of your account. If you connect a Google Calendar, Eliza reads your calendars' events and writes its bookings to them through Google's Calendar API, as described in Section 2. Eliza's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements: we use your calendar data only to know when you are busy and to keep your bookings in step, we never use it for advertising, and we do not pass it to anyone else.
OpenAI
After a call ends, its text transcript is sent to OpenAI once to produce the short call summary shown in your dashboard. The transcript is not stored by us, and the summary is written without the caller's name, phone number, e-mail address or PIN. For a law firm no transcript is sent at all: its summary is built from the booking record. Where your account uses an OpenAI voice model, the call audio is streamed to OpenAI instead of Google. Please review OpenAI's Privacy Policy.
Hosting and Database
Appointment and account data is stored in a PostgreSQL database hosted on infrastructure we control. Data is not shared with hosting providers beyond what is technically necessary to operate the service.
Stripe
Subscriptions and pay-per-call top-ups are processed by Stripe. Card details are entered on Stripe's own checkout page — we never see or store a full card number. We hold your Stripe customer and subscription identifiers, your plan, and the amounts due or paid. Please review Stripe's Privacy Policy.
E-mail and SMS
Verification codes, alerts and other transactional e-mail are sent from our own mail server. SMS confirmations to your customers, and the notifications your staff receive, are sent through Twilio and are covered by the same terms as calls.
Fonts, Page Components and Video
Our pages load fonts from Google Fonts and some page components from the jsDelivr and cdnjs (Cloudflare) networks, so your browser connects to those services and they see your IP address, as with any website you open. The video on the home page is embedded in YouTube's privacy-enhanced mode (youtube-nocookie.com), which does not set a tracking cookie unless you play it.
6. International Data Transfers
Our own servers and database are in Europe. Several of the providers in Section 5 are headquartered in the United States, however, and personal data may be processed outside the European Economic Area by Twilio, Google, OpenAI and Stripe.
Where data leaves the EEA, the transfer is made under the European Commission's Standard Contractual Clauses, or under the EU–US Data Privacy Framework where the provider is certified under it. You can ask us which applies to a particular provider and for a copy of the safeguards in place.
7. Data Retention
Business account data is retained for as long as your account is active. Deleting your account starts a 30-day countdown and shows you the exact date: nothing is erased in the meantime, the service keeps working, and you can cancel the request at any point before that date. On that date your account and everything belonging to it are permanently erased, unless we are required to retain something by law.
Call-related data is purged automatically on a fixed schedule, whether or not you ask. 30 days after an appointment has taken place, everything personal about it is erased — the caller's name, phone number and PIN, anything else recorded for that kind of appointment (such as an address, a plate number, a pet's details or a reason for the visit), and the customer record behind them — while the booking itself stays in your history. Phone-book entries are deleted 180 days after that number last called. Call summaries, call records and messages left by callers are deleted once they are 180 days old; on a browser call, the caller's name is cleared after 90 days and the whole record is deleted at 180. A number blocked automatically after abusive calls is released after 365 days; a number you block by hand is kept, together with the reason you gave, until you unblock it — that is a standing decision of yours rather than a log that has gone stale. You may request earlier deletion at any time.
Caller data (name, phone number, appointment details) is stored only for as long as needed to fulfil the appointment and is tied to the above retention window.
Records of visits to this website (Section 2) are deleted automatically 90 days after the visit.
If you connect a Google Calendar, the times and titles Eliza keeps of your events are deleted 30 days after each event ends, and at once if you disconnect. The bookings Eliza has added to your Google Calendar are entries in your own calendar: our automatic clean-up does not reach them, and they stay there until you delete them.
Our backups are taken every six hours and each is kept for 30 days, so data erased from the service disappears from the backups within about 30 days as well.
The list of businesses we may contact, and the record of our e-mails and calls to them, are kept for as long as we may still offer them our service; a business can ask us to delete its details at any time. A request not to be contacted again is kept permanently, because it is the record that stops us contacting that business again.
The signup code an account came with is kept for as long as the account exists. The daily click counts on code links contain nothing about the people who clicked. The statements we give partners are kept as accounting records for as long as the law requires.
8. Data Security
Passwords are never stored in plain text — we use bcrypt hashing — and when you choose one we check it against passwords exposed in known breaches, sending only the first five characters of its hash. All data in transit is protected using TLS encryption. If you connect a Google Calendar, the permission that lets Eliza reach it is stored encrypted. Your data is backed up automatically every six hours, so it stays safe even in the event of a hardware failure. Access to customer and appointment data is scoped to the authenticated business account that owns it; one business cannot access another's data, and we do not access, sell, or share your business's data in the ordinary course of business.
While we take reasonable precautions, no system is completely immune to security risks. We encourage Business Users to use strong, unique passwords and to contact us immediately if they suspect unauthorised access.
9. Cookies
Eliza itself sets two cookies, and neither follows you to any other website. The public pages also carry the Google Ads tag, which sets advertising cookies only if you accept them in the banner.
- session — a signed cookie that keeps you signed in to the dashboard. Strictly necessary: without it there is no way to stay signed in. It is cleared when you sign out, and stops working by itself if your password changes.
- lang — remembers which language you chose, for a year, so pages come back in it. Set only when you pick a language yourself.
- Google Ads (_gcl_au and similar, set by Google) — tell us which of our ads brought a visitor here, so we can tell which ones work. Only on the public pages, never in the dashboard, and only after you click Accept. Until then Google receives cookieless signals with no identifier. Your choice is kept in your browser's local storage, not in a cookie. See how Google uses advertising cookies.
The session and lang cookies are either strictly necessary or set by an action you took yourself, so they need no consent. The Google Ads cookies do, which is what the banner asks for; you can change your answer at any time. You can also block or delete any of them in your browser, but the dashboard cannot sign you in without the session cookie.
Your browser's local storage also keeps a few preferences that never leave it: your light or dark mode choice, your cookie choice, and some dashboard display settings.
10. Your Rights
Depending on your jurisdiction, you may have the right to:
- Access the personal data we hold about you
- Correct inaccurate or incomplete data
- Delete your data ("right to be forgotten")
- Restrict how we process your data in certain circumstances
- Port your data to another service in a machine-readable format
- Object to processing we carry out on the basis of our legitimate interests
- Complain to a data protection supervisory authority
To exercise any of these rights, please contact us at the address in Section 15. We will respond within 30 days.
Callers who wish to have their appointment data or phone number removed from a business's records may contact that business directly, or reach us and we will facilitate the request.
If you believe we have mishandled your personal data you can lodge a complaint with your national supervisory authority. In Romania that is the National Supervisory Authority for Personal Data Processing (ANSPDCP), dataprotection.ro. We would much rather you came to us first at info@baum.ro so that we can put it right.
11. Children's Privacy
Eliza is not directed at children under the age of 16. We do not knowingly collect personal data from children. If you believe a child has provided us with personal data, please contact us and we will delete it promptly.
12. Changes to This Policy
We may update this Privacy Policy from time to time. When we do, we will revise the "Last updated" date at the top of this page. For significant changes, we will notify registered Business Users via email. Continued use of Eliza after changes are posted constitutes acceptance of the updated policy.
13. Publishing Your Business Details
Your call link page is reachable by anyone who has the link. Separately, you may choose to publish that page: this adds your business details to it and allows search engines to list it, so that customers can find you without having been sent the link.
Publishing is off unless you turn it on, in Eliza Settings → Call Handling. We never enable it for you. When it is on, the page shows your business name and your services, with their duration and price. Three further details are each their own separate choice, and each is off until you enable it: your business description, your address, and your staff members' names together with their working hours. Your telephone number is never published.
If you publish your staff members' names and hours, you are publishing information about other people. You are responsible for making sure you are entitled to do so — normally by informing them and, where required, obtaining their agreement. Publish only what those people would be content to see on a public web page.
You can stop publishing at any time using the same switch. We stop serving the details immediately and remove the page from our sitemap on the next request. We cannot control how quickly a search engine drops what it has already stored: published details may remain visible in search results and caches for some time afterwards, and copies made by others while the page was public are outside our control.
14. If You Installed Eliza from Shopify
This section applies to businesses that installed Eliza from the Shopify App Store. The rest of this policy applies to them as well.
What Shopify sends us
When you install Eliza, Shopify gives us your shop's name, its myshopify.com address, its contact e-mail, its business address, time zone and currency, and whether it is a development store. We use them to create your Eliza account and fill in your business details, which are then yours to change in Eliza. Eliza asks Shopify for permission to read your products, which it keeps in step with your store so that it can answer callers' questions about them, and, only if you switch on answers about your store's policies, to read those policies. It reads no orders, customers or payment details from your store. When a caller asks for a product's link, Eliza texts the product's page to the number they are calling from.
Signing in
Inside your Shopify admin, Shopify signs you in to Eliza with a short-lived token it issues for each request. Your Eliza account has no password of its own, and Eliza sets no cookie there. The access token Shopify issues for your shop is stored encrypted and is deleted when you uninstall.
Billing
Your plan is chosen and paid for through Shopify, and appears on your Shopify bill. We learn from Shopify which plan your shop is on and whether it is active. We never see your payment details, and Stripe is not involved.
Privacy requests Shopify passes on
Shopify passes three kinds of privacy request on to us, and Eliza acts on each by itself:
- A customer asks for their data. Eliza gathers what your Eliza account holds about that person, matched by their phone number or e-mail address, into a file, and e-mails you that it is ready. You download it under Account → Data requests, for 30 days, and pass it on.
- A customer asks to be erased. Eliza removes that person's details from your account: their name, phone number and e-mail address, their messages, call summaries and phone-book entry, and the details of their bookings. Appointments still to come stay in your calendar without those details, marked “Anonymised on request”, so the time stays reserved. A block you placed on their number is kept, without any note you wrote, on the legitimate interest (Article 6(1)(f) GDPR) of protecting your line from abuse.
- Your shop asks to be erased. Shopify sends this 48 hours after you uninstall Eliza. We then delete your Eliza account and everything in it, and release its phone number. If you reinstall before then, nothing is erased. Backup copies age out within a further 30 days.
When you uninstall, your plan ends and Eliza stops answering your calls. Your settings and data are kept for those 48 hours, so that a reinstall finds them.
15. Contact
If you have questions about this policy, wish to exercise your data rights, or need to report a concern, please contact us at:
Email: info@baum.ro