Privacy policy
Last updated: 8 October 2026
Riplo replies to Instagram comments and direct messages automatically, using rules the account owner writes. This policy explains what personal data Riplo processes, why, who it is shared with, how long it is kept, and how to have it deleted. It covers riplo.co, the Riplo dashboard at app.riplo.co and the Instagram features of the service. The Persian-language site, riplo.ir, is run by the same team and follows the same practices.
The short version
- Riplo connects to Instagram only through Meta's official login. We never see or store your Instagram password.
- We use what Meta sends us only to run the features you switch on for your own account. We do not sell it, use it for advertising, or build profiles from it.
- Instagram access tokens are encrypted, and disconnecting an account deletes its token.
- You can ask us to delete your data at any time. The steps are on the data deletion page.
Who is responsible
Riplo ("Riplo", "we", "us") operates the service; contact details are at the end of this policy. Two groups of people have data passing through Riplo, and our role differs for each:
- Account holders are people who sign up for Riplo. For their account, billing and usage data, Riplo decides how the data is used.
- Contacts are people who comment on, or send a message to, an Instagram account connected to Riplo. For their comments and messages, the account holder decides what happens, because they run the Instagram account. Riplo processes that data on the account holder's behalf and only to provide the service.
What we process
Riplo does not collect Instagram passwords, and we do not receive full payment card numbers.
| Category | What it includes | Where it comes from |
|---|---|---|
| Account details | Name, email address (or mobile number for accounts made on riplo.ir), a salted hash of your password, language, and business name. If you sign in with Google, the identifier and verified email Google returns. | You |
| Instagram connection | The Instagram professional account's ID, username, profile picture, account type and follower count; the permissions you granted; token expiry and connection status; and the access token, which is stored encrypted. | Meta, when you approve the connection |
| Content and insights of your account | Details of your recent posts and reels (ID, caption, link, type, thumbnail, date, like and comment counts) and, where you granted the permission, performance figures such as reach, views, interactions and profile visits. Shown to you in the dashboard and used to let you target a rule at a specific post. | Meta |
| Comments and messages (contacts) | The text and time of a comment or direct message, comment and message IDs, the sender's Instagram-scoped ID, and their username and name when Meta provides them; links to attachments; and the replies sent, including messages you type in the Instagram app to someone who has already written to you. If you use the follow-before-reply feature, whether the person follows your account is checked once to decide which reply to send. | Meta, when someone comments or messages your account |
| Automation settings | Keywords, reply texts, buttons and multi-step flows, images, audio or video you attach to replies, and counts of how often each rule ran. | You |
| Leads and follow-ups (if you use them) | Answers submitted through forms you create, and follow-up sequences you set up. | You and your contacts |
| Billing | Plan, amount, payment reference and status from the payment provider, and a masked card reference the provider returns. | You and the payment provider |
| Support and security | Messages you send us; a log of account actions such as sign-in, connecting and disconnecting; a hash of your IP address and your browser's user-agent for each sign-in session; rate-limit counters; and logs of incoming Meta events and outgoing message jobs. | You, your browser, and our systems |
| Optional alerts | Your Telegram chat ID, if you link Telegram to receive alerts. | You |
Instagram and Meta permissions
Riplo asks for only the four permissions below. If you decline one, the features that need it are unavailable.
| Permission | What Riplo uses it for |
|---|---|
instagram_business_basic | Identify the connected account and show its profile and recent posts. |
instagram_business_manage_comments | Read comments on your posts and reels and reply to them. |
instagram_business_manage_messages | Receive direct messages sent to your account and send the replies you configured, including private replies to comments. |
instagram_business_manage_insights | Show your account and post performance in the dashboard. |
Data we receive from Meta is used only to provide the features you asked for in your own account. In particular:
- We do not sell it or license it, and we do not share it with data brokers or advertisers.
- We do not use it to build advertising audiences or profiles of people, or to make decisions about credit, employment, insurance or similar matters.
- We do not send message or comment content to third-party AI or analytics services.
- Automated messages are sent only in response to something the person did, such as commenting or messaging, and within the windows and rules Meta sets for messaging. You write the message text and are responsible for it.
Riplo follows the Meta Platform Terms and Developer Policies. Riplo is not affiliated with or endorsed by Meta or Instagram.
Google and YouTube
Riplo uses Google services in two optional ways: signing in with Google, and publishing videos to your YouTube channel. Neither is needed to use Riplo, and each asks only for the access below.
| Google permission | When it is asked for | What Riplo uses it for |
|---|---|---|
openid, email, profile | Sign in with Google | Identify you and show your name and email address in your account. |
https://www.googleapis.com/auth/youtube.upload, openid, email | Connecting a YouTube channel | Upload a video you choose to that channel, with the title, description and privacy setting you entered, now or at the time you scheduled; show you which Google account is connected. |
What we access and keep. For YouTube, Riplo stores the refresh token Google returns (encrypted) and the email of the connected Google account, so we can show you which account is connected. The video file waits on our servers only until it is published: at once, or at the time you scheduled (at most 180 days ahead). It is deleted as soon as YouTube has received it. If an upload fails it is kept for 3 days so you can try again; an upload you never finished is deleted after 24 hours, and one you cancel is deleted at once. We keep a record of each upload (title, description, visibility, schedule, the video's YouTube ID and link, status) so you can see it in your dashboard. Riplo cannot read, change or delete the videos, comments, playlists or settings already on your channel: the only YouTube permission it asks for is to upload.
How we use it. Only to provide the feature you asked for: uploading the video you selected, at once or at the time you scheduled. We do not use Google user data for advertising, we do not sell it, we do not use it to train artificial intelligence or machine-learning models, and we do not transfer it to anyone except as needed to provide the feature (our server host), to comply with the law, or with your explicit consent. No one at Riplo reads it unless you ask us to for support, it is needed for security, or the law requires it.
Limited Use. Riplo'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.
YouTube. Riplo uses YouTube API Services. By connecting a YouTube channel you agree to be bound by the YouTube Terms of Service. Google's use of your data is described in the Google Privacy Policy.
Removing access and deleting data. You can disconnect YouTube in your Riplo dashboard, or remove Riplo's access at any time from your Google Account permissions page (also reachable at security.google.com/settings/security/permissions). When you disconnect, Riplo revokes the token at Google and deletes it at once, and deletes any video still waiting to be published; the upload records are deleted when you ask us or close your account (see data deletion). Riplo is not affiliated with or endorsed by Google or YouTube.
How we use it
- To provide the service: match comments and messages to your rules, send replies, show your inbox and analytics, and keep the connection working.
- To keep it safe: prevent duplicate or abusive sending, enforce plan limits, detect misuse and secure accounts.
- To bill you and keep the records the law requires.
- To support you: answer your questions and fix problems.
Where the law asks for a legal basis, we rely on: performing our contract with you (running your account and automations); our legitimate interests in securing and improving a reliable service; your consent, which you give and can withdraw by connecting or disconnecting Instagram; and legal obligations such as tax records.
Who we share it with
We share data only with the service providers below, and only as needed for the purpose shown. Some apply only if you use the related feature.
| Provider | Purpose | Data involved |
|---|---|---|
| Meta Platforms (Instagram API) | Log you in, and read and send what you ask for | Access token, comment and message content, IDs |
| Cloudflare | DNS, network security, and delivery of the website and parts of the platform | Requests, IP addresses, technical logs |
| Our server host (Germany) | Runs the dashboard and the database | All data described above |
| Resend | Sends verification and account emails | Your email address and the code |
| Payment provider | Processes payments; card details are entered on the provider's page, never on Riplo | Plan, amount, payment reference |
| Google (optional) | Only if you choose Sign in with Google | Name, email address |
| Google / YouTube (optional) | Only if you connect a YouTube channel: uploading the videos you choose | Access token, the video and its title, description and privacy setting, the connected Google account's email |
| Telegram (optional) | Only if you link Telegram alerts | Chat ID and alert text |
| SMS provider (optional) | Only for accounts created with a mobile number, mainly on riplo.ir | Mobile number and the code |
We may also disclose data when the law requires it, to protect the security of the service or its users, or as part of a merger or sale of the business, in which case this policy continues to apply to the data.
Where data is processed
The dashboard and database run on our servers in Germany. Providers such as Cloudflare, Meta and Resend may process data in other countries, including the United States. Where data protection law requires safeguards for such transfers, we rely on the mechanisms those providers make available, such as standard contractual clauses.
Security
- Instagram access tokens are encrypted before they are stored (AES-GCM) and are used only on our servers; they are never sent to your browser or shown on any page.
- Passwords are stored as salted hashes, and sign-in sessions are stored as hashes.
- Traffic is encrypted with HTTPS, and incoming Meta events are verified with a signature before they are processed.
- Requests are rate-limited, and account actions are logged.
No online service can promise absolute security. If a breach affects your data, we will tell the people affected, and the authorities where the law requires it.
How long we keep it
| Data | How long |
|---|---|
| Account, Instagram connection, automations, contacts, and conversations with their messages | While your account is open, so your inbox and history stay available. We delete them when you ask (see the data deletion page). |
| Instagram access token | Removed when you disconnect the account. Removing Riplo in your Instagram settings also cuts our access at once. |
| YouTube access token | Removed when you disconnect YouTube. Removing Riplo in your Google Account permissions also cuts our access at once. |
| Video files you send to YouTube | Until published (at once, or at the scheduled time, at most 180 days ahead), then deleted. A failed upload: 3 days, so you can retry. An unfinished upload: 24 hours. Cancelled: deleted at once. |
| YouTube account email and upload records | While your account is open, or until you ask us to delete them. |
| Logs of incoming Meta events | Removed 30 days after they are processed. |
| Records of sent message jobs | Removed 30 days after sending. |
| Sign-in sessions, verification codes, rate-limit counters | Removed automatically when they expire, within days. |
| Payment records | As long as tax and accounting law requires. |
| Backups | Deleted data can remain in backups for a limited time until they are overwritten. We do not restore deleted data except to recover from a failure. |
Your rights
Depending on where you live, you may have the right to:
- get a copy of the data we hold about you;
- have inaccurate data corrected;
- have your data deleted;
- receive your data in a portable format;
- object to or restrict some processing;
- withdraw consent, for example by disconnecting Instagram or revoking Riplo in your Instagram settings; and
- complain to your data protection authority.
To use any of these, write to hello@riplo.co. We reply within 30 days. If you are a contact, meaning you commented on or messaged a business that uses Riplo, you can write to us too: tell us your Instagram username and we will help, or pass your request to the business that controls the account.
Cookies and browser storage
riplo.co sets no cookies and has no analytics or advertising trackers. Our hosting provider keeps standard server logs for security. The dashboard stores a sign-in token and your language preference in your browser's local storage so you stay signed in; it is not used for advertising.
Children
Riplo is for businesses and is not directed to anyone under 18. We do not knowingly collect data from children. If you think a child has given us data, write to us and we will delete it.
Changes to this policy
When we change this policy, we publish the new version here with a new date. If a change is significant, we tell account holders before it takes effect.
Contact
Questions, requests or security reports: hello@riplo.co. We answer in English here and in Persian at riplo.ir.