FLOARO
Privacy Policy
Effective and last updated: August 25, 2026
This Policy explains how Floaro collects, uses, discloses, retains, and protects personal information across its website, SaaS platform, marketplace integrations, AI features, and the Floaro integration for ChatGPT and Codex.
1. Who We Are and Scope
Floaro LLC ("Floaro," "we," "us," or "our") provides marketplace-management software, listing tools, analytics, integrations, AI-assisted features, and related services. This Privacy Policy applies when you use floaro.com, dashboard.floaro.com, the Floaro SaaS platform, Floaro marketplace connections, public store-audit tools, support services, and the Floaro integration made available through ChatGPT and Codex (collectively, the "Services").
For personal information processed through the Services, Floaro generally acts as the business or controller. In some business-account and team contexts, Floaro may process information on behalf of the subscribing company, which may separately act as controller.
2. Information We Collect
2.1 Account, company, and team information
We collect information used to create and administer a Floaro account, including name, email address, company name, role, account preferences, team membership, permissions, authentication records, and communications preferences. Passwords are stored only in protected hashed form; Floaro personnel cannot retrieve the original password.
2.2 Marketplace and commerce information
When you connect an authorized marketplace account, such as eBay, we may collect or receive marketplace account identifiers, seller and store names, marketplace region, authorization tokens, connection status, product and variation data, listing content and status, images, inventory, pricing, policies, orders, order items, sales totals, payment and fulfilment status, cancellation status, and related marketplace records.
Order records may include buyer or recipient information supplied by the marketplace, such as a buyer username, name, email address, telephone number, and delivery address, where available and necessary for order management. Floaro limits access to this information according to the authenticated user’s company, role, and assigned marketplace accounts.
2.3 Content you provide
We collect product titles, descriptions, item specifics, images, templates, policies, prompts or instructions submitted to AI features, files, support messages, and other content you create, upload, import, or ask Floaro to process.
2.4 Billing information
We collect subscription, invoice, transaction, billing-contact, and payment-status information. Payment-card and payment-account details are processed by our payment providers. Floaro does not store complete payment-card numbers or card security codes on its own servers.
2.5 Website, device, and usage information
We may collect IP address, browser and device type, operating system, approximate location derived from IP address, login times, pages or features used, referral source, cookie identifiers, error information, security events, and request metadata. We use this information for authentication, fraud prevention, security, service operation, analytics, and improvement.
2.6 Public eBay store-audit information
If you use a public eBay store-analysis or audit feature, we process the store URL, seller name or identifier, publicly available listing information, analysis results, and any email address you provide to receive a report or follow-up information.
2.7 Support and business communications
We collect the contents of support tickets, emails, contact forms, survey responses, and other communications, together with relevant account and technical information needed to investigate and respond.
3. How and Why We Use Information
We use personal information to:
- Create, authenticate, secure, and administer accounts and team access.
- Connect authorized marketplace accounts and synchronize products, listings, inventory, policies, orders, and sales information.
- Provide dashboards, reports, templates, product-management features, marketplace publishing functions, and requested integrations.
- Respond to user requests made through the Floaro integration for ChatGPT and Codex.
- Generate and improve AI-assisted product content when a user chooses to use an AI feature.
- Process subscriptions, invoices, payments, credits, and service entitlements.
- Provide support, troubleshoot errors, communicate service notices, and respond to enquiries.
- Protect Floaro, users, marketplaces, and third parties; prevent fraud, abuse, and unauthorized access; and enforce our terms.
- Measure service performance, understand feature usage, and improve reliability and usability.
- Send marketing communications where permitted, subject to your choices.
- Comply with applicable law, legal process, tax obligations, and regulatory requirements.
4. Floaro Integration with ChatGPT and Codex
4.1 How the integration works
The Floaro integration is an authenticated, read-only connection that allows a user to ask ChatGPT or Codex for information held in the user’s authorized Floaro account. When the user invokes a Floaro tool, OpenAI sends Floaro an authenticated tool request. Floaro verifies the user and their permissions, retrieves only the information needed for that request, and returns a structured response to OpenAI so it can present the result in the conversation.
Using the Floaro integration does not give Floaro access to the user’s OpenAI password, ChatGPT password, API keys, multi-factor authentication codes, or full ChatGPT/Codex conversation history. Floaro receives only the tool request and parameters that OpenAI sends for the selected Floaro function. The current integration cannot create, edit, publish, cancel, refund, or delete marketplace data.
4.2 Current tool inputs and outputs
Depending on the request, tool inputs may include a date range, marketplace-account selection, product or listing identifier, order identifier, status filter, search term, sort preference, page number, or result limit. Outputs are limited to information relevant to the user’s request and authorization.
| Floaro tool | Typical inputs | Data returned |
|---|---|---|
| floaro_account | Authenticated account context; no marketplace credentials. | Authorized account, company, plan or account-status summary. |
| floaro_marketplace_accounts | Optional account or status filtering. | Connected marketplace names, seller/store identifiers, regions, connection status, and authorized account totals. |
| floaro_product_summary | Optional marketplace account and product/listing status filters. | Product totals and available status or listing breakdowns. |
| floaro_order_summary | Date range and optional marketplace account or order-status filters. | Order and sales totals, date range, currency/status breakdowns, and marketplace-level summaries. |
| floaro_orders | Date range, marketplace account, status, search, sorting, pagination, and result limit where supported. | A limited list of authorized orders, including order reference, date, store, totals, currency, and status information. |
| floaro_order | An order identifier or reference. | Authorized order details, which may include items, quantities, amounts, marketplace, payment, fulfilment and cancellation status, and limited buyer or delivery data when available and necessary. |
| floaro_product_sales | Date range and optional product or marketplace-account filters. | Product titles or identifiers, quantity sold, sales totals, and originating marketplace account. |
4.3 Data not returned by the integration
Floaro does not return passwords, marketplace OAuth tokens, API secrets, payment-card data, internal database credentials, or information belonging to another company or an unauthorized marketplace account. Floaro also seeks to exclude internal diagnostic identifiers and unnecessary buyer information from tool responses.
4.4 OpenAI as a recipient
OpenAI receives the Floaro tool request and response at the user’s direction so that ChatGPT or Codex can answer the user. OpenAI processes that information under its own terms, privacy policy, workspace settings, and retention controls. Floaro does not control how a user’s ChatGPT or Codex conversation is retained by OpenAI. Users should review the applicable OpenAI privacy and data-control information before installing or using the integration.
4.5 MCP request logging and retention
Floaro does not maintain a separate history of ChatGPT/Codex conversations and does not intentionally store raw ChatGPT/Codex prompt text or complete Floaro tool-response bodies as a plugin conversation history. Tool requests and responses are processed transiently to complete the request. Limited server and security logs may record the request time, route or tool name, authenticated Floaro account or company identifier, IP address, response status, duration, and error information. These logs are retained for up to 30 days, unless a specific security incident, legal obligation, or dispute requires longer retention.
4.6 User controls for the integration
A user may stop the data flow by disconnecting or removing Floaro in ChatGPT/Codex, revoking Floaro’s authorization from the relevant OpenAI account or workspace, signing out, or asking Floaro Support to revoke the integration. Revocation prevents new tool requests but does not automatically delete information already retained in the user’s OpenAI conversation history. Users must use the controls provided by OpenAI to manage those conversations.
5. AI-Assisted Features
When a user chooses an AI-assisted feature, Floaro may send the user’s instructions and the minimum product or listing information needed to an AI service provider to generate titles, descriptions, item specifics, recommendations, or other requested content. Floaro does not intentionally send marketplace passwords, payment-card data, or unrelated account information to AI providers. AI-generated content may be inaccurate and should be reviewed before use or publication.
6. Legal Bases for Processing
Where applicable law requires a legal basis, Floaro relies on one or more of the following: performance of a contract to provide the Services; legitimate interests in operating, securing, supporting, and improving the Services; consent for optional integrations, cookies, or marketing where required; and compliance with legal obligations. Where processing is based on consent, you may withdraw consent at any time without affecting processing already performed lawfully.
7. How We Disclose Information
We disclose personal information only as reasonably necessary for the purposes described in this Policy, including to:
- OpenAI, when you invoke the Floaro integration through ChatGPT or Codex, as described in Section 4.
- Authorized marketplaces such as eBay, to connect accounts and perform marketplace functions that you request through Floaro.
- Cloud hosting, database, content-delivery, monitoring, backup, and security providers that operate Floaro infrastructure.
- AI service providers when you use an AI-assisted feature.
- Payment processors, banks, accounting providers, and fraud-prevention services for billing and financial administration.
- Email, customer-support, analytics, and communications providers supporting Floaro’s operations.
- Your company owner, administrators, and authorized team members according to account permissions.
- Professional advisers, auditors, insurers, and legal authorities where necessary to protect rights, comply with law, or respond to valid legal process.
- A buyer, successor, or relevant advisers in connection with a merger, financing, reorganization, acquisition, or sale of all or part of Floaro, subject to appropriate safeguards.
Floaro does not sell personal information for money. Subject to applicable law, consent requirements, and cookie choices, Floaro may disclose online identifiers and website activity to analytics and advertising providers for measurement, attribution, audience insights, or relevant advertising. Some U.S. state privacy laws may define these disclosures as "sharing" or use for targeted advertising. Where required, users may opt out through available cookie controls, browser-based signals that Floaro is legally required to recognize, or by contacting us.
8. Data Retention
Floaro retains information only for the periods below, unless a longer period is required by law, necessary to establish or defend legal claims, requested by the user, or needed to investigate fraud or a security incident. When a retention period expires, information is deleted, anonymized, or isolated from active use.
| Category | Retention period |
|---|---|
| Account, company, team, product, listing, inventory, template, and marketplace data | For the active account or connection, then deleted from active systems within 30 days after verified account deletion or applicable disconnection. |
| Marketplace authorization tokens | For the duration of the authorized connection; revoked or removed from active use promptly after disconnection and no later than 30 days afterward. |
| Orders, invoices, transaction, tax, and accounting records | Up to 7 years after the relevant transaction or as otherwise required by applicable financial and tax law. |
| ChatGPT/Codex tool inputs and response bodies | Processed transiently; not retained as a separate Floaro plugin conversation history. |
| MCP and general security/access logs | Up to 30 days, unless associated with an active security investigation, legal obligation, or dispute. |
| AI inputs and generated outputs stored in a Floaro account | For the life of the account and deleted from active systems within 30 days after verified account deletion, unless the user deletes them earlier where available. |
| Support tickets and customer-service communications | Up to 3 years after the ticket or enquiry is closed. |
| Website analytics data | Up to 14 months, unless a shorter period is configured or the data is aggregated or anonymized. |
| Marketing contact data | Until consent is withdrawn or the user opts out; a minimal suppression record may be kept for up to 5 years to honour the opt-out. |
| Backups | Removed or overwritten within 90 days after deletion from active systems, unless preservation is legally required. |
9. Security
Floaro uses administrative, technical, and organizational safeguards designed to protect personal information, including access controls, role-based authorization, encryption in transit, protected credentials, monitoring, backups, and security procedures. No system is completely secure, and we cannot guarantee that unauthorized access, loss, or misuse will never occur. Users are responsible for protecting their credentials and promptly reporting suspected unauthorized access.
10. International Data Transfers
Floaro and its service providers may process information in the United States and other countries that may have different data-protection laws from your country. Where required, Floaro uses appropriate safeguards for international transfers, such as contractual protections, data-processing agreements, and other legally recognized mechanisms.
11. Cookies and Similar Technologies
Floaro uses essential cookies for authentication, security, sessions, and core functionality. Subject to applicable law and user choices, we may also use functional, analytics, and performance cookies to remember preferences, understand usage, and improve the Services. More information is available in Floaro’s Cookie Policy. Browser settings and any cookie controls presented by Floaro may be used to manage non-essential cookies.
12. Your Privacy Rights and Choices
Depending on your location and subject to applicable exceptions, you may have the right to access, correct, delete, restrict, or object to processing of personal information; receive a portable copy; withdraw consent; opt out of marketing; and complain to a data-protection authority. Residents of certain U.S. states may also have rights to know, correct, delete, or obtain a copy of personal information and to opt out of sale, sharing, targeted advertising, or certain profiling. Floaro does not discriminate against users for exercising applicable privacy rights.
You can manage certain information through your Floaro account, disconnect marketplace accounts, remove team access, unsubscribe from marketing emails, disconnect Floaro from ChatGPT/Codex, or contact us at info@floaro.com. We may need to verify your identity and authority before completing a request. An authorized agent may submit a request where permitted by law, but we may require proof of authorization.
13. Marketplace and Third-Party Services
Marketplace providers, OpenAI, payment processors, and other third-party services have their own privacy practices. When you connect or use those services, their terms and privacy policies also apply. Floaro is not responsible for third-party websites or services that it does not control. Disconnecting a third-party integration in Floaro stops future access through that connection but may not delete information held independently by the third party.
14. Children’s Privacy
Floaro accounts and commercial marketplace-management Services are intended for business users who are at least 18 years old or the age of legal majority in their jurisdiction. Floaro does not knowingly collect personal information from children under 13. If we learn that personal information was collected from a child in violation of applicable law, we will take reasonable steps to delete it. The Floaro integration does not contain mature or adult content, but account eligibility requirements still apply.
15. Changes to This Policy
We may update this Privacy Policy to reflect changes in the Services, integrations, law, or data practices. We will publish the updated Policy on this page and change the effective date. Where required, we will provide additional notice or request consent before a material change takes effect.
16. Contact Us
Questions, requests, or complaints about this Privacy Policy or Floaro’s handling of personal information may be sent to:
Floaro LLC
5811 Pelican Bay Blvd
Naples, Florida 34108
United States
Email: info@floaro.com
Website: https://www.floaro.com
Individuals in the European Economic Area or United Kingdom may also lodge a complaint with their local supervisory authority. We encourage you to contact Floaro first so we can try to resolve the concern.
