Privacy Policy

What we collect

We collect the email address you sign up with, the App Store Connect and Google Play credentials you connect, the reviews we fetch on your behalf — including the reviewer name the store publishes — and the replies you approve. When you allow notifications, we also store your device's push token with its platform, app version and language, so a notification reaches the right device in the right language.

We also collect usage data: which screens you open and which actions you take in the mobile app, with your plan and reply allowance attached. It is counted per device and is not linked to your account. You can turn it off at any time (see Usage data below).

When something breaks, the app sends a crash or error report. Those are tied to your account by its numeric ID, so we can follow up on a problem you report, and never by your email address.

When you sign in, we record the IP address and the app or browser the request came from, so that a sign-in you did not make can be looked into if you ever ask us to. It is recorded once per sign-in, not while you keep using the app, and is deleted within 60 days.

How we store credentials

All store credentials (App Store private keys, Google service-account JSON) are encrypted at rest with Active Record Encryption (AES-256-GCM), under a key held outside the database. They are decrypted only in memory during sync runs and reply posts, and are filtered out of our logs.

Who processes your data

We do not sell your data, and we do not share it for advertising. We do use a small number of service providers to run Replylo, and each one receives only what it needs to do its job:

• OpenAI — the text of each review, to generate a draft reply and the weekly summary.
• RevenueCat — your subscription status and purchase history, identified by your account ID.
• Sentry — crash and error reports: the error itself, where in the app it happened, your account ID, and your app version and device model.
• PostHog — anonymous usage events: which screens and actions, your plan, and roughly how many apps you have connected, under a random ID for the device that is not linked to your account. PostHog derives an approximate location (country and city) from the connection's IP address and does not keep the address itself. Nothing is sent to PostHog while Share usage data is off.
• Google (Firebase Cloud Messaging) — your device's push notification token and the message to deliver, so we can tell you when a draft is ready.

What we deliberately don't send

Reviews, the replies you write, and your reply style settings are customer content. They are never sent to our analytics or error-reporting providers. Concretely: our analytics events carry counts and settings only — no account ID, no review text, no reply text, no email addresses. Error reports have email addresses masked out of their messages, and carry no screenshots, request bodies, cookies or IP addresses. Session recording is switched off, and we do not send your device's push token to our analytics provider.

Why we use your data

Where the EU or UK General Data Protection Regulation applies, these are our legal bases:

• To provide Replylo (performance of our contract with you): your account, the store credentials you connect, fetching reviews, drafting, translating and posting replies, notifications, and your subscription.
• Our legitimate interests: crash and error reports, to keep the app working; the IP address and client recorded with each sign-in, to protect accounts from stolen sessions; and anonymous usage data, to understand which features are used. You can object to any of these; for usage data, the switch above does it at once.

Your rights

You can ask us for a copy of your data, to correct it, to delete it, to restrict how we use it, to receive it in a portable format, or object to how we use it. Email [email protected] from the address on your account and we will answer within one month. You can also complain to the data protection authority where you live.

Where your data is processed

Our own server is in the EU, and our usage analytics (PostHog) and error reporting (Sentry) are both configured to their European regions, so that data stays in the EU. Neither of them stores the IP address a request came from. Our other providers — OpenAI, RevenueCat and Google — process data under their own terms and locations, which their privacy policies describe.

Tracking and advertising

Replylo does not track you across other companies' apps or websites, and we do not use advertising identifiers. Nothing we collect is used for advertising or sold to data brokers.

Deleting your data

You can delete your account at any time from your account settings. Deletion is immediate: your apps, credentials, reviews and replies are deleted from our database the moment you confirm, and cannot be restored. Usage data is not linked to your account, so there is nothing in it to find and erase. To have your crash and error reports erased from our error-reporting provider as well, email us and we will request their deletion.

Who we are

Replylo is made and run by Mustafa Yılmaz, an independent developer based in Türkiye, who is the data controller for everything described here. Questions, or any of the rights above: [email protected].