Evara Automations
Privacy Policy
Effective 14 September 2026
Evara Automations is business automation software. It connects to services a client chooses, in order to carry out the automation that client has asked for. This explains what we collect, why, what we store and what we do not do.
01Who we are
Evara Automations is operated by Evara, founded by Eva Jereb, in Slovenia. You can reach us about anything in this policy at info@evara.studio.
We provide automation software to businesses. A client connects the systems they already use, and Evara performs the specific automation they have configured.
02Information we collect
Account and business information. What a business tells us when it applies and while it uses the product:
- business name, contact name, email address, phone number and website, where given
- business type, and the answers given on the application form
- which booking software is used and how it will be connected
- settings for the automations held by that business
Operational automation data. What the automation needs in order to work:
- appointments — service, staff member, start time, duration, price and status, as published by the client's own booking system
- the customer name as it appears in the client's booking notification, where the automation needs it to identify the appointment
- booking events — that a booking was created, changed, rescheduled, confirmed or cancelled, and when
- cancellation and recovery cases — what was at risk, how many suitable customers were eligible, how many were contacted, the outcome and how long it took
- records of automation runs and of failures, so a problem can be diagnosed and fixed
Connected-service data. Covered in the next section.
03Google user data
Some booking systems have no usable interface for software, so Evara offers a booking email connection: with the client’s authorisation, it reads the booking notifications their booking software already sends them. This is optional and only applies to clients who choose it.
Where a client chooses it, Evara requests one Google permission and no others: gmail.readonly. We do not request permission to send, delete or modify mail.
Being honest about what that permission is: the authorisation Google grants for gmail.readonly is broad enough to read Gmail messages and settings generally. Google does not restrict it to one sender, and we will not pretend it does. What narrows it is Evara’s own behaviour, described next.
What Evara actually retrieves. The connector is designed to retrieve and process only verified booking-system messages needed to operate the automation. In practice that means two filters:
- Evara asks Gmail only for messages matching the connected booking system's own search, over a recent window, rather than reading the mailbox.
- Every message returned must then come from that booking system's sender, carry one of its notification subjects, and contain its own structural markers. A message failing any of those checks is discarded, and nothing about it — not the sender, not the subject, not the body — is kept.
Setting up a booking system we have not seen before. Some clients use booking software Evara has never connected to, so there is no sender to filter on yet. In that case, and only during setup, Evara looks differently: we give you a short reference to put in a test booking and ask Gmail for that exact text, or - if your software strips it - we make a bounded, recent search for appointment words. Either way we show you what we found and you point us at it. Only the message you confirm is processed; everything else the search returned is discarded unread by anything other than the check that decided it was not a booking. Once one message is confirmed, Evara has learned that provider’s sender and format, and every search afterwards is the narrow one described above.
What we take from a message that passes. The booking fields the automation needs: booking reference, service, staff member, start time, duration, price, status, the customer name as printed, and the booking link. We also store the Gmail message id of that message, so the same notification arriving twice is recognised and not processed twice.
What we use it for. Only to provide the automation the client asked for:
- recognise that a booking was created, changed or cancelled
- keep the client's appointment and recovery records up to date
- run the configured automation, such as offering a cancelled slot to suitable customers
- show the client the outcome in their own workspace
- diagnose a failure in that client's automation
What we do not do. Each of these is a statement about the software as it is built:
- Evara does not sell Google user data.
- Evara does not use Google user data for advertising.
- Evara does not read unrelated email to build marketing or customer profiles.
- Evara does not use Google user data to train general-purpose AI models.
- Evara does not transfer Google user data to third parties except the infrastructure providers described in section 06, acting on our instructions to run the service.
Evara’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
04What is stored, and what is not
There is a difference between the message in the client’s mailbox and the record Evara keeps, and it matters:
- We do not keep a copy of the email itself. We store the booking fields taken from it, and the Gmail message id that identifies it.
- Messages that do not pass the checks in section 03 are not stored as automation data at all.
- Where a matching message cannot be parsed confidently, we record that it could not be — the message id, which fields were missing, and the confidence — with no subject, sender or body.
- Authorisation credentials, including the Google refresh token, are encrypted at rest and are never written into ordinary application records or logs.
05Why we are allowed to process it (GDPR)
Evara operates in Slovenia and the EU. Depending on the data, we rely on:
- performance of a contract, or steps taken at a business's request before one — providing the automation a client has asked for
- legitimate interests — keeping the service running, secure and diagnosable, and communicating with a business about its own account
- consent — where consent is the right basis, such as connecting a Google account, which a client gives explicitly and can withdraw
- legal obligations, where one applies
A client acts as controller for their own customers’ information; Evara processes it on their instructions in order to run the automation they configured.
You have the right to ask for access, correction, deletion, restriction, portability where it applies, to object to processing based on legitimate interests, and to withdraw consent where processing is based on it. Write to info@evara.studio. You may also complain to the Slovenian Information Commissioner (Informacijski pooblaščenec).
06Who processes it with us
We use infrastructure providers strictly to run the service, under our instructions: a hosting provider for the application, a managed database for its records, an email provider for transactional messages such as sign-in links, Evara’s own automation runtime for executing automations, and Google’s APIs where a client has connected Google.
We do not share Google user data with unrelated third parties, and we do not sell data.
07How long we keep it
We keep account and operational data for as long as it is needed to provide the service, to keep it secure and diagnosable, and to meet legal obligations that apply to us.
There is no self-service deletion screen today. A client can ask us to disconnect a service or delete their data by writing to info@evara.studio, and we will disconnect the connected services, remove the stored credential material, and delete the automation records belonging to that business, except anything we are required to retain.
08Your control over the Google connection
A client who has connected Google can:
- revoke Evara’s access at any time from their own Google Account, at myaccount.google.com/permissions — this takes effect immediately and stops any further reading
- ask us to disconnect it and remove the stored credential, by email
Revoking access stops the automation that depends on it. We will say so in the workspace rather than fail quietly.
09Security
We apply reasonable technical and organisational measures: credentials encrypted at rest, access to client data scoped to the signed-in business, transport encryption, and administrative access limited to people who need it. We do not hold a SOC 2 or ISO certification, and we do not claim one.
10Children
Evara Automations is intended for businesses and the people who run them. It is not directed to children.
11Changes
We may update this policy. When we do, the effective date at the top changes. If a change materially affects how we handle client or Google user data, we will tell affected clients.
12Contact
info@evara.studio — for any question, request or complaint about this policy.
Evara · info@evara.studio