Privacy Policy
This document is not selling anything. It is here so that you can check what data we process, who we pass it to and how long we keep it — before the first call.
This is a translation. In case of any discrepancy, the Slovak version prevails.
01Who manages the data
The controller is Good Friends s. r. o., the company behind Renly. Full identification and contact details are on the Contact page.
02Two roles to tell apart
Renly acts in two different capacities, and different rules apply to each:
- Controller — for data of visitors to this website, data of our customers, i.e. the organisations that use Renly, and data of organisations we look up and contact as potential customers. We decide about this data.
- Processor — for data that a visitor to our customer's website enters into the assistant chat, and for data the customer itself puts into Renly — for example contacts and deals in the CRM, tasks, invoices and their recipients, or calendar events. There the customer is the controller; we process that data on its behalf and according to its instructions.
The assistant chat on this website, renly.sk, is our own — for it, we are the controller.
If an assistant answered you on someone else's website and you want to exercise your rights, contact the operator of that website first. We will gladly help them handle your request.
03This website
The website uses a strictly necessary cookie to remember your choice and — only with your consent — analytics and marketing cookies. Details are below in the section Cookies and traffic measurement.
Contact form
When you write to us via the contact form, we process your name, email address, optionally your company name and website address, and the text of your message. We store the enquiry in our system for managing business cases and send a confirmation that the message arrived to the address you entered. We use the data solely to reply to you and handle your enquiry. We do not use it for marketing and we do not pass it to anyone except the providers listed below, who process it for us.
The legal basis is our legitimate interest in answering the questions you send us (Art. 6(1)(f) GDPR) and, if you are asking about entering into a contract, also steps taken before entering into it (Art. 6(1)(b) GDPR).
Browser storage
The assistant chat stores in the browser only what it cannot work without. These are not cookies and they are not used for tracking:
- the identifier of the ongoing conversation (
localStorage), so that it is not lost when you move to another page — it is stored only after the first message and is valid for 12 hours, - pinning of the chat window (
localStorage), only if you pin the window, - display of the welcome bubble (
sessionStorage), so that it does not appear repeatedly — it is deleted when you close the browser.
You can delete this data at any time in your browser settings.
Demos for companies
When an assistant demo is opened at /demo/…, we record the time and the device
type (computer, tablet, mobile). We use the IP address only for short-term
protection against abuse and we do not store it.
Cookies and traffic measurement
On your first visit we ask for your consent. Until you decide, or if you decline,
the website stores only the strictly necessary cookie renly-consent, in which it
remembers your choice for one year.
- Analytics cookies (Google Analytics 4) — how many people visit the website, where they came from, which pages they read and whether, for example, they sent the contact form or clicked to sign up. We never send your name, e-mail or the text of your message to them.
- Marketing cookies — measure whether a visitor came from our advertising (for example Google Ads) and make it possible to show ads to people who have already visited the website. We use them only while an ad campaign is running.
We manage measurement and advertising tools through Google Tag Manager. Without consent they store no cookies; Google receives only anonymous signals without an identifier, from which it estimates overall traffic (Google Consent Mode).
The legal basis is your consent (Art. 6(1)(a) GDPR and Section 109(8) of Slovak Act No. 452/2021 Coll. on Electronic Communications). You can change or withdraw your consent at any time via Cookie settings in the website footer; withdrawal does not affect processing carried out before it.
The list of cookies is updated automatically according to the tools we currently use on the website:
04Customer account
When an account is created, we process identification and contact details of the organisation and its users, billing details and operational records of service use. We need them to perform the contract (Art. 6(1)(b) GDPR), for invoicing and to meet our legal obligations, in particular accounting and tax obligations (Art. 6(1)(c) GDPR). Card and recurring payments are processed by the GoPay payment gateway in compliance with PCI DSS Level 1. Full payment card details never reach us and Renly does not store them; we keep only an opaque payment reference needed to manage the payment and any automatic renewal.
Sign-in with Google, Microsoft and Apple
If you choose to sign in with Google, Microsoft or Apple, we process the unique identifier of your account with that provider, your email address and basic profile data, such as your name. Apple sends us your name only on the first sign-in, and if you choose to hide your email, we receive a forwarding address from Apple instead of yours. We use this data only to create or find your account, sign you in, link accounts and accept a company invitation. We do not use it for advertising, profiling or model training.
You can remove the link at any time in your profile. We keep the provider identity for as long as it is linked to your Renly account; after unlinking we delete it. For security reasons, unlinking ends active sessions and connected Claude and ChatGPT access, but it does not delete the Renly account itself or company data.
Connected Google and Apple calendars
If you connect your Google Calendar or Apple (iCloud) calendar to Renly, Renly:
- reads the list of your calendars and the events in them (title, time, location, description, link and whether the time is free or busy) from one month back to one year ahead, to show them in the Renly calendar next to company events and highlight where they overlap;
- writes to your calendar only when you yourself edit, delete or create an event in Renly;
- stores a copy of the events and the access credentials (a refresh token for Google, an app-specific password for Apple) encrypted on servers in the EU;
- shows colleagues in your company only when you are busy, without the title, location or description of your events;
- does not sell data from your calendars, share it with third parties, use it for advertising or for training or improving artificial intelligence models, or send it to language models.
You can disconnect at any time in the Renly calendar, at the connected account. Renly then deletes the copy of the events and the access credentials and, for Google, revokes access. You can also revoke access in your Google or Apple account settings. You turn this feature on yourself; the legal basis is the performance of a contract (Art. 6(1)(b) GDPR).
Renly's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Sending documents from your Google or Microsoft 365 mailbox
If you choose to send documents through Google or Microsoft 365 in Finance, Renly:
- receives from the provider only the permission to send email on your behalf
(Google
gmail.send, MicrosoftMail.Send) and your email address, which becomes the sender address; - does not read, search or store your mail, contacts or attachments — it has no permission to do so;
- sends from your mailbox only the emails you start in Renly or have set up (a document, a payment reminder, a thank-you for payment and a test email to your own address); sent emails appear in your Sent folder;
- stores the refresh token encrypted on servers in the EU and never shows it in the app, in logs or in error reports;
- does not sell data received from Google or Microsoft, does not share it with third parties, does not use it for advertising or to train or improve artificial intelligence models, and does not send it to language models.
You can disconnect at any time in Finance. Renly then deletes the token and, for Google, also revokes access at Google. You can also remove access in your Google or Microsoft account settings. If access stops working, documents are sent from the Renly address with replies going to your address. The legal basis is the performance of a contract (Art. 6(1)(b) GDPR); for the personal data of your customers in the documents we act as your company's processor.
Renly's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Documents from Google Drive
If you connect a Google Drive folder to the Knowledge Base, Renly reads only the files you have shared and processes them like other knowledge sources. The legal basis is the performance of a contract (Art. 6(1)(b) GDPR). If you put other people's data into the calendar or documents, such as meeting attendees, we process it as a processor for your company.
05Renly mobile app
The Renly mobile app for iPhone and Android is another way into your customer account. You sign in with the same account as on the web and the app works with the same data described above. In addition, it processes only the following:
- Camera and photos — only when you photograph a document yourself, add a photo to a task or job, pick a photo from the device or scan a barcode. Only what you confirm is uploaded to Renly; we do not read other photos on the device.
- Sharing to Renly — files you send to the app through the system Share sheet are kept on the device temporarily and uploaded to Renly only after you confirm.
- Location — only when you ask the job map to show where you are. The location stays on the device and is not sent to our servers.
- Notifications (push) — if you allow them, we store a device token from Firebase Cloud Messaging (Google) and the operating system type with your account. The notification text, for example that a new document arrived, is delivered to the device by Google and, on iPhone, also by Apple. We remove the token from your account when you sign out.
- Anonymous usage statistics — through Firebase Analytics (Google) we record which screens of the app are opened and which main actions are taken (for example "invoice issued"). We do not send names, e-mail addresses, record identifiers or content, and we do not collect the device advertising identifier. You can turn the statistics off in the app under Profile.
- Error reports — when an error occurs in the app, we send Sentry a technical description of the error, the app and system version, the device type and the signed-in user's identifier and e-mail address so we can trace it. We do not send document content or passwords.
The app does not track you across other companies' apps and websites and we do not use its data for advertising. The legal basis is performance of the contract (Art. 6(1)(b) GDPR); for statistics and error reports our legitimate interest in a reliable and understandable app (Art. 6(1)(f) GDPR). You can revoke access to the camera, photos, location and notifications at any time in the device settings. Uninstalling the app also removes the data stored on the device. To have your account deleted, follow the Data deletion section below.
06Leads from Facebook and Instagram ads
A business using Renly can connect its Facebook Page. Renly then retrieves leads from that business's lead forms via the Meta platform (Meta Platforms Ireland Ltd.) and stores them in that business's CRM.
- Role: the business whose form was submitted is the controller of this data. Renly acts as a processor and processes it only on the business's behalf and instructions.
- What data: the fields the business requests in its form (typically name, email, phone and answers to questions), submission time, and identifiers of the ad, campaign and form the lead came from.
- Purpose: to let the business contact the person who requested it through the form and keep a record of that communication.
- What we don't do: we do not sell lead data, use it for our own marketing or to train AI models, or share it with other companies.
- Retention: until the business deletes it in the CRM or closes its account; it is then deleted as described under Data deletion.
- Disconnecting: the business can remove the connection at any time in Renly's integration settings or on Facebook under Settings → Business Integrations. After disconnection we no longer retrieve new leads.
07Finding and contacting organisations
Renly looks up companies and organisations that an AI assistant could help, and may contact them by email with a demo of an assistant for their website. Here we are the controller.
Where the data comes from and what it is
- Public sources: OpenStreetMap map data and the Slovak Register of Legal Entities and Register of Financial Statements — name, company ID, address, legal form, industry, size category and figures from financial statements.
- The organisation's website: the website address, the contact email and phone listed on it, and technical details such as whether it already has a chat.
We write to the organisation's contact addresses, not to people's private addresses. We do not store the names of statutory representatives from the registers. If we exceptionally use the work email of a specific person, we record where we got it. If the organisation replies, we store the text of the reply and the details it gives in it, such as the writer's name and phone. Only authorised Renly staff see them, and they continue in our deal management system.
Legal basis and how to opt out
The legal basis is our legitimate interest in offering organisations a service related to their activity (Art. 6(1)(f) GDPR). We send an organisation one email and, if it does not reply, one automatic reminder. After that, one of our sales staff may get in touch, no later than 60 days after the first email. You can refuse further messages at any time by replying to the email or writing to support@renly.sk; we respect the refusal immediately and keep the address only in a refusal list so that we do not contact it again.
08AI assistant chat
This is the part that concerns processing by third parties, which is why we describe it in detail.
What data is processed
When a visitor writes to the assistant, we process:
- the content of messages from the visitor as well as the assistant's answers and messages from the operator who replies to the visitor,
- attachments the visitor adds to the chat,
- voice recordings, if the visitor uses voice mode,
- the page on which the chat runs — the address without query parameters and, with the feature enabled, also its title,
- location, only if the visitor shares it and the customer has this feature enabled.
Sensitive personal data, payment details and login credentials do not belong in the chat. The assistant will never ask for them.
When data goes to AI providers
We do not call language models only when writing an answer. We pass data to them in these situations:
- The assistant's answer. The model that writes answers receives the assistant's instructions, the current message with attachments, several previous messages of the conversation (ten at most by default), excerpts from the knowledge selected by search and, depending on the settings, also the page and location. For images it receives the image itself, for documents the text extracted from them.
- Semantic search. So that the assistant finds the right excerpts, the search model processes the text of the visitor's question with every question, and in advance also the texts of the Knowledge Base. On the first preparation of a source or its full recalculation, this means its entire active content, not just the excerpts that later end up in a single answer. This model may come from a different provider than the model that writes answers.
- Optional AI knowledge clean-up. If the customer chooses it for a source, we send new or changed parts of the text in batches to a language model, which writes a description with keywords for them and assesses their quality. The model is set by Renly and may come from a different provider than the answer model. Editing a part of the text may repeat the clean-up. Without clean-up no language model is used, but the search model processes the text anyway.
- Auxiliary tasks. Shorter tasks around the conversation, such as a conversation summary for the customer's staff, recognising a place in a question, translating fixed answers into the visitor's language or an assistant quality test on real unanswered questions, may be done by a different model from the one that writes answers.
- Web search. If the package and the assistant settings allow it, the model may request a web search. Only the search query, which the model builds from the visitor's question, goes to the search engine.
Which models a particular assistant uses depends on its settings and on the customer's package; the customer can see them in the assistant settings. The model for AI knowledge clean-up is set by Renly for the whole platform.
Operators' internal notes in a conversation are never passed to language models. This does not apply to content the customer adds to the Knowledge Base or to the assistant's instructions — models process that as described above.
The customer should not add to the Knowledge Base or to the assistant's instructions any personal or sensitive data that the assistant does not need for the agreed purpose.
Who the data is passed to
So that the assistant can answer, we pass part of this data to providers who process it on our behalf. The contracting party, place of processing, transfer safeguards and date of the last review for each of them are given in the list of subprocessors.
| Provider | Where | What for and what it receives |
|---|---|---|
| OpenAI | USA and other countries | Answers, semantic search, AI knowledge clean-up and auxiliary tasks — depending on what the assistant has an OpenAI model set for. It receives the data described above for the given situation. |
| Anthropic | USA and other countries | Answers, AI knowledge clean-up and auxiliary tasks, if they are set to a Claude model. Anthropic does not provide a semantic search model. |
| Google (Gemini API) | USA and other countries | Answers, semantic search, AI knowledge clean-up and auxiliary tasks — depending on what the assistant has a Gemini model set for. |
| ElevenLabs | USA | Voice mode. It receives the voice recording for transcription and the answer text it is to read out. It is involved only when the visitor actually uses voice mode. |
| Exa | USA | Web search, if the package and the assistant settings allow it. It receives only the search query built from the visitor's question. |
| Sentry | EU (Germany) | Technical error reports. It receives technical data about the error; for an error in the administration also the identifier and email of the signed-in user. |
| OpenStreetMap | United Kingdom | Place lookup via the public Nominatim service. It receives only the name of the place or address being searched for, not the whole message. The service operator processes the data as an independent controller. |
Training and retention by AI providers
We use language models through paid business APIs, not through consumer applications. Under the contractual terms of OpenAI, Anthropic and Google (for paid Gemini API services), inputs and outputs from our calls are not used to train or improve their models without explicit consent.
However, providers may temporarily retain data for abuse detection, security and compliance with legal obligations: OpenAI generally for no more than 30 days, Anthropic generally up to 30 days and content flagged as a policy violation up to two years, Google 55 days. If abuse is suspected, the content may also be reviewed by authorised staff of the provider. We have not agreed a mode with no retention at all by the provider (Zero Data Retention).
Transfers outside the European Economic Area
The contracting parties for OpenAI and Anthropic are their Irish companies, but they also process data in the USA and other countries. Transfers are covered by the EU standard contractual clauses that form part of their data processing addendums. For the Gemini API, Google relies on the EU–US Data Privacy Framework (Google LLC is certified) or on standard contractual clauses. Details about the other providers are in the list of subprocessors.
09Electronic invoices
If a company activates delivery of electronic invoices in the Peppol network in the Finance module, we send and receive its documents through the certified delivery service provider Verteco digital services, s. r. o. The documents may contain personal data, for example the name of a sole trader or a contact person, e-mail and phone.
- For the content of the documents we are a processor of the company that issues or receives them, and Verteco is our sub-processor. For its own purposes under the Peppol network rules (for example reporting to the Financial Administration of the Slovak Republic) Verteco processes the data as an independent controller.
- During activation we process the details of the company and of the person acting on its behalf (name, role, e-mail and phone) and the time of their declarations and consent.
- Records of documents — who created, sent or received a document, when and through which access — are kept by us as a controller. They are required by the Peppol network rules and by our contract with the certified provider. The legal basis is our legitimate interest in demonstrating who used the network and in cooperating with public authorities.
The terms of the service are set out in the Special terms for electronic invoice delivery (in Slovak).
10Other providers
Besides the chat providers, we use these processors and other recipients — a payment institution and, for sign-in, the identity provider you choose:
| Provider | Where | What for and what it receives |
|---|---|---|
| Hetzner | Germany | Servers on which the platform and this website run. It stores all platform data. |
| Mailgun | EU | Sending emails — enquiry confirmations, replies, invitations and notifications. It receives the recipient's address and the content of the email. |
| Google (Analytics, Tag Manager) | EU and USA | Traffic measurement on this website, only with your consent. Receives visit data — pages viewed, traffic source, device and browser, and events such as sending a form; it uses the IP address only to determine the country and does not store it. For marketing cookies, Google acts as an independent controller for advertising. |
| Google (Firebase) | EU and USA | Mobile app: notification delivery (Cloud Messaging) and anonymous screen and action statistics (Analytics). Receives the device token and the notification text, and for statistics the screen or action name and technical device data, without names, e-mail addresses or the advertising identifier. |
| Verteco | EU (Germany) | Delivery of electronic invoices in the Peppol network, only for companies that activate it. It receives sent and received documents including the personal data in them. |
| GoPay | Czech Republic | Card payments and recurring payments. A payment institution; it processes the data needed to execute the payment as an independent controller. |
| Google, Microsoft, Apple | USA | Account sign-in, calendar connection and sending documents from your mailbox, only if you choose them. They verify your identity and pass us the data described in the Customer account section. They are not our processors — they process data about your account with them under their own terms. |
11Where the data is stored
The platform and its database run on servers in a data centre in Germany (Hetzner Online GmbH, Falkenstein). Outside the European Economic Area, data reaches only the providers listed above, in particular the AI providers, and only to the extent described for each of them.
12How the data is protected
- All communication is encrypted via HTTPS.
- We store administrators' passwords only as a hash, never in readable form.
- Login and recovery tokens are stored in the database only as a hash.
- Access credentials for integrations are encrypted in the database.
- The assistant's access to data is tied to the key of a specific customer and to the allowed domains on which the chat may run.
We provide a detailed technical description of our security measures to customers and partners on request; we do not publish it so as not to make attackers' work needlessly easier.
13How long we keep the data
- Message from the contact form — as long as necessary to handle the enquiry and the follow-up communication about it.
- Conversation with the assistant on this website — the identifier in the browser for 12 hours, the transcript according to the rules for conversation transcripts below.
- Your choice in the cookie banner (cookie
renly-consent) — 1 year. - Traffic measurement data (Google Analytics) — 14 months; the lifetime of individual cookies is shown in the list of cookies above.
- Customer account and billing details — for the duration of the contract and then according to statutory periods, in particular for accounting.
- Proof of consent to a recurring payment — for the duration of the recurring payment and at least 12 months after it ends.
- Conversation content — 180 days after the last activity in the conversation by default; the customer can choose 30, 90, 180, 365 or 730 days for an assistant. After this period we delete the message content, attachments and recordings; only statistics without content remain. We keep a conversation with an unresolved ticket until the ticket is closed.
- Answer sources in AI diagnostics (the question and the knowledge excerpts the assistant answered from) — 14 days.
- Voice recordings — according to the customer's settings, 30 days at most by default.
- Archive of Knowledge Base versions — 7 days.
- Connected Google and Apple calendars — a copy of the events and the access credentials for as long as the calendar is connected; we delete them immediately after disconnecting.
- Email sender via Google or Microsoft 365 — the sender address and the encrypted refresh token for as long as the mailbox is connected; we delete them immediately after disconnecting.
- Data about contacted organisations — 24 months from the last contact, unless the organisation becomes a customer; we delete it earlier on request. An address that refused further messages stays in the refusal list permanently.
- Electronic invoices — XML files in the Renly archive for as long as the delivery service lasts and, on request for an export, for another 90 days after it ends; records of documents for the term of the contract and five years after it ends.
The customer can request deletion of its assistant's conversations at any time. After the contract ends, we delete its data.
14Your rights
You have the right to access your data, to have it corrected, to have it erased, to restrict processing, to data portability and the right to object to processing. Write to us and we will handle it. If you are not satisfied with how it was handled, you can contact the Office for Personal Data Protection of the Slovak Republic.
Data deletion
- A business using Renly can request deletion of its account and all its data, including contacts and leads in the CRM, at any time.
- A person who submitted a form to a business using Renly (e.g. a Facebook or Instagram lead form) should first contact that business, as it is the controller of their data. They may also contact us and we will forward the request and help resolve it.
How to request: email support@renly.sk with the subject "Data deletion". Include the email or phone number we hold for you and, for leads, the name of the business whose form you submitted. We may verify your identity by replying to the same email address.
We delete contact details, form answers, CRM communication history and any other data linked to you. We process requests without undue delay and within 30 days at the latest. Data is removed from backups during regular rotation, within 30 days of deletion. Data we are legally required to keep (e.g. accounting records) is retained only for the statutory period.
15Changes
We may amend this document when the way we process data changes — for example when one of the providers is added or removed. We will notify customers of material changes in advance.
This version is effective from 1 December 2026.