Renvizo
Privacy Policy
Effective date: March 3, 2026 | Version 2.0 | Last updated: March 3, 2026
1. Introduction
Renvizo ("we," "us," or "our") operates the Renvizo mobile application (the "App"), available on iOS and Android, and the website at www.renvizo.com (the "Website"). Renvizo is a business analytics and messaging platform designed for content creators and small business owners.
This Privacy Policy explains what personal data we collect, how we use it, who we share it with, and what rights you have. It applies to all users of the App and Website, as well as third parties whose data may be processed through connected platforms (such as people who send direct messages to our users).
By using Renvizo, you agree to the practices described in this policy. If you do not agree, please do not use the App or Website.
2. Who We Are
Renvizo is operated as a sole proprietorship. For the purposes of applicable data protection laws (including the EU General Data Protection Regulation, "GDPR"), Renvizo is the data controller for the personal data processed through the App and Website.
Contact information:
3. Data We Collect
3.1 Account Data
When you create a Renvizo account, we collect:
- Email address
- Display name
- Authentication credentials (managed by Firebase Authentication; we do not store passwords directly)
3.2 Connected Platform Data
When you connect a third-party platform (Instagram, LinkedIn, TikTok, YouTube, Stripe, Kit, or Mailchimp), we collect and store:
- OAuth tokens: Access tokens and refresh tokens required to communicate with the platform's API on your behalf. These are encrypted using AES-256-GCM and stored server-side. Your device never receives or stores these tokens.
- Platform account identifiers: Your username, account ID, and display name on the connected platform.
- Analytics data: Aggregate engagement metrics (follower counts, post impressions, likes, comments, video views, revenue figures, email campaign statistics). This data is stored server-side in our database to power your analytics dashboard.
3.3 Instagram Direct Message Data
Privacy-first architecture: Message content and contact personal information from Instagram Direct Messages are stored exclusively on your device. They are never stored on our servers.
When you use the Inbox feature, the following data flows apply:
- Message content (text): Fetched from Instagram's API by our server, transmitted to your device, and stored in on-device local storage only. Our server acts as a pass-through and does not retain message content.
- Contact names, handles, and profile pictures: Retrieved from Instagram's API and stored on your device only. These are never written to or stored on our servers.
- Server-side conversation metadata (minimal): Only opaque thread identifiers (non-reversible IDs), timestamps, and platform identifiers are stored on our servers. This minimal metadata enables real-time notification delivery. No names, handles, profile pictures, or message content are stored server-side.
3.4 Email Marketing Data
When you connect Kit (ConvertKit) or Mailchimp, we collect aggregate campaign statistics only (send counts, open rates, click rates, revenue attribution). We do not collect, store, or process individual subscriber names, email addresses, or any subscriber-level personal data.
3.5 Device and Usage Data
- Crash reports: Collected via Firebase Crashlytics to diagnose and fix app issues. These may include device model, operating system version, and crash stack traces. No personal message content is included in crash reports.
- Push notification tokens: Firebase Cloud Messaging (FCM) device tokens for delivering push notifications.
4. How We Use Your Data
| Purpose |
Data Used |
Legal Basis (GDPR) |
| Provide the analytics dashboard |
Platform analytics, account identifiers |
Contract performance (Art. 6(1)(b)) |
| Deliver the Inbox feature |
Opaque thread identifiers, timestamps (server-side); message content and contact info (on-device only) |
Contract performance (Art. 6(1)(b)) |
| Send push notifications |
FCM token, sender name only (no message content) |
Legitimate interest (Art. 6(1)(f)) |
| AI-powered business insights |
Aggregated analytics metadata only (stage, tone, count); no message text or PII |
Contract performance (Art. 6(1)(b)) |
| Authenticate your account |
Email, Firebase Auth credentials |
Contract performance (Art. 6(1)(b)) |
| Diagnose and fix bugs |
Crash reports, device information |
Legitimate interest (Art. 6(1)(f)) |
| Communicate with platform APIs |
Encrypted OAuth tokens |
Contract performance (Art. 6(1)(b)) |
5. AI Features
Renvizo includes AI-powered features (Business Advisor insights, smart reply suggestions, tone adjustment) powered by Anthropic's Claude API. Our AI features are designed with a strict privacy-first approach:
5.1 Business Advisor & Smart Reply
- Zero message text transmitted: The smart reply feature sends only metadata to the AI service — specifically the conversation stage, desired tone, and message count. No direct message text from Instagram or any other connected platform is transmitted to the AI service.
- PII guard: An automated allowlist-based guard rejects any payload containing personal data (names, email addresses, phone numbers, account handles) before it leaves the device. This is enforced at the code level, not by policy alone.
5.2 Tone Adjustment (Rewrite with Tone)
- The tone adjustment feature sends only the creator's own drafted text (the text you write) to the AI service for rephrasing. It does not send any data received from Meta's API or any other platform API.
5.3 AI Data Handling
- AI-generated outputs (insights, suggested replies) are not used to train AI models. We use Anthropic's zero-retention API configuration.
- Only aggregated, k-anonymized analytics data is used for business insights. Individual user data is never exposed to the AI model.
6. Who We Share Data With
We do not sell, rent, or trade your personal data. We share data only with the following categories of service providers, solely for the purposes described in this policy:
| Provider |
Purpose |
Data Shared |
| Google (Firebase) |
Authentication, database, cloud functions, crash reporting, push notifications |
Account data, analytics data, opaque thread identifiers and timestamps, FCM tokens, crash reports |
| Anthropic (Claude API) |
AI-powered insights and tone adjustment |
Aggregated analytics metadata (stage, tone, count) only; creator's own draft text for tone adjustment only. Zero message content from connected platforms. |
| Meta (Facebook/Instagram API) |
Retrieve analytics and messages on your behalf |
OAuth credentials (server-to-server only) |
| LinkedIn, TikTok, YouTube, Stripe, Kit, Mailchimp APIs |
Retrieve analytics data on your behalf |
OAuth credentials (server-to-server only) |
All service providers are bound by data processing agreements. We do not share data with advertisers, data brokers, or any other third parties.
6.1 Push Notifications
Push notifications are delivered via Firebase Cloud Messaging (Google LLC). Notification payloads contain the sender's name only — no message content is included in push notifications. Notifications are ephemeral with a maximum time-to-live of 24 hours, after which undelivered notifications are automatically discarded by Google.
7. Data Retention
| Data Type |
Retention Period |
| Account data |
Until you delete your account |
| Analytics data (active platforms) |
Retained while the platform is connected |
| Analytics data (disconnected platforms) |
Archived for up to 12 months, then automatically deleted. You may choose immediate deletion at the time of disconnection. |
| OAuth tokens |
Deleted immediately when you disconnect a platform |
| On-device message content and contact info |
Stored locally until you delete the app or clear app data |
| Server-side conversation metadata (opaque IDs and timestamps) |
Deleted when you disconnect the messaging platform, delete your account, or when triggered by Meta's automated data deletion callback |
| Push notification payloads |
Ephemeral; maximum 24-hour TTL, not stored after delivery |
| Crash reports |
90 days (Firebase Crashlytics default) |
8. Data Security
We implement the following security measures to protect your data:
- Encryption at rest: OAuth tokens are encrypted with AES-256-GCM before storage. On-device messages are stored in an encrypted SQLite database.
- Encryption in transit: All data transmitted between the App, our servers, and third-party APIs is encrypted using TLS 1.2 or higher.
- Token isolation: OAuth access tokens and refresh tokens are never transmitted to or stored on your device. All API communication with connected platforms occurs server-side.
- PII guard: An automated allowlist-based system prevents personal identifiers from being sent to AI services. This guard operates at the code level and rejects non-conforming payloads before transmission.
- Access control: Server-side operations are authenticated using Firebase Authentication. Each user can only access their own data.
- On-device isolation: Contact names, handles, profile pictures, message content, and message previews are stored exclusively on the user's device and are never transmitted to or stored on our servers.
9. Your Rights
Under the GDPR and other applicable data protection laws, you have the following rights:
- Access (Art. 15): Request a copy of all personal data we hold about you.
- Rectification (Art. 16): Request correction of inaccurate personal data.
- Erasure (Art. 17): Request deletion of your personal data ("right to be forgotten").
- Data portability (Art. 20): Request your data in a structured, machine-readable format.
- Restriction (Art. 18): Request that we restrict processing of your data in certain circumstances.
- Objection (Art. 21): Object to processing based on legitimate interest.
- Withdraw consent: Where processing is based on consent, you may withdraw it at any time.
To exercise any of these rights, contact us at privacy@renvizo.com. We will respond within 30 days.
You also have the right to lodge a complaint with your local data protection supervisory authority.
9.1 Data Export
You can request a full export of your personal data through the App (Settings > Privacy > Export My Data) or by contacting us. The export includes all analytics data, conversation metadata, and account information. Archived data from disconnected platforms is included and clearly labelled.
9.2 Data Deletion
You can delete your data in the following ways:
- Per-platform: Disconnect a platform in Settings to delete or archive its analytics data and revoke tokens.
- Full account deletion: Contact us at privacy@renvizo.com to delete your entire account and all associated data.
- Automated Meta data deletion: When you remove Renvizo from your Facebook Settings (Settings > Business Integrations), Meta sends an automated deletion request to our server. We immediately delete all server-side data associated with your Meta account (thread metadata, contact insights) and return a confirmation code. You can check the status of your deletion request at any time. On-device data is deleted when you uninstall the app or clear app data.
10. Information for Non-Users
If you have sent a direct message to a Renvizo user's Instagram account, the following applies to you:
- Your message content is retrieved from Instagram's API and delivered to the Renvizo user's device, where it is stored locally. Your message content is not stored on our servers.
- Your name, username, and profile picture are stored on the Renvizo user's device only. These are never stored on our servers. Our servers store only opaque identifiers (non-reversible IDs) and timestamps — not your name, username, or profile picture.
- Your data is not shared with any AI service. Smart reply features do not transmit any of your message content.
- Your data is processed under the legitimate interest legal basis (GDPR Art. 6(1)(f)) — the Renvizo user has a legitimate interest in receiving and managing messages sent to their business account.
- You have the right to request access to, correction of, or deletion of any data we hold about you. Contact us at privacy@renvizo.com with your request.
11. Push Notifications
When you receive a new message, we may send a push notification to your device via Firebase Cloud Messaging (Google LLC). Push notifications contain the sender's name only — no message content or preview text is included. Push notification payloads have a maximum time-to-live of 24 hours and are not stored by Renvizo or Google after delivery or expiration.
You can disable notifications through the App's settings or through your device's notification settings.
12. Meta Platform Terms Compliance
Renvizo accesses Instagram data through Meta's official APIs and complies with the Meta Platform Terms and Meta Developer Policies. Specifically:
- No third-party data sharing: Data obtained from Meta's APIs (including Instagram DM content, contact information, and analytics) is not shared with any third party. It is used solely to provide Renvizo's features to the authenticated user.
- No surveillance or profiling: Data from Meta's APIs is not used for surveillance, advertising profiling, data brokering, or any purpose prohibited by Meta's Platform Terms.
- On-device storage only for personal data: Message content, contact names, usernames, and profile pictures obtained from Meta's APIs are stored exclusively on the user's device. They are never stored on our servers.
- Automated data deletion: When a user removes Renvizo from their Facebook Business Integrations, Meta sends a data deletion callback to our server. We automatically delete all server-side data associated with that user's Meta account and return a confirmation code with a status URL. Users can verify deletion was completed.
- AI isolation: No data obtained from Meta's APIs is sent to AI services. The smart reply feature transmits only metadata (conversation stage, tone, message count) — zero message content.
13. International Data Transfers
Our servers and service providers (Google, Anthropic) are located in the United States. If you are located in the European Economic Area (EEA), United Kingdom, or Switzerland, your data is transferred to the United States under the following safeguards:
- EU-U.S. Data Privacy Framework (where applicable)
- Standard Contractual Clauses (SCCs) approved by the European Commission
- Service provider data processing agreements
14. Children's Privacy
Renvizo is not intended for use by individuals under the age of 16. We do not knowingly collect personal data from children. If you believe a child has provided us with personal data, please contact us at privacy@renvizo.com and we will promptly delete it.
15. Cookies and Tracking
The Renvizo mobile app does not use cookies. The Website (renvizo.com) may use essential cookies required for basic functionality. We do not use advertising cookies, tracking pixels, or analytics cookies on the Website.
16. Changes to This Policy
We may update this Privacy Policy from time to time. When we make material changes, we will notify you through the App or by email. The "Last updated" date at the top of this page indicates when the policy was most recently revised.
17. Contact Us
If you have any questions about this Privacy Policy or our data practices, please contact us: