Privacy Policy
Last updated: November 3, 2026
1. Who we are
Omnifox is an omnichannel customer-engagement SaaS platform operated by OMNIFOX, LLC (commercial brand: Omnifox), a company incorporated under the laws of the State of Delaware, United States.
- Legal entity: OMNIFOX, LLC
- Registered address: 131 Continental Dr, Suite 305, Newark, DE 19713, USA
- Privacy contact: [email protected]
- General support: [email protected]
This Policy explains how Omnifox collects, uses, shares and protects personal data, in compliance with Ecuador's Ley Orgánica de Protección de Datos Personales (LOPDP), the EU General Data Protection Regulation (GDPR), the California Consumer Privacy Act (CCPA / CPRA) and Brazil's LGPD.
2. Our roles
Omnifox acts in two distinct capacities depending on the data:
- Data controller for data we collect directly about our paying Customers (account, billing, support interactions).
- Data processor for data that a Customer uploads or sends through the platform about their End Users (contacts, messages, media). The Customer remains the controller of that data; Omnifox processes it only on the Customer's documented instructions.
3. Data we collect
3.1 Account data
- Name, email address, phone number.
- Organization details (legal name, tax ID, billing address).
- Hashed password (we never see your plaintext password).
3.2 Usage and technical data
- IP address, browser user agent, device information.
- Pages visited inside the product, actions performed, timestamps.
- Error and security logs.
3.3 Channel and integration data
- Messages, contacts and media exchanged through connected channels (WhatsApp, Messenger, Instagram, webchat, email, SMS, voice).
- WhatsApp Business credentials:
phone_number_id,waba_idand access tokens — access tokens are encrypted at rest using Laravel's application key. - Messenger and Instagram Graph page tokens (encrypted at rest).
- When you use social publishing or ad management: YouTube, TikTok and Meta ad-account access tokens (encrypted at rest) and the basic profile data described in Sections 7, 8 and 9.
3.4 Billing data
- Legal name, billing address, tax ID.
- Last 4 digits and brand of the payment card (issued by Stripe — Omnifox never stores full card numbers).
3.5 Cookies and trackers
- Strictly necessary session cookies.
- Functional cookies (UI preferences, language, dark mode).
- Optional analytics — see Section 13.
4. How we use your data
- Operate the platform — deliver, receive and route messages on behalf of the Customer across connected channels.
- Provide technical support and resolve incidents.
- Issue invoices and collect payments.
- Improve the product through aggregated, de-identified analytics.
- Comply with legal obligations (tax, court orders, lawful requests from authorities).
- Send service communications (security notices, billing alerts, breaking changes). Marketing communications are opt-in only.
- Detect and prevent fraud, abuse and security incidents.
5. Legal basis (GDPR Article 6)
- Performance of a contract — to deliver the Service the Customer has subscribed to.
- Legal obligation — tax and regulatory compliance.
- Legitimate interest — security, fraud prevention and product improvement, balanced against your rights.
- Consent — for marketing emails, non-essential cookies and any optional AI processing.
6. Sharing with third parties
Omnifox does not sell personal data. We do not share data with advertisers. We share data only with sub-processors that are essential to operate the Service, all bound by data protection agreements:
- Meta Platforms, Inc. — Omnifox is registered as a Tech Provider with Meta. We use the WhatsApp Cloud API, the Messenger Platform and the Instagram Graph API to send and receive messages on behalf of our Customers. Data flowing through these channels is processed by Meta under the WhatsApp Business Messaging Policy and the Meta Platform Terms.
- Amazon Web Services, Inc. (AWS) — hosting, databases, object storage and transactional email (SES). Customer data is stored in region
us-east-2(Ohio, USA). - Stripe, Inc. — payment processing. Omnifox never stores full card numbers — Stripe is a PCI-DSS Level 1 service provider.
- Pusher / Reverb (Laravel) — realtime WebSocket delivery for the inbox and notifications.
- OpenAI, L.L.C. and Anthropic PBC — when a Customer enables AI features (autoreplies, summaries, intent detection), message content is forwarded to these providers under their data processing terms. We anonymize identifiers where technically feasible and never use Customer data to train third-party models.
- Google LLC (YouTube) and TikTok — only if you connect an account to publish: the video and texts that a person in your organization approves are sent to that platform. See Sections 7 and 8.
- Cloudflare, Inc. — CDN, DNS and DDoS protection in front of omnifox.io and customer-facing widgets.
- Sentry / Flare — error monitoring (technical exceptions only; we redact PII before sending).
- Servicio de Rentas Internas (SRI), Ecuador — electronic invoicing for Customers in Ecuador, billed through our Ecuadorian entity (Omnifox SAS), as required by Ecuadorian law.
A complete and current list of sub-processors is available on request at [email protected].
7. YouTube and Google user data
If you connect a YouTube channel to Omnifox to publish videos (Marketing > Posts > Publishing accounts), Omnifox uses YouTube API Services. By connecting a channel you agree to be bound by the YouTube Terms of Service. Data handled by Google is governed by the Google Privacy Policy.
7.1 What we access and why
- youtube.readonly: the channel ID, channel name, handle and avatar, only to show which channel is connected and to choose it as a destination.
- youtube.upload: to upload the videos that a person in your organization approves in Omnifox, with the title, description and privacy setting that person chooses. We keep the ID and link of each uploaded video to show its publication status.
- We do not read your existing videos, analytics, comments, subscribers, messages or any other YouTube or Google account data.
7.2 How we store it
The OAuth access and refresh tokens are stored encrypted at rest (AES-256, Laravel encrypted cast) in your organization's isolated database. They are never shown in the interface, in exports or in API responses. While the connection is active, Omnifox re-verifies the authorization with Google every day.
7.3 What we do not do
We do not sell YouTube or Google user data, we do not use it for advertising, we do not use it to train AI models and we do not share it with third parties, except infrastructure providers (AWS) that process it on our behalf to run the Service. Omnifox staff do not read this data, except with your express consent for support, when necessary for security, or to comply with the law.
7.4 How to revoke access and deletion periods
- From Omnifox: Marketing > Connected accounts > Disconnect (app.omnifox.io/marketing/accounts). Omnifox revokes the token with Google and deletes the tokens and the channel data at that moment, and in any case within 7 days.
- From Google: remove Omnifox at security.google.com/settings/security/permissions. Our daily check detects the revocation, deletes the tokens that same day and deletes the remaining channel data within 30 days (in practice, within 7 days).
- If you close your Omnifox account or ask us to delete your data, YouTube data is deleted within 7 days. For this data, the 90-day general retention period of Section 11 does not apply.
- Deleting data in Omnifox does not delete the videos you already published on YouTube; you can manage them in YouTube Studio.
7.5 Sign in with Google and Google Calendar
Sign in with Google (openid, email, profile scopes): we use your Google name, email, profile picture and ID only to create your Omnifox account and sign you in.
Google Calendar is optional: an Omnifox appointment calendar is connected to a Google Calendar only if someone in your organization chooses to (Calendar > calendar settings > Connect Google). We use:
- calendar.calendarlist.readonly: the ID, name and access level of your calendars, only so you can choose where appointments are saved and which calendars count as busy.
- calendar.freebusy and event reads under calendar.events: only the start, end and status (busy/free, accepted/declined) of your events, so we never offer your customers times when you are already busy. We do not read or store the title, description, location or attendees of your personal events; these time blocks are kept in a temporary cache for at most 90 seconds.
- Writes under calendar.events: create, update and delete in your Google Calendar only the events for appointments booked in Omnifox (title, date and time, appointment notes, location or video-call link, and that appointment's attendees). We store the ID of each event we create so we can update or delete it. We never modify or delete events that Omnifox did not create.
Google Calendar tokens are encrypted at rest (AES-256 with the application key). The rules in Section 7.3 apply. To revoke access: Calendar > calendar settings > Disconnect Google (Omnifox revokes the token with Google and deletes it immediately) or at security.google.com/settings/security/permissions. Disconnecting does not delete events already created in your Google Calendar.
Privacy questions or deletion requests: [email protected].
Omnifox's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
8. TikTok
If you connect a TikTok account to Omnifox (TikTok Login Kit and Content Posting API), your use of TikTok remains subject to the TikTok Terms of Service and the TikTok Privacy Policy.
- What we access: your TikTok open ID, display name and avatar (
user.info.basic), and permission to post the videos that a person in your organization approves in Omnifox (video.publish), with the privacy and interaction settings that person chooses. We keep the publication ID and status of each post. We do not read your followers, messages, videos or analytics. - Storage: the access and refresh tokens are stored encrypted at rest in your organization's database and are never shown in the interface or in API responses.
- No sale, no advertising: we do not sell this data, we do not use it for advertising and we do not share it with third parties, except infrastructure providers (AWS) acting on our behalf.
- Revoking from Omnifox: Marketing > Connected accounts > Disconnect (app.omnifox.io/marketing/accounts). Omnifox revokes the token with TikTok and deletes the tokens and profile data at that moment, and in any case within 7 days.
- Revoking from TikTok: in the TikTok app, Profile > Menu > Settings and privacy > Security and permissions > Apps and services, remove Omnifox (on the web: tiktok.com/setting). Our daily check detects it, deletes the tokens that same day and the remaining data within 30 days (in practice, within 7 days).
- For this data, the 90-day general retention period of Section 11 does not apply. Deleting data in Omnifox does not delete videos already posted on TikTok.
- Questions: [email protected].
9. Meta: Facebook Pages, Instagram and ads
Your use of these features remains subject to the Meta Terms of Service, the Instagram Terms of Use, the Meta Commercial Terms and the Meta Privacy Policy.
9.1 Publishing to Facebook Pages and Instagram
- What we use: the Facebook Page or Instagram professional account you connected in Channels: its ID, name or username and the Page access token (permissions
pages_manage_postsandinstagram_content_publish), only to publish the posts that a person in your organization approves in the Content Studio. We keep the ID and link of each published post to show its status. - Storage: the token is stored encrypted at rest and is never shown in the interface or in API responses.
- Revoking from Omnifox: delete the channel in Channels. Omnifox unsubscribes its app from the Page or account at Meta and deletes the token and the channel data within 7 days (this also deletes that channel's conversations in Omnifox).
- Revoking from Meta: remove Omnifox in Facebook > Settings > Business integrations or in Instagram > Apps and websites. The token stops working at once and the channel shows that it must be reconnected; delete the channel in Omnifox to delete its data, or ask us at [email protected] and we will delete it within 30 days. Meta can also send us a deletion request on your behalf: see Data deletion instructions.
9.2 Managing Meta ad accounts
- What we use: with
ads_readandads_management, the ad accounts you choose to link (ID, name, currency, time zone, status), their campaigns, ad sets, ads and performance metrics, to show them in Omnifox and, only when a person with permission in your organization asks for it, to pause or resume them or change budgets within the spending cap you set. Each change is recorded in a change log (who, what, when). - Storage: the Facebook access token is stored encrypted at rest and is never shown in the interface or in API responses.
- Revoking from Omnifox: Marketing > Ads > Disconnect (app.omnifox.io/ads/accounts). The token is deleted at that moment. The ad account ID and name are kept only inside the change log, as the record of the changes made through Omnifox. This button does not remove Omnifox's permission at Meta, because the same Facebook authorization may be serving your other ad accounts or Pages.
- Revoking from Meta: remove Omnifox in Facebook > Settings > Business integrations. Our daily check detects that the token no longer works and deletes it within 30 days (in practice, within 7 days of detecting it).
We do not sell data obtained from Meta, we do not use it for our own advertising or to build profiles, and we do not share it with third parties, except infrastructure providers (AWS) acting on our behalf. For tokens and profile data obtained from Meta, the periods above apply instead of the 90-day general period of Section 11; the change log follows the general rules of Section 11. Questions: [email protected].
10. International transfers
Because Omnifox uses AWS and other cloud providers, personal data may be stored or processed in the United States and other countries outside your jurisdiction. Where required (notably for EU/EEA data subjects), transfers are covered by Standard Contractual Clauses or equivalent safeguards. The Customer's contract with Omnifox includes a Data Processing Addendum that incorporates these clauses by reference on request.
11. Retention
- Active account: while the contractual relationship lasts.
- Channel messages: configurable by the Customer. Default is unlimited; minimum 90 days for support and dispute purposes.
- Data from connected platforms (YouTube/Google, TikTok, Meta): the specific periods of Sections 7, 8 and 9 apply (deletion within 7 days when you revoke from Omnifox, within 30 days when you revoke from the platform), not the 90-day period below.
- After account closure: 90-day grace period for support and disputes, then deletion. Tax and billing records are kept for up to 7 years as required by applicable law.
- Security and access logs: up to 12 months.
12. Your rights (GDPR, CCPA, LOPDP)
Subject to applicable law, you have the right to:
- Access your personal data and information about how we process it.
- Rectify inaccurate or incomplete data.
- Erase your data ("right to be forgotten") when no longer necessary.
- Port your data — export in machine-readable JSON via
/settings/data-exportinside the product. - Object to processing based on legitimate interest.
- Restrict processing in certain circumstances.
- Withdraw consent at any time, without retroactive effect.
- Lodge a complaint with your local supervisory authority (e.g., Ecuador's Superintendencia de Protección de Datos Personales, your EU member-state DPA, the California Attorney General).
- Opt out of sale / sharing of personal information — Omnifox does not sell personal data; this right is honored by default.
To exercise any of these rights, write to [email protected] with the subject "Data Subject Request" and proof of identity. We respond within 30 days (15 business days under LOPDP).
If your data was uploaded to the platform by one of our Customers, please contact that Customer directly. We will forward such requests to them where appropriate.
14. Security
- TLS 1.2+ in transit (HSTS enforced).
- AES-256 encryption at rest on AWS RDS, KMS-managed keys.
- Channel and connected-platform access tokens (WhatsApp, Messenger, Instagram, YouTube, TikTok, Meta Ads) encrypted with Laravel
Crypt. - Role-based access control (RBAC) and least-privilege internal access.
- Optional two-factor authentication (2FA) for end users; mandatory for administrators.
- Immutable audit logs.
- Automated, redundant backups.
- DKIM, SPF and DMARC on outbound mail.
- Continuous error and anomaly monitoring.
- SOC 2 Type II: in progress.
No system is 100% secure. In case of a data breach with risk to data subjects, Omnifox will notify affected Customers and the competent supervisory authority within 72 hours, as required by GDPR and LOPDP.
15. Children
Omnifox is a B2B service. It is not directed to anyone under 18. We do not knowingly collect personal data of minors. If you believe a minor has provided us with personal data without parental consent, contact us at [email protected] and we will delete it.
16. Changes to this policy
We may update this Policy as our service evolves or the law changes. Material changes will be notified by email to workspace administrators at least 30 days before they take effect. The effective date at the top of this document will be updated. Continued use of the Service after the effective date constitutes acceptance.
17. Governing law
This Policy is governed by the laws of the State of Delaware, United States, without prejudice to mandatory protections that apply to data subjects under GDPR (EU/EEA/UK), CCPA/CPRA (California) and LGPD (Brazil).
18. Contact
- Privacy and Data Subject Requests: [email protected]
- Legal: [email protected]
- General support: [email protected]
- Postal address: OMNIFOX, LLC, 131 Continental Dr, Suite 305, Newark, DE 19713, USA.
- Data Protection Officer (DPO): appointed; reachable at [email protected].