Last updated November 19, 2026

Privacy Policy

How Replivy handles account, campaign and audience data, including comments and tracked links.

Who handles your information

Akhmed Dadakaev, Individual Entrepreneur, operates Replivy. Georgian registration number 302376630, registered by the LEPL National Agency of Public Registry on August 14, 2026. Registered address: Mikheil Tsinamdzgvrishvili Street N 52, Attic, Tbilisi, Georgia. For privacy questions, write to office@dadakaev.com.

Our role and the creator’s role

Replivy determines how it handles sign-in, workspace administration, support and service security. The creator or organisation running a campaign chooses its audience, triggers, messages, links and use of reports. Replivy processes audience data to carry out those settings. If you received a reply, you can contact the creator about the campaign or contact us for help identifying the workspace.

Accounts, teams and sign-in

We store your email, user ID, verification status, account timestamps and, where supplied, your name and profile image. We store password hashes for password sign-in, verification records with expiry times, and session tokens and expiry dates. Workspace records include names, ownership, members, roles, invitation emails, invitation status and monthly message counts. You do not need to enter payment details to use the Free plan.

Subscriptions and payments

If you choose a paid plan, Replivy stores a subscription record linked to your user ID, the payment provider and provider subscription ID, plan, status, paid-access end date, last payment identifier, checkout approval link and verification timestamps. We retain selected webhook metadata, including event IDs, event types, plan and subscription identifiers, processing outcome and event timestamps, to verify subscription changes and prevent duplicate processing. Internal free plan grants are recorded separately from paid subscriptions.

You enter payment details with PayPal, not Replivy. We check subscription and payment information with PayPal to provide paid access, handle renewals, cancellations and refunds, and investigate payment issues. Replivy does not store raw PayPal webhook payloads, payer contact details or card information in its billing records. PayPal handles payment details under its Privacy Statement.

Your Replivy account has a separate random account token reserved for associating future app purchases with the same login. Apple in-app purchases are not currently enabled. This token is not a payment credential and does not create a subscription.

Instagram campaigns and inbox

For monthly contact limits, we retain the workspace owner, UTC calendar month, a hash derived from the connected Instagram account and recipient identifiers, and delivery-confirmation or pending-reservation metadata. Several campaign messages to the same recipient on that Instagram account count once. Hashes are pseudonymous identifiers, not anonymous data. These usage records survive campaign or connection removal to prevent resetting the monthly allowance and are removed with the account.

When you connect Instagram, we store the account ID, username, available name, connection status and encrypted access token. For campaigns we store selected posts or reels, keywords, reply text, links, and follow-up or public reply settings. Meta supplies events and comments. Delivery records can include the commenter’s Instagram ID and available name, comment text and ID, matching keyword, status, attempts, timestamps and error details. We use identifiers to prevent duplicate replies. The dashboard can store dated follower counts. Opening the inbox also retrieves available conversations and participant profiles from Meta, with short-lived server caches.

Campaign images, audio, video and reminders

When you save a campaign with an image, recording or video, Replivy stores the selected file with that campaign. Instagram retrieves it through a time-limited link to deliver it in the chat. Replacing or removing the file, or deleting the campaign, removes the stored active copy. Delivered messages and backup copies follow the retention rules below. To stop reminders after a reply, reaction or button tap, Replivy temporarily stores the interaction time against the account and recipient. Reminder scheduling and duplicate prevention use a 24-hour window.

What happens when you click a tracked link

Before redirecting you, Replivy records the time, tracked link, campaign, workspace and connected creator account. Where available, the click record contains a salted hash derived from the IP address, the browser’s user-agent string and the referring URL. The click record has no dedicated field for the visitor’s Instagram ID. A hash can still distinguish visits and is not anonymous. The destination website receives the visit and applies its own privacy practices.

Who can see campaign results

Authorised workspace members can access campaign information according to their role. Anyone with an enabled report link can view the shared report, including the workspace name, Instagram username, campaign details, keywords, destination hosts and aggregate delivery and click results. Take care where you share that link.

Optional Telegram campaigns

When a workspace connects a Telegram bot, we store its ID, username, encrypted bot token and webhook configuration. Campaigns store channel details, messages and reward links. We process bot commands and button presses, check channel membership through Telegram, and store campaign-specific Telegram user IDs, last interaction and delivery times, and update IDs used to prevent duplicate processing. These records do not automatically associate Telegram subscribers with Instagram commenters.

Security, diagnostics and browser storage

Replivy stores incoming Instagram webhook payloads and their processing status. These events may include message content or platform identifiers. Delivery queues temporarily hold job data. Diagnostics can include error messages, request metadata and short excerpts of rejected requests. We use this information to deliver messages, prevent abuse and investigate failures. Sign-in uses cookies. A language preference cookie remembers your choice for up to a year. If you import campaigns, your browser can temporarily store pending import rows and the selected account.

Service providers and international processing

Replivy is operated from Georgia. Hostinger hosts our production application, database and task queue in Frankfurt, Germany.

Resend handles sign-in and verification email. It stores message content and delivery logs in the United States, including when email is sent from a European sending region. Resend describes its international transfer safeguards in its GDPR information.

Meta handles Instagram authorisation, events and messaging. Its international processing can include transfers to the United States. See the Meta Privacy Policy. If a workspace connects Telegram, Telegram receives the requests needed to check membership and send messages. For users who signed up from the UK or EEA, Telegram identifies the Netherlands as its data storage location in its Privacy Policy. Contact us for further information about transfer safeguards applicable to your data.

Purposes and legal bases

Where the GDPR applies and we act as controller, we process information necessary to provide your requested account and workspace under Article 6(1)(b). We rely on legitimate interests in protecting accounts, preventing duplicate or abusive activity, and diagnosing failures under Article 6(1)(f), subject to your rights. Where the law requires us to retain or disclose information, the basis is Article 6(1)(c). The campaign operator is responsible for the legal basis and notices for its own messaging and audience measurements.

How long records are kept

Account and workspace records support the active account. Campaign records, delivery logs and click history are retained with the campaign until deleted. Sign-in credentials have different lifetimes. For example, mobile email verification codes expire after ten minutes. Expiry prevents use and does not mean every associated record is immediately erased. Webhook payloads, deduplication records and diagnostics do not all have an automatic age-based deletion deadline. Some are stored separately from the campaign and may remain after it is removed.

Billing records and payment-event metadata are retained to manage the subscription, resolve payment issues and meet applicable record-keeping obligations. Cancelling renewal does not immediately delete the billing history. Contact us with a deletion or retention question; any records that must be retained are handled separately from active account access.

Hostinger backs up our production server weekly and stores the backups separately in France. It keeps the two most recent weekly recovery points and automatically replaces the oldest as new backups are created. Data deleted from the active service can remain in an earlier backup until that recovery point is replaced.

Disconnecting, deleting and exercising your rights

Disconnecting Instagram removes the selected connection, its campaigns and associated campaign logs and clicks. Deleting a Telegram campaign removes its subscriber records. Disconnecting the bot also removes its campaigns. Messages already delivered can remain on the receiving platform. For workspace or account deletion, see the data deletion instructions.

How to contact us, including without an account

Email office@dadakaev.com. Workspace users can give the workspace name. If you commented or clicked a link, you can write without a Replivy login. Identify the creator, post or link and approximate date. For Telegram, identify the bot and channel. We may need to verify the request or involve the campaign operator. Please do not send passwords or access tokens. Where applicable, you may request access, correction, erasure, restriction or portability, object to processing based on legitimate interests, and complain to your local data protection authority.