Privacy Policy

01What we collect

We collect the minimum needed to run the app and send notifications. Nothing is sold or used for advertising.

• Resend access tokenCreated at OAuth sign-in. It stays on your device only, in the Keychain (iOS) or Keystore (Android). It is never sent to the relay or any server of ours.
• Local cacheEmail, domain and metric lists kept on the device to reduce API calls. Deleted when you sign out.
• Relay dataDevice push token, language, team and webhook IDs, alert preferences (events, bounce threshold, do not disturb, time zone) and the webhook signing secret.
• re: Pro statusPurchase transaction and product IDs, and the trial start date, to unlock Pro.
• Product analyticsApp usage events (for example, screen opened, filter changed or alert enabled), with a random device identifier and a hashed team code (it cannot be turned back into the team id). Screens are recorded by route template, without ids. Events go to PostHog and Google Analytics for Firebase, with no advertising identifier (IDFA/AAID) and no ad signals. They never include email content, addresses, subjects, domains or tokens. You can turn this off in Settings > Privacy > Share usage data.
• Crash reportsApp version, device model, OS and the error, without email addresses or content.

02What we don’t collect

Your emails, threads and contacts are read by the app straight from the Resend API and shown on your device. They do not pass through our servers.

• Email contentSubjects, bodies, attachments and recipient addresses are not stored by us.
• API keysre: never asks for or stores API keys. Sign-in uses Resend’s official OAuth.
• TrackingNo advertising SDKs, no cross-app or cross-site tracking, no location.

03Notification relay

Resend doesn’t send push notifications. So the app creates a webhook in your account pointing to relay.tryre.dev and gives the relay only that webhook’s ID and signing secret. The relay verifies each event’s signature, applies your rules (threshold, do not disturb, grouping), builds the notification and delivers it through Expo Push, which uses Apple (APNs) and Google (FCM).

The relay never receives or stores your Resend token and does not store email content. An event is kept only until its notification goes out (or is retried, if sending fails) and is then discarded. The notification carries only what it needs, such as domain, count and subject. Technical logs are kept up to 7 days and don’t contain event bodies. When you leave a team in the app, that team’s webhook and relay data are deleted.

04Third-party services

We use few vendors, each only for what is described:

• ResendOAuth sign-in and the whole API. Your account data follows Resend’s own policy.
• Apple, Google and ExpoPush delivery (APNs, FCM, Expo Push) and purchase processing on the App Store and Google Play.
• PostHogThe product analytics described above, with no email data.
• Google (Firebase Analytics)The same product analytics, with no email data and no advertising identifier.
• SentryCrash reports.
• Vercel and RailwayHosting for this website (Vercel) and the relay (Railway).
• fdbk.onlineFeedback and bug widget on this site and in the app. What you write there, and your email if you provide it, is stored by fdbk.online.
• Google FontsThis site’s fonts. Your browser downloads them from Google, which receives your IP address.

05Purchases

re: Pro is sold through the App Store and Google Play. Apple or Google processes the payment. We only receive the purchase confirmation (transaction and product IDs), validated by the relay with the store, to unlock Pro. We have no access to card data.

06Your rights (LGPD and GDPR)

We process relay data to provide the service you asked for, and analytics and crash reports under our legitimate interest in keeping the app working and improving it, without email data.

• Access and portabilityAsk for a copy of the relay data tied to your device.
• Correction and deletionIn More, Alerts, tap Erase my relay data. Deletion is immediate. Uninstalling the app removes the token and local cache.
• Response timeEmail requests are answered within 15 days.

07Contact

Questions about this policy or requests about your data: [EMAIL DE CONTATO]. Controller: [NOME COMPLETO], an individual. Data protection officer: [NOME DO ENCARREGADO].

If this policy changes materially, we will tell you in the app before the change takes effect.