Last updated · November 9, 2026
Privacy Policy
Here is what data we collect, what we use it for, who we share it with and how to ask us to delete it. Written to be understood in one read.
This is an English version for your convenience. If anything differs, the Spanish version applies.
Who is responsible for your data
Relevo is a service of Matías Castellani, domiciled in the City of Buenos Aires, Argentina. Any question about this policy goes to hola@relevo.cc and we answer it ourselves, not a form.
What data we collect
If you visit relevo.cc
We measure visits with Umami, a counter that runs on a server of ours. It uses no cookies, doesn't store your IP address and doesn't follow you to other sites. It tells us which pages are read and from which country, nothing else. There is no Google Analytics and no social media pixels.
If you write to us by WhatsApp or email
We keep what you send us: your name, your phone or email, and what you tell us about your business. We use it to reply to you and to keep track of the sales conversation.
If you request a demo
The Request your free demo form sends us the demo you want to see, what your business is and its address, your name, your email and your WhatsApp number. It is stored in Relevo's platform as a sales contact. We use it to message you with the invitation and to follow up on that conversation, the same as if you had written to us.
If you have a user account on the platform
At app.relevo.cc we store your name, your email, your encrypted password —we can't read it, not even us— and the record of your sign-ins: date, IP address and browser. That record exists for security: if an access ever needs to be reviewed, it is needed.
The data your company loads
Customers, products, orders, invoices, whatever the company loads to work. That data belongs to your company, not to us. It is confidential: the terms of service say what that means. We keep it to provide you the service and don't use it for anything else: we don't analyze it to sell, we don't cross it with another company's data and we don't train anything with it.
If you send us a support request
From the platform you can tell us something is wrong or suggest an improvement. We keep what you write, the screenshots you attach and, to be able to reproduce the problem, the screen you were on, the platform version and your browser. Screenshots are stored reduced in size and without the data the camera adds, such as date or location.
A screenshot may show data of your company or your customers. We treat it like the rest of your company's data: we use it only to resolve the request. The request is seen by whoever opened it, the owner and the administrators of your company, and us.
If your company uses an automation
Some automations are done by a robot of ours, on a Relevo machine, on behalf of your company. For example: downloading a month's sales and purchases from the tax portal and building the files your accounting system imports.
- The files it builds are stored in a Relevo Google Drive, in a folder for your company. We share it only with the people your company tells us to. The link is kept in the platform.
- The platform also keeps what each run did: the steps, the month's check and what it left for someone to decide. It is seen by the people in your company who have access to automations.
- If the robot needs a credential to enter another system, such as a tax key, that credential stays only on the machine where it runs. It doesn't pass through the platform or the Drive, and it doesn't appear in what the robot reports.
- This is data of your company and your customers. We treat it like the rest: we use it only to do the work you asked us for.
Sign in with Google
On the platform you can sign in with your Google account instead of a password. When you do:
- We ask Google for your email address, your name and whether that email is verified. Nothing more than that.
- We use the email to find your user account, which must already exist. Signing in with Google doesn't create anyone: at Relevo a user is created when a company invites you or when you set up your own. If the email doesn't match any active user, you don't get in and we store nothing.
- We don't read your Gmail, your Drive, your contacts or your calendar. We don't ask for those permissions, so we couldn't even if we wanted to.
- We never see your Google password. We don't store Google's tokens either: once sign-in is done, the session that stays open is ours, with a cookie of our own.
- You can cut it off whenever you want from myaccount.google.com/permissions, and keep signing in with your usual password.
Relevo's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Instagram and Facebook
A company can connect its Facebook page, and the Instagram linked to it, to the platform, to read and answer the messages it gets from there, and to publish. When it does:
- Whoever connects signs in with their Facebook and gives Relevo permission to read and answer the messages of the page and its Instagram. We store that page permission, encrypted. We never see their Facebook password and store nothing from their personal profile.
- If the company publishes from Relevo, it also gives Relevo permission to publish on its page and its Instagram the photos and videos it prepares on the platform. Meta downloads them from our server through a link that expires, and once published they are deleted on our side.
- If you write to that company on Instagram or Messenger, Relevo receives your message, your name and, on Instagram, your username, as Meta provides them. Photos you send are shown from Meta's address; we don't store them.
- Those messages are data of the company you wrote to, like everything else it loads: they stay in its customer's history and the people at that company see them. We use them for nothing else.
- Nobody writes to you first from Relevo: only a conversation you started gets answered, and within the window Meta sets. From your profile we read only your name and username.
- The company can cut it off whenever it wants, from the platform or from its page settings on Facebook. What already came in stays with the company until it deletes it or leaves Relevo.
A company can connect its WhatsApp Business number to the platform, to read and answer from there the messages it gets. When it does:
- Whoever connects signs in with their Facebook, in a Meta window, and gives Relevo permission to read and answer the messages of that number and to see the details of its WhatsApp Business account: the number and its display name. We store that permission, encrypted. We never see their Facebook password and store nothing from their personal profile.
- If you write to that company on WhatsApp, Relevo receives your message, your phone number and your profile name, as Meta provides them. With your number, the platform checks whether you are already a customer of that company, to add the conversation to your history.
- Photos, voice notes and files you send are requested from Meta when someone at the company opens them, and passed along as they are. We don't store them.
- Those messages are data of the company you wrote to, like everything else it loads: they stay in its customer's history and the people at that company see them. We use them for nothing else.
- Nobody writes to you first from Relevo: only a conversation you started gets answered, within the 24 hours WhatsApp sets. We don't send advertising.
- The company can cut it off whenever it wants, from the platform. What already came in stays with the company until it deletes it or leaves Relevo.
YouTube
A company can connect its YouTube channel to the platform to upload its videos from there. Relevo uses YouTube API Services for this, and by connecting the channel you agree to the YouTube Terms of Service. When the company connects it:
- Whoever connects signs in with their Google account and gives Relevo permission to upload videos to the channel and view the channel's data, nothing else: Relevo can't delete or change the videos already there. We store that permission encrypted, with the channel's name, ID and picture.
- The video and thumbnail the company prepares in Publishing stay on our server until they are published; then they are deleted on our side. The texts and the link to what was published stay with the company, like the rest of its data.
- For each published video, every six hours we read its views, likes and number of comments, to show them to the company. We don't read the comments or anything about the people who watch.
- The company can cut it off whenever it wants: from the platform, under Settings → YouTube, which also removes the permission at Google, or from the permissions page of its Google account. What YouTube does with the videos and with the people who watch them is governed by the Google Privacy Policy.
The cookies we use
There are five, all necessary for the platform to work. None is used for advertising or to track you outside the site.
- rv_sesion
- Keeps your session open after you sign in. Without it, you'd have to enter the password on every screen.
- rv_tema
- Remembers whether you chose light or dark mode.
- rv_google
- Lasts ten minutes and only exists during the round trip to Google. It verifies that the browser coming back is the same one that left.
- rv_meta
- The same, on the trip to Facebook when a company connects its page: it lasts ten minutes.
- rv_meta_elegir
- If whoever connects manages several pages, it keeps the Facebook permission encrypted while they pick one. It lasts ten minutes.
Where it lives
Everything runs on our own server at DigitalOcean. Every night we make a backup of each company, which the owner can download from the platform. Backups are kept for thirty days, and one per month for a year; after that they are deleted automatically. We also make backups of the whole server, at DigitalOcean and in a Google Drive account of ours. The files the automations build are also stored in that Google Drive account. The server is outside Argentina, so by using the service you accept that international transfer, which exists solely to be able to provide you the service.
Who we share it with
With nobody who isn't needed for this to work. The complete list of providers that may handle data:
- DigitalOcean — the server where everything runs.
- Cloudflare — domains and email forwarding.
- Brevo — sending emails: notifications and password recovery.
- Google — sign in with Google; YouTube, if the company connects its channel; and in Drive the backups and the files the automations build. And Gemini, its artificial intelligence: the platform's assistants and the dashboards that summarize the week send it what they need to answer, under the terms of its API for businesses, which don't let it train on that.
- Anthropic — when Relevo works on your company's data with its artificial intelligence assistant, for example to load your history or review a spreadsheet of yours. Under its commercial terms, which don't let it train on that.
- Mercado Pago — online store payments, when the company uses it.
- Meta — Instagram, Messenger and WhatsApp, when the company connects its page or its number: the messages it gets come in that way, and the ones it answers from the platform go out.
- The systems your company connects — Fudo, Faire, Wix, your mailbox: we read and write there with the authorization you give us, and each has its own terms. The emails you send to your customers go out through your own email provider.
- Your browser's notification service — Google, Apple or Mozilla, depending on which one you use: when you turn on notifications with Relevo closed, it only receives the text of the notification.
We don't sell data, we don't hand it over for advertising and we don't pass it to anyone else, except on request from a competent authority with the corresponding order.
How long we keep it
As long as you have an active user account and as long as your company keeps using the service. If the company leaves, the data remains available for ninety days so it can take it, and then it is deleted. Backups that still contain it are deleted automatically when their time comes, within the year, and meanwhile remain under the same confidentiality. What the law requires us to keep —invoices and accounting records— is kept for as long as the law says, even if the account is closed.
What you can ask of us
You can ask for access to your data, to have it corrected, updated or deleted. Write to hola@relevo.cc from your user's email address and that's it. Access requests are answered within ten calendar days; rectification or deletion requests, within five business days.
If you wrote on Instagram, Messenger or WhatsApp to a company that uses Relevo, your messages are that company's data: you can ask it or us to delete them, and we sort it out with the company. If you connected your page and want us to delete what Meta passed on to us, disconnect it from the platform (the permission is deleted right then) and write to us for the rest.
Under Argentine law (Law 25,326, section 14, subsection 3), the data subject may exercise the right of access free of charge at intervals of no less than six months, unless a legitimate interest is shown. The Agencia de Acceso a la Información Pública, as the supervisory authority under Law 25,326, has the power to handle complaints and claims from those whose rights are affected by non-compliance with personal data protection rules.
Minors
The service is for businesses and the people who work in them. It is not directed at anyone under 18 and we don't ask for or seek data from minors.
If this changes
The date at the top changes too. When the change is significant, we notify those who have a user account by email before it takes effect.
How to contact us
By email at hola@relevo.cc. A person answers.