Legal
Privacy Policy
Effective date: 20 November 2026
This policy explains what information RevenueAI handles, why, who helps us process it, and how it can be deleted. It describes how the product works today. We do not sell personal information, and we do not use it for advertising.
1. Who we are
RevenueAI is a lead management service for service businesses. It turns enquiries that customers send through a business’s channels (website form, email, SMS, Instagram, Messenger, WhatsApp, Telegram, Viber, LINE and WeChat) into leads, replies to them, and lets the business’s staff manage the conversation.
RevenueAI is operated by BURMESE BOX (ABN 20 945 270 952), 14 Cropton St, Jordan Springs NSW 2747, Australia. For privacy questions, contact tom@smarteduglobe.com.
2. Businesses and their customers
RevenueAI has two kinds of users:
- Businesses and their staff, who create a RevenueAI account and connect their own channels.
- Their customers: people who send an enquiry or message to one of those businesses. They do not have a RevenueAI account.
Customer information is collected and stored on behalf of the business the customer contacted, so that business can respond. That business decides how its customers’ information is used, and RevenueAI handles it for the business to provide the service. Each business can only see its own leads and conversations. If you are a customer, you can also contact the business directly about your information.
For business accounts, staff accounts and billing, RevenueAI decides how that information is used, as described in this policy.
3. What we collect
Business and staff accounts
- Business details entered during setup and in settings: business name, contact details, services, prices, opening hours and the business information used to answer customers.
- Staff names, email addresses and roles. Sign-in is handled by our authentication provider (Supabase). RevenueAI does not store passwords in plain text.
- Plan and subscription status. Payments are processed by Stripe: RevenueAI does not see or store card numbers. We keep the Stripe customer and subscription identifiers.
- Connection details for each channel the business connects, including access tokens. Tokens and passwords for connected services are stored encrypted.
Customers’ enquiries
- The details a customer gives or a channel provides: name, phone number, email address, the service requested, location and answers to the business’s questions.
- The conversation: messages from the customer, replies from RevenueAI and from staff, the time of each message, and whether it was delivered or read.
- The identifier each messaging channel uses for the customer (for example an Instagram-scoped ID, a Messenger page-scoped ID, a WhatsApp number or a Telegram user ID), so later messages join the same conversation.
- Appointments and notes the business records for the lead.
Technical records
- Incoming webhook events from messaging platforms, kept in a processing queue until handled (see Instagram data).
- An audit log of administrative actions, billing changes, SMS opt-in and opt-out requests, and inbound emails or text messages that could not be matched to a business. These records can include a phone number or email address, an email subject, or the text of an unmatched SMS.
- Application server logs of errors and operational events. They are designed to leave out access tokens, but can include identifiers and error messages returned by providers.
4. Instagram data
A business can connect its Instagram professional account through Meta’s sign-in. RevenueAI asks Meta for two permissions only: instagram_basic and instagram_manage_messages. We do not read, publish or manage posts, comments, stories, ads, insights or followers.
About the connected business account
- The Instagram account ID and username, so the business can see which account is connected and incoming messages reach the right business.
- The Meta business portfolio ID and login configuration ID that Meta returns at sign-in.
- The access token Meta issues, stored encrypted, with its expiry date and when it was last checked with Meta.
About people who message the business
- The sender’s Instagram-scoped ID. It is issued by Instagram for that business account only and is not the person’s username.
- The text of Direct Messages sent to the business, the message ID and time, and replies sent from RevenueAI or from the business’s Instagram app.
- The sender’s name or username when Instagram provides it, which is used as the lead’s name.
- Whether replies were delivered and read.
- Attachments (photos, videos, voice messages, files, shares) are not downloaded or stored. Only the type of attachment is noted in the conversation, for example “a photo”, so staff know to check Instagram.
Webhook events
Instagram sends each message to RevenueAI as a webhook event. The event is saved first so that no message is lost, then processed. Once processed, its message contents are cleared from the queue; the stored conversation is kept as described above. An event that could not be processed keeps its contents so staff can be alerted and the message is not lost.
5. How we use data
- To create leads and show each business its conversations, appointments and follow-ups.
- To send replies and notices to customers on the channel they used, within that channel’s rules (for example Instagram, Messenger and WhatsApp only allow replies within 24 hours of the customer’s last message).
- To alert the business’s staff, including by email, when a customer asks for a person or a message needs attention.
- To keep connections working: checking that access tokens are still valid and telling the business when it needs to reconnect.
- To run accounts, billing, security and support.
We only send messages to customers who contacted the business first. We do not use customers’ information to send promotions or to train AI models.
6. AI-assisted replies
When AI replies are enabled, RevenueAI sends the following to OpenAI to write a reply or pick out details such as a phone number or the service requested: the business’s information and instructions, the details already known about the lead, and the customer’s latest message with recent messages in the conversation.
Requests are made with OpenAI’s option not to store the response as application data. This is not the same as zero data retention: OpenAI may still keep request data for a limited time under its own policies, for example to detect abuse. When AI is not enabled, RevenueAI replies with fixed templates and nothing is sent to OpenAI.
On Instagram, Messenger, WhatsApp, Telegram, Viber, LINE and WeChat, staff can take over a conversation, after which RevenueAI stops replying automatically to it.
7. Automated assessment of enquiries
To help a business decide which enquiries to answer first, RevenueAI automatically writes a short summary of each enquiry and gives it a score. It marks an enquiry as qualified, not qualified (for example, when the business doesn’t offer the service requested) or needing a person. This uses fixed rules and, when AI is enabled, the AI described above.
These assessments are only shown to the business. RevenueAI does not make decisions with legal or similarly significant effects about anyone: the business’s staff decide how to respond.
8. Service providers
We use these providers to run RevenueAI. Messaging and email providers only receive data for the channels a business actually connects.
- Supabase: database and staff sign-in.
- Amazon Web Services: hosts the RevenueAI application server.
- Meta Platforms: Instagram, Facebook Messenger, WhatsApp and Facebook Lead Ads, which carry messages and leads between customers and the business.
- OpenAI: AI-assisted replies and detail extraction, when enabled (see above).
- Resend: sends email (replies to customers who wrote by email, and alerts to the business) and receives enquiry emails.
- Twilio: sends and receives SMS.
- Stripe: subscriptions and payments.
- Google: sends staff replies from a business’s own Gmail address, when the business connects it.
- Telegram, Rakuten Viber, LINE and Tencent (WeChat): carry messages on those channels, when connected.
Some of these providers process data in countries other than the one you live in. Each processes data under its own terms and privacy policy.
9. Storage and security
- Account, lead and conversation data is stored in a Supabase-hosted PostgreSQL database. Database rules keep each business’s data separate from other businesses.
- RevenueAI’s website and dashboard are served over HTTPS, so data is encrypted in transit between your browser and our server.
- Access tokens and passwords for connected services are encrypted before they are stored.
- RevenueAI does not keep a separate store of files or attachments.
- Database backups are managed by our database provider. Backup retention: up to 7 days.
10. Cookies and browser storage
RevenueAI only uses what it needs to work:
- Sign-in cookies set by our authentication provider (Supabase), which keep staff signed in to the dashboard.
- A cookie that marks a demo session, when someone uses the demo.
- Browser storage in the dashboard that remembers which notifications a staff member has already read.
RevenueAI does not use analytics, advertising or tracking cookies, and does not place advertising pixels on its pages.
11. How long we keep data
- Leads and conversations are kept while the business’s account is active, until deletion is requested as described on our Data Deletion page.
- Disconnecting a channel removes its stored access token and connection details, but does not delete the leads and conversations already received.
- Closed accounts: kept for 30 days after the account is closed so it can be reactivated, then personal data is permanently deleted, unless the law requires us to keep some of it longer.
- Server logs: kept for up to 14 days.
12. Your choices and deletion
You can ask us to access, correct or delete personal information we hold about you. Depending on where you live, the law may give you further rights. We will respond within 30 days of receiving a verified request, or sooner where the law requires it.
- Customers can ask the business they contacted, or ask us directly.
- Businesses can disconnect a channel at any time from Integrations, and can ask us to delete their customer data or their whole account.
- You can also remove RevenueAI’s access to Instagram or Facebook from your Meta account settings at any time.
Deletion requests are currently handled by our team, not automatically. How to make a request, and what each option deletes, is set out on our Data Deletion page.
13. Children
RevenueAI is a service for businesses and is not directed at children. You must be 18 or older to have a staff account.
RevenueAI cannot tell the age of a customer who messages a business. If a child’s information has been received through a business’s channels, the business, or the child’s parent or guardian, can ask us to delete it as described on our Data Deletion page.
14. Changes, contact and complaints
We will update this page when what we collect or how we use it changes, and change the effective date at the top.
Questions or requests: tom@smarteduglobe.com, or by post to BURMESE BOX, 14 Cropton St, Jordan Springs NSW 2747, Australia.
If you are not satisfied with our response, you can complain to the Office of the Australian Information Commissioner (OAIC) at oaic.gov.au.
See also: Privacy Policy · Terms of Service · Data Deletion