Privacy Policy

Information we collect

We collect information you provide directly, data from connected platforms, and technical data generated by using our service.

Third-party integrations

When you connect external platforms, we access your data on those platforms only to provide the features you request. We access only the permissions you explicitly grant during the OAuth flow.

We do not store platform data longer than necessary to provide the features you use. You can disconnect any integration at any time from your Integrations page. Each integration is connected within a specific workspace and is only used for that workspace.

Telegram (optional AI assistant interface)

Telegram is an optional way to chat with the same Floating IQ AI assistant you use on the web — it is not a separate product, AI, or data store. Linking Telegram is entirely your choice, and the assistant, memory, and integrations are unchanged whether you use the web app or Telegram.

• How linking works: From the Integrations page we generate a secure, single-use, time-limited token and open our Telegram bot with it. When you press Start, the bot links your Telegram account to your Floating IQ account.
• What we store: your Telegram user ID, chat ID, username (if set), the workspace currently linked to your Telegram, and the messages you exchange with the assistant (stored as part of your workspace chat history, the same way web chats are stored).
• What it can access: messages sent through Telegram are answered using your currently selected workspace's data, connected integrations, and long-term memory. You can switch workspaces from Telegram, and the assistant only ever accesses workspaces you own.
• Processing: messages are transmitted through Telegram's servers (subject to Telegram's own privacy policy) and processed by our AI provider (OpenAI) to generate replies.
• Duplicate protection & disconnect: a Telegram account can be linked to only one Floating IQ account. You can unlink at any time from the Integrations page, which removes the stored Telegram link.

Workspaces & data isolation

Floating IQ is multi-tenant. Each user can have multiple businesses/workspaces, and all workspace-owned data — integrations, cached platform data, chat history, and business memory — is strictly isolated per workspace and per user. Every request resolves an active workspace, ownership is verified against your account, and database access is scoped so one workspace can never read another workspace's data. This isolation applies identically whether you access the assistant from the web app or from Telegram.

Meta Platform Data — Facebook and Instagram Advertising

Connecting Meta Ads is voluntary. You authorize access through Meta and confirm the connection in Floating IQ for your workspace. We retrieve advertising information through authorized Meta APIs, limited to the permissions and advertising assets available through your authorization. You explicitly select the advertising account for your workspace from the accounts available through your authorization. We retrieve its currency and timezone to display amounts and reporting dates accurately. We also retrieve your Meta app-scoped user identifier to associate your authorization with deletion requests; this is separate from the advertising account identifier.

Information accessed and purposes

We access advertising account identifiers and names; campaign identifiers, names, configured and effective status, objectives and remaining/daily/lifetime budgets; ad set identifiers, names, campaign associations, status and daily or lifetime budgets; and advertisement identifiers, names, status and campaign/ad set associations. We also retrieve performance insights, including spend, clicks, impressions, click-through rates and conversion actions, and calculate summary metrics. The reporting period is the last 30 complete days in the advertising account timezone; website purchase counts are a specific conversion action, not a count of all business outcomes. We use this information for dashboards, reports, audits, AI recommendations and draft advertising copy.

Production reporting does not retrieve targeting settings, Page lists or Page engagement data, Facebook or Instagram private messages, personal posts, contacts, or unrelated personal information.

Permissions and available functionality

Production Meta advertising access is read-only. A disabled-by-default local development implementation supports explicitly approved campaign, ad set and ad status changes and existing daily or lifetime budget updates. It requires separate Meta ads_management authorization and records proposals, decisions and execution outcomes. It cannot be enabled in production by its local feature flag. In local development only, separately approved steps can upload supplied image/video assets and create paused traffic campaigns, targeted ad sets, standalone creatives and paused ads. Creating a creative may create an unpublished Page story. Activation requires another approval. There is no automatic multi-step publishing or background advertising change. Acknowledging or dismissing a Meta recommendation, or keeping or dismissing a copy draft, records your decision within Floating IQ; it does not execute a change in Meta. Production campaign-management writes and Page-management features are not currently available. Any future functionality requiring additional access would require appropriate authorization and updated disclosures.

Local identity selection additionally requires already authorized pages_show_list, pages_read_engagement and pages_manage_ads grants, plus instagram_basic for a connected Instagram identity. These permissions are not requested by the current OAuth flow. Local creation verifies advertising account tasks, Page access and linked Instagram identity. Supplied media bytes are retained within the durable approval record so execution uploads exactly the reviewed asset; chat previews and audit logs contain media metadata and a hash instead of those bytes. Full account erasure removes these approval records under the controls below.

Processing and sharing

Meta advertising information is processed by our backend hosted on Render and stored in Supabase. When you use AI features, relevant advertising information is sent to OpenAI's API: performance analysis includes campaign/ad set names, status, objectives, budgets and metrics; copy generation includes the campaign name and any business context you provide. Assistant requests can also include advertising results and relevant conversation context. If you use the optional Telegram assistant, messages and replies containing this information pass through Telegram.

We do not sell Meta Platform Data or use it for unrelated advertising or unauthorized purposes. We do not use it to train our own AI models. OpenAI states that API data is not used for model training by default unless the API customer explicitly opts in; its processing and retention are governed by the applicable service terms and account settings. See OpenAI's API data controls. This does not mean that AI requests have zero retention.

Your control, retention and deletion

You can disconnect Meta Ads from the Integrations page. On successful disconnect, we delete the locally stored integration record and encrypted access token, cached Meta advertising data, and recommendations and generated drafts linked to that integration from our active database during that request. These records are not held for a seven-day waiting period. The Meta integration cleanup is transactional; a failure is not reported as completed deletion. We also attempt to revoke the app's permissions with Meta; provider revocation can fail independently of local deletion.

You can also remove Floating IQ's access in your Facebook Business Integrations settings. Removing access at Meta does not itself confirm deletion of all copies held by Floating IQ; use our disconnect option or contact us for deletion assistance. An expired or invalid connection is not the same as a completed deletion request. A verified deletion callback from Meta receives a private confirmation code and a public status link showing the recorded processing outcome. We retain a minimal deletion-request record, including the Meta app and user identifiers, confirmation code, status and timestamps, to report the outcome and prevent old authorizations from restoring deleted connections; it contains no access token or advertising content. Older connections without a verified Meta user identifier require review; we do not identify them by guessing from ad-account IDs.

A full account-deletion request removes your locally stored advertising approval arguments, execution results and mutation history together in a verified database transaction. Disconnecting alone preserves that history. Deletion cannot complete while an approved action is still marked executing, including an interrupted execution awaiting resolution. A terminal failed or uncertain result does not block deletion and is never automatically retried. Before erasing local evidence, check Meta Ads Manager for any uncertain result and save any IDs you need. Deleting Floating IQ data does not delete, pause or undo advertising objects in Meta Ads Manager. An identity-service failure is reported as incomplete and can be retried. A minimal, backend-only hash of the deleted account identifier and timestamp prevents stale requests from restoring deleted records; it contains no advertising data. The minimal Meta deletion-request receipt described above is retained separately for deletion status and replay protection.

Disconnecting does not delete advertising approval history or the associated mutation audit trail, your workspace, chat history, business memory or other reports that may contain previously retrieved information. You can delete a workspace using the workspace switcher, or request account deletion, access to your data or further removal at floatingiq.22@gmail.com. See our Data Deletion page for instructions. These actions concern Floating IQ's stored information; we do not promise to delete advertising records from Meta's own systems.

Google API User Data

Floating IQ accesses Google APIs to provide our marketing analysis features. We strictly limit our access to what is necessary.

Data Accessed

Data Usage & Third-Party Processing

Floating IQ processes Google data exclusively to perform the features you request (e.g., generating marketing reports and AI analysis). To provide these features, we use Large Language Models provided by third-party processors, primarily OpenAI. Your Google data is sent to OpenAI strictly for processing your specific requests. OpenAI does not use your data to train their models.

AI Processing and Recommendations: AI recommendations are advisory only until explicitly approved by the user. The AI never autonomously executes mutations. All AI-suggested changes are presented in an Approve/Reject interface, ensuring you maintain complete control over your accounts.

Data Sharing

We never sell your Google data. We never use your Google data for serving advertisements. Your data is only shared with subprocessors (like OpenAI for AI processing and Supabase for database storage) required to deliver the core functionality of Floating IQ.

Data Storage & Retention

Your Google OAuth tokens are encrypted at rest using AES-256 and stored securely in our database. We retain your cached Google data only as long as necessary to provide the service. If you disconnect your Google account, all associated OAuth tokens are revoked and deleted immediately, and cached data is deleted within 7 days.

Google Limited Use Policy

Revoking Google Access

You can revoke Floating IQ's access to your Google account at any time. To do so:

• From our App: Navigate to the Integrations page and click "Disconnect" on any connected Google service.
• From Google: Go to your Google Account Security settings and remove access for Floating IQ.

When you revoke access, we immediately delete all associated OAuth tokens and initiate the deletion of your cached Google data from our servers.

Explicit User Approval for Google Ads Mutations

Floating IQ NEVER performs Google Ads mutations automatically. Every action requires explicit user approval via an Approve/Reject UI before execution. Rejected or unapproved actions are never executed.

The following is a list of ALL supported mutations:

• Budget updates
• Campaign pause / resume
• Keyword pause / resume
• Negative keyword management
• Responsive Search Ad creation
• Geo targeting updates
• Smart bidding (Target CPA / Target ROAS) updates

How we use your data

• To run website audits, generate scores, and produce marketing recommendations
• To power AI analysis using OpenAI's API — your data is sent to OpenAI for processing
• To display dashboards showing your connected platform metrics
• To maintain your account and authenticate you
• To send service-related emails (never marketing without consent)
• To detect errors, improve reliability, and debug issues
• To comply with legal obligations

Public website processing and Business Memory

When you supply a business website during signup or workspace creation, request an audit or re-analysis, change the website, or explicitly request a refresh, we send its public URLs to Firecrawl to retrieve relevant public pages. This can include page text, links, titles and other metadata, and publicly listed contact and social information. The website-processing service does not receive your advertising-platform OAuth tokens or login credentials.

We use OpenAI's GPT-6 Luna to analyze the retrieved content and retain supported business facts and source evidence in your workspace's Business Memory. Your confirmed fields are preserved; conflicting website information becomes a suggestion. Ordinary chat messages use saved context and do not automatically start a new website scrape.

Firecrawl is a third-party processing provider. Its retention, processing and deletion practices depend on its terms and the applicable account settings. Our local cache expiry does not control Firecrawl's copies. We do not promise zero data retention or a particular processing location for Firecrawl. See Firecrawl's privacy policy.

Data storage

Your data is stored in Supabase (PostgreSQL), hosted on AWS infrastructure. We strictly manage OAuth tokens with the following practices:

• Both access tokens AND refresh tokens are stored to maintain your active connection.
• AES-256 encryption is used for all stored credentials.
• Tokens are deleted immediately and permanently upon account disconnect.
• No credentials are ever logged or exposed in plaintext.

Account authentication is handled by Firebase Authentication (Google); we verify Firebase-issued tokens on our backend and do not store your password. Our backend runs on Render. Our frontend is served as a static site. Both are hosted in the United States.

Data sharing

We share your data only with the following sub-processors, and only to deliver the service:

We may disclose data if required by law, court order, or to protect our rights or the safety of users.

Data retention

For the specific records removed when you disconnect Meta Ads, and workspace information retained separately, see Meta Platform Data.

• Account data: retained while your account is active, deleted within 30 days of account deletion request
• Audit results: retained for your account history, deleted with your account
• OAuth tokens: deleted immediately when you disconnect an integration
• Platform data (cached): deleted within 7 days of disconnection
• Website analysis cache: reused for up to one hour. Cached pages and website-analysis cooldown records become eligible for physical deletion after 24 hours. The backend checks at startup and every five minutes; outages, errors or large backlogs can delay deletion, and cleanup resumes when service recovers.
• Website-derived Business Memory and source evidence are separate from the temporary cache and remain until you edit them or delete the workspace/account. Successful account deletion removes all associated workspace website caches in the same database transaction.
• Usage logs: retained for 90 days for debugging purposes

Your rights

Depending on your location, you may have the following rights:

• Access — request a copy of all data we hold about you
• Correction — update inaccurate data
• Deletion — request deletion of your account and all associated data
• Portability — receive your data in a machine-readable format
• Objection — object to certain types of processing
• Withdrawal — disconnect any integration and revoke access at any time

To exercise any right, email us at the address in the Contact section. We will respond within 30 days.

Export Your Data

Users may request an export of their data at any time before deletion. Data exports include all provided account information, generated reports, and cached integrations data. Requests can be made by contacting us at floatingiq.22@gmail.com.

Security

We implement industry-standard security measures: OAuth tokens encrypted at rest, HTTPS-only connections, Supabase Row Level Security so users can only access their own data, and no storage of plaintext credentials.

No system is perfectly secure. If you discover a security vulnerability, please contact us immediately at the address below.

Cookies & local storage

We use only what is necessary to keep you signed in and remember basic preferences. Your authentication session is managed by Firebase, and we store lightweight preferences (such as your active workspace) in your browser's local storage. We do not use advertising cookies or third-party tracking pixels, and we do not use Google Analytics or similar tracking tools.

Children

Floating IQ is not directed at anyone under the age of 16. We do not knowingly collect data from children. If you believe we have collected data from a child, contact us and we will delete it immediately.

Changes to this policy

We may update this policy from time to time. We will notify you by email and update the "Last updated" date at the top of this page. Continued use of the service after changes constitutes acceptance of the new policy.

Contact us

For any privacy-related questions, data requests, or to report a concern: