revnu

Privacy policy

Privacy

Last updated: October 21, 2026. How the Revnu service and its integrations collect, use and retain data. We never sell your data or train shared models on your content.

Revnu service

This policy covers the Revnu growth service operated by IT5 Inc. and the integrations you choose to connect. The separate Revnu New Tab extension has its own data practices, described below.

Privacy Policy — Revnu New Tab (Chrome extension)

Last updated: July 5, 2026

The Revnu New Tab extension (published by IT5 Inc. DBA Revnu) does not collect, store, transmit, sell, or share any user data.

  • No personal information, browsing history, or usage analytics are collected.
  • Search queries typed into the new tab page are passed directly to your browser's default search engine via Chrome's built-in search API; the extension never sees, stores, or transmits them to any server.
  • The extension makes no network requests. All wallpapers, fonts, and other assets are bundled inside the extension package.
  • Wallpaper rotation state is stored locally on your device (localStorage) and never leaves it.
  • The extension contains no ads, no trackers, and no third-party code.

Questions: george@revnu.com

What we collect

Account info (email, name), billing and contact details, the data you connect via integrations (your product copy, brand voice, CRM and analytics data, GitHub repo metadata, the ad accounts you connect and their advertising history (campaigns, ads, creatives, audiences and performance reports), and content from tools you authorise such as Slack, Notion, and Gmail), and product usage telemetry (page views, feature interactions). We collect what we need to run Revnu for you and nothing else.

Demo enquiries

When you press Continue on our booking form, we save your submitted work email, company website, budget and timing answers to review your enquiry, including when you do not book a call. We also save the attendee and company details supplied with confirmed bookings, including bookings made directly through our calendar. Confirmed bookings may be assessed using public company information. We retain these enquiry details for up to 180 days, or the configured booking-record retention period, and record call and sales outcomes separately. Submitting an enquiry does not subscribe you to marketing emails.

Why we collect it

To operate the service, generate work for you (drafts, ads, outbound), bill correctly, debug issues, and improve the product. We never sell your data, never show your content to another customer, and never train shared LLMs on your content.

How Revnu learns, by plan

On self-serve plans, we regularly review how agents across self-serve accounts perform and turn what works into general improvements for every agent, such as better ways to write, research or follow up. Only generalized lessons are carried over. No customer sees another customer's content, contacts, results or settings, and no agent is given another account's data.

On Managed plans, your data is used only for your account and is never part of these reviews, and our model providers process it with zero data retention: they do not store your requests after responding. Data from Gmail, Google Ads and Slack is never used this way on any plan.

Prospect data

When you use Revnu for outreach, it finds and contacts people for you. That means names, job titles, employers, business email addresses, LinkedIn profiles and public company information. This comes from licensed B2B data providers, which compile publicly available professional and company information, and from public sources such as company websites, news and professional profiles. Revnu records which source supplied each contact's email address, so you can tell a prospect where their details came from.

For this outreach you are the controller and Revnu is your processor. Unsubscribes and opt-outs reported by our email providers go on your block list automatically, and you can add anyone to it yourself. Revnu never contacts anyone on your block list. A prospect can email support@revnu.com to ask what we hold about them or to have it deleted.

Gmail and Google API data

When you connect Gmail, Revnu uses Unipile to connect your mailbox. We access message content, headers, recipients, attachments and thread information as needed to show your inbox, understand replies, prepare drafts and send messages within your instructions and account approval settings. Unipile, our infrastructure providers and our AI model providers process the data needed to provide these features.

Revnu's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy and the Google Workspace API User Data and Developer Policy, including the Limited Use requirements. We do not sell Gmail data, use it for advertising targeting or use it to train shared AI models. Gmail data is excluded from reviews that carry general lessons between customer accounts. Human access is limited to the circumstances those policies permit, such as your explicit consent to view specific data, necessary security investigations or legal requirements.

You can disconnect Gmail in Revnu and revoke access in your Google Account connections. Disconnecting does not erase messages in Gmail or delete all historical records in Revnu. To request deletion of retained Gmail data, email support@revnu.com. The retention and deletion terms elsewhere in this policy apply.

Google Ads and conversion measurement

When you connect Google Ads, Revnu stores an encrypted authorization token and reads accessible advertiser and manager account information, campaign settings and performance reports. We use this data to display results, prepare campaigns and manage advertising within your instructions and account controls. Our infrastructure and model providers process the data needed to provide those features. We do not sell Google data, share it across customer accounts or use it to train shared models.

For each Google Ads account you can access, Revnu reads and keeps a copy of its advertising history: campaigns, ad groups, ads, keywords, assets (with their images), audiences, budgets, bidding strategies, conversion actions and their settings, the account's change history, and daily performance reports, including search terms. We use it to run and report on your advertising, and keep it in your workspace only.

If you enable Google conversion delivery, Revnu sends eligible business outcomes to your configured Google destination through Google Data Manager. Records can include a Google click identifier, event identifier, time, value, currency and advertising consent states. Google processes these records for conversion measurement. This integration does not upload email addresses or phone numbers for enhanced conversion matching.

Connecting an ad account does not provide visitor consent. Customer websites must provide the appropriate notices and consent choices. Revnu checks the recorded Google-specific consent before forwarding eligible outcomes.

Disconnecting Google Ads

Disconnecting in Revnu removes the stored connection. It does not pause campaigns in Google Ads, erase records already sent to Google, or immediately delete your historical campaign and measurement records in Revnu. You can also revoke access in your Google Account connections. To request deletion of data retained by Revnu, email support@revnu.com.

Meta Ads

When you connect Meta Ads, Revnu stores an encrypted authorization token and reads the advertiser accounts you can access so you can choose the account Revnu should use. Connecting does not publish a campaign or change its budget.

For each ad account you can access, Revnu reads and keeps a copy of its advertising history: campaigns, ad sets, ads and creatives (with their images and videos), audiences, pixels and their settings, the account's change log, and daily performance reports. We use it to run and report on your advertising, and keep it in your workspace only.

Disconnecting removes the stored Meta authorization token but does not pause campaigns in Meta or stop their spend. A deletion request sent through Meta removes the matching token, the discovered Meta account records and the advertising history Revnu kept, and returns a confirmation code and status URL. You may also request deletion by emailing support@revnu.com.

Microsoft Advertising

When you connect Microsoft Advertising, Revnu stores an encrypted authorization token and reads the ad accounts you can access so you can choose the account Revnu should use. Connecting does not publish a campaign or change its budget.

For each ad account you can access, Revnu reads and keeps a copy of its advertising history: campaigns, ad groups, ads, keywords, assets (with their images and videos), audiences, conversion goals and UET tags and their settings, and daily performance reports, including search terms and location, age, gender and device breakdowns. We use it to run and report on your advertising, and keep it in your workspace only.

Disconnecting removes the stored Microsoft authorization token but does not pause campaigns in Microsoft Advertising or stop their spend. To delete the advertising history Revnu kept, email support@revnu.com.

LinkedIn Ads

When you connect LinkedIn Ads, Revnu stores an encrypted authorization token and reads the ad accounts and company pages you can access. Connecting does not publish a campaign or change its budget.

For each ad account you can access, Revnu reads and keeps a copy of its advertising history: campaign groups, campaigns, ads and creatives (with their images and videos), conversions, audiences and their settings, and daily performance reports, including LinkedIn's aggregated audience demographics. We use it to run and report on your advertising, and keep it in your workspace only.

Disconnecting removes the stored LinkedIn authorization token but does not pause campaigns in LinkedIn or stop their spend. You can also revoke access in your LinkedIn settings. To request deletion of the account records and advertising history Revnu kept, email

TikTok Ads

When you connect TikTok Ads, Revnu stores an encrypted authorization token and reads the advertiser accounts you authorised so you can choose the account Revnu should use. Connecting does not publish a campaign or change its budget.

For each advertiser account you authorise, Revnu reads and keeps a copy of its advertising history: campaigns, ad groups and ads (including deleted ones), the image and video library with the images and videos themselves, custom audiences, identities, pixels and their events, and daily performance reports, including by age, gender, country and placement. We use it to run and report on your advertising, and keep it in your workspace only.

Disconnecting removes the stored TikTok authorization token but does not pause campaigns in TikTok or stop their spend. Deleting your Revnu account deletes the advertising history Revnu kept. You may also request deletion by emailing support@revnu.com.

Reddit Ads

When you connect Reddit Ads, Revnu stores an encrypted authorization token and reads the ad accounts you can access so you can choose the account Revnu should use. Connecting does not publish a campaign or change its budget.

For each ad account you can access, Revnu reads and keeps a copy of its advertising history: campaigns, ad groups, ads and their posts (with their images and videos), the images and videos in your asset library, audiences, pixels, lead forms and funding details, and daily performance reports. We use it to run and report on your advertising, and keep it in your workspace only.

Disconnecting removes the stored Reddit authorization token but does not pause campaigns in Reddit or stop their spend. To request deletion of the advertising history Revnu kept, email support@revnu.com.

X Ads

When you connect X Ads, Revnu stores an encrypted authorization token and reads the advertiser accounts you can access. Connecting does not publish a campaign or change its budget.

For each ad account you can access, Revnu reads and keeps a copy of its advertising history: campaigns, ad groups, promoted posts and their text, cards, the images and videos they use, audiences, conversion tags, funding instruments and their settings, and daily performance reports. We use it to run and report on your advertising, and keep it in your workspace only.

Disconnecting removes the stored X authorization token but does not pause campaigns in X or stop their spend. To delete the advertising history Revnu kept, email support@revnu.com.

Slack

When you install the Revnu Slack app, Slack gives Revnu a bot token for your workspace. We store it encrypted, along with your workspace ID and name and the Slack channels you link to your Revnu account.

Revnu reads messages and files only in channels where you have added it. It acts on a message that mentions @Revnu, and on replies in a thread that started with one. In a channel that is not linked yet, it checks messages only for the one-time phrase that links the channel to your account, and does not store the others. For those requests we store the message text, the Slack user IDs and display names in the thread, message timestamps and event IDs, and any file a user attaches to the request. Revnu does not request Slack email addresses. It does not read direct messages and does not export or back up your channel history.

We use this data to understand and answer your requests, post replies and completed work back into Slack, and debug delivery problems. Our model providers process the request content needed to produce a reply. They do not train on it, and we do not use Slack data to train any model.

Slack conversation records stay in your Revnu workspace history while your account is active. When you uninstall the Slack app, Slack notifies us and we stop receiving events and stop sending messages to that workspace immediately. We keep your channel links so a reinstall picks up where you left off. To delete stored Slack data, email support@revnu.com and we will delete it within 30 days.

AI assistants and the MCP server

When you connect Claude, ChatGPT, Cursor or another AI app to Revnu's MCP server, we store the app's name and redirect addresses, and an API token scoped to the permissions you chose on the consent screen. We keep only a hash of the token.

Review decisions the app makes, block list entries it adds and messages it sends to Revnu are recorded against its name in your account. The app receives the results of the tools it calls, such as review cards, leads and results, and its own provider's privacy terms apply to that data once it has it.

Revoke an app any time in Settings → Developers; its token stops working immediately. To delete the stored records, email support@revnu.com and we will delete them within 30 days.

Subprocessors

These vendors process personal data to run Revnu. Each has agreed to data processing terms that require it to protect the data and use it only to provide its service to us.

  • Convex: database and backend
  • Vercel: web hosting
  • Cloudflare: edge network and background jobs
  • E2B: isolated computers the Revnu agent works in
  • Anthropic and OpenAI: AI models, which do not train on your data
  • Stripe: payments
  • Resend: account and notification emails
  • PostHog: product analytics

For outreach and research we also use licensed B2B data providers, email and LinkedIn delivery providers, email verification services, web research tools and media generation services. We share the full list with customers under a confidentiality agreement; email support@revnu.com. Customers with a data processing agreement hear from us before we add a subprocessor.

How long we keep it

We keep your data for as long as your account is active and for a limited period afterward as needed to provide the service, comply with our legal obligations, resolve disputes, and enforce our agreements. When you disconnect an integration, we delete or de-identify the associated cached data within a commercially reasonable period. Historical work, reports and measurement records may remain where needed for the purposes described above. We retain operational logs only as long as needed for security and debugging. You can request deletion at any time (see “Your rights”).

Your rights

You can export your data, request deletion, or correct inaccurate info any time from account settings or by emailing support@revnu.com. We respond within 30 days. If you're in the EU/UK, you have GDPR rights including data portability and the right to lodge a complaint with your data-protection authority.

Data processing agreement

For personal data you put into Revnu or ask Revnu to process, including prospect data, you are the controller and IT5 Inc. is your processor. Our data processing agreement meets Article 28 of the UK and EU GDPR. Email support@revnu.com to sign it, or send us yours.

International transfers

Revnu is operated by IT5 Inc. in the United States, and most of our subprocessors process data in the United States. When personal data moves out of the UK or the European Economic Area, we rely on the European Commission's Standard Contractual Clauses with the UK Addendum, or on the recipient's certification under the EU-US Data Privacy Framework and its UK Extension. Our data processing agreement includes the Standard Contractual Clauses and the UK Addendum.

Cookies + tracking

We use first-party cookies for authentication and session state, and PostHog for product analytics. Customer websites can install Revnu Tag to measure visits and business outcomes, including advertising click identifiers and consent states. When a customer enables a supported advertising destination, eligible outcomes can be shared with that provider as described above. You can disable cookies in your browser; some features won't work without them.

Ad measurement on revnu.com

Ad measurement runs automatically on revnu.com. We use advertising cookies from the ad platforms we advertise on, such as Google and Meta. We share eligible booked calls, trial starts and payments with those platforms. Each record can include that platform's ad click identifier, the event identifier and time, and a payment's value and currency. Google's record never includes your name or email. Other platforms', such as Meta's, can also include a hashed copy of the email address or phone number you gave us, and Meta's can include its browser cookies, your browser's user agent and your IP address. Google ad personalisation is enabled. You can manage or block cookies through your browser settings.

Security

All data is encrypted in transit (TLS 1.2+) and at rest. Access controls are role-based and audit-logged. SOC 2 Type II is in progress. If you find a vulnerability, email support@revnu.com with "security" in the subject — we'll respond within one working day.

Children

Revnu isn't directed at users under 13. If you believe we've collected data from a child under 13, email us and we'll delete it.

Changes

If we change this policy in a material way, we'll notify you in-product before it takes effect. Otherwise, the latest version is always at this URL.

Contact

This service is operated by IT5 Inc. (Delaware, USA). Questions about this policy: support@revnu.com.

See also: Terms of service and Data Processing Agreement.