Legal
Last updated: 30 July 2026
This Privacy Policy explains how we collect, use, disclose, retain and protect personal data when you visit floneo.co, join the waitlist, request a demo, contact us, create an account, use FloNeo, make a payment, receive marketing, apply for a role or otherwise interact with us.
We collect only the data needed to operate, secure, improve, and support FloNeo. We do not sell personal data. Payment card details are handled by our payment provider, not stored by FloNeo. Private project content is not used to train general-purpose models unless we clearly tell you and obtain any permission required by law. You can unsubscribe from marketing and request access, correction, or deletion of your data.
FloNeo Technologies Pvt. Ltd. ("FloNeo", "we", "us" or "our") provides an AI app builder, low-code/no-code application platform, workflow automation, visual editing, integrations, deployment and related services. Our registered address is Door No. 1-650, Thazham North, Kollam, Kerala 691572, India. Our privacy and grievance contact is admin@floneo.co.
This Policy applies to:
When a business customer uses FloNeo to collect or manage personal data inside an application, workflow, database, or integration, the customer normally determines why and how that data is used. In that situation, the customer is the data controller/data fiduciary and FloNeo acts as its processor/service provider. Requests about personal data held in a customer-built application should usually be directed to that customer. Our processing is governed by the customer agreement and, where applicable, a data processing agreement.
| Category | Examples |
|---|---|
| Contact and waitlist data | Name, work email, phone number, company, role, country, interests, referral source, campaign/UTM data, consent choices, and communications. |
| Account and profile data | Login details, profile information, organisation, workspace membership, permissions, subscription, account settings, and authentication records. |
| Project and application content | Prompts, clarifying answers, files, logos, colour choices, generated pages, workflows, schemas, code, databases, app content, test data, versions, exports, and deployment configuration. |
| Usage and technical data | IP address, device/browser type, operating system, session identifiers, timestamps, pages and features used, clickstream, crash reports, diagnostics, security logs, and approximate location derived from IP. |
| Billing and transaction data | Plan, invoices, payment status, tax details, transaction reference, billing contact, and limited payment metadata. FloNeo does not store complete card or bank credentials. |
| Support and communications | Support tickets, emails, calls, meeting notes, product feedback, bug reports, survey responses, and attachments. |
| Marketing and community data | Newsletter preferences, campaign engagement, event participation, WhatsApp opt-in, social-media interactions, and community activity. |
| Recruitment data | CV, portfolio, education, work history, interview notes, compensation expectations, references, and verification documents where required. |
| Purpose | What we do | Legal basis / ground |
|---|---|---|
| Provide the website and platform | Create and manage accounts; process prompts; generate, edit, store, export, and deploy applications; run workflows; provide integrations; and deliver requested features. | Contract, consent, and other grounds permitted by applicable law. |
| Operate the waitlist and launches | Record interest, send launch updates, manage beta access, attribute campaigns, prevent duplicates, and prioritise relevant product information. | Consent or legitimate/business interest where permitted. |
| Support and communicate | Answer questions, troubleshoot, handle complaints, provide onboarding, deliver notices, and maintain service communications. | Contract and legitimate/business interest. |
| Process payments and subscriptions | Create invoices, confirm payments, manage plans and credits, prevent fraud, and meet accounting and tax obligations. | Contract and legal obligation. |
| Secure FloNeo | Authenticate users, control access, monitor misuse, investigate incidents, maintain logs, prevent fraud, and protect users, systems, and data. | Legitimate/business interest and legal obligation. |
| Improve the product | Analyse feature use, reliability, performance, errors, feedback, and aggregate trends; test new features; and improve usability. | Legitimate/business interest, consent where required, and contractual necessity. |
| Marketing | Send newsletters, product updates, events, case studies, and relevant offers; measure campaign performance; and manage WhatsApp or email opt-ins. | Consent or legitimate/business interest where permitted. |
| Recruitment and partnerships | Assess candidates, manage interviews, verify information, communicate about opportunities, and manage partner relationships. | Consent, contract steps, legitimate/business interest, and legal obligation. |
| Legal and compliance | Enforce agreements, respond to lawful requests, protect rights, maintain records, and comply with applicable law. | Legal obligation and legitimate/business interest. |
FloNeo processes prompts, clarifying answers, application structure, selected project context, and outputs to provide AI-assisted generation and editing. Depending on the feature and deployment, this processing may be performed by FloNeo systems or by third-party AI providers acting as service providers.
FloNeo does not use website or standard product data to make solely automated decisions about individuals that produce legal or similarly significant effects. If that changes for a specific feature, we will provide a separate notice and any required controls.
FloNeo uses cookies and similar technologies to operate the website, keep sessions secure, remember preferences, understand performance, measure campaigns, and improve user experience.
Cookie choice: Where required, non-essential cookies will not be activated until you provide consent. You can change your choices through the website cookie settings and can also control cookies through your browser. Blocking some cookies may affect functionality.
| Type | Purpose | Control |
|---|---|---|
| Strictly necessary | Authentication, security, load balancing, session management, consent preferences, and essential site functions. | Used where needed to provide the service. |
| Analytics | Page views, traffic sources, engagement, errors, and performance. This may include Google Analytics or equivalent tools. | Used only with consent where required. |
| Marketing and attribution | Campaign source, retargeting, ad measurement, and conversion attribution. | Used only with consent where required. |
| Functional | Remembered settings, embedded media, support widgets, and communication preferences. | Used according to the feature and consent requirements. |
We share personal data only when reasonably necessary for the purposes described in this Policy.
| Recipient category | Reason |
|---|---|
| Hosting and infrastructure providers | Cloud hosting, storage, content delivery, monitoring, backups, and security. |
| AI and software providers | Prompt processing, code or content generation, model routing, diagnostics, and product functions. |
| Customer relationship and communication tools | HubSpot or equivalent CRM, email services, Waplify/WhatsApp where enabled, support tools, and meeting services. |
| Analytics and marketing providers | Google Analytics, Google Tag Manager, Search Console, advertising and campaign-measurement tools where enabled and permitted. |
| Payment providers | Razorpay or another approved payment processor for payment authorisation, transaction processing, refunds, fraud prevention, and regulatory checks. |
| Professional advisers | Lawyers, accountants, auditors, insurers, and security specialists. |
| Authorities and legal recipients | Courts, regulators, law enforcement, tax authorities, or other parties where disclosure is required or legally justified. |
| Corporate transactions | A buyer, investor, lender, or adviser in connection with a merger, financing, restructuring, acquisition, or sale, subject to appropriate confidentiality and legal safeguards. |
We do not sell personal data — FloNeo does not sell personal data for money. If an advertising or analytics practice is treated as a "sale" or "sharing" under an applicable law, we will provide any legally required notice and opt-out control.
Payments may be processed through Razorpay or another approved payment provider. The payment provider collects and processes card, bank, UPI, or other payment credentials under its own privacy terms and security controls. FloNeo receives transaction references, payment status, billing details, and limited metadata needed to activate services, issue invoices, process refunds, prevent fraud, and maintain financial records. FloNeo does not store complete payment-card numbers or security codes.
FloNeo is based in India and may use service providers or infrastructure located in India and other countries. Those countries may have different data-protection laws. Where required, we use contractual, organisational, and technical safeguards for international transfers, such as approved contractual clauses, transfer assessments, access controls, encryption, and provider due diligence.
We may retain de-identified or aggregated information that cannot reasonably identify an individual. We may also retain data longer where necessary to comply with law, preserve evidence, investigate abuse, enforce agreements, or protect legal rights.
| Data category | Typical retention |
|---|---|
| Waitlist and marketing records | Until you unsubscribe, withdraw consent, or remain inactive for 24 months, unless a longer period is required to document consent or resolve a dispute. |
| Account and profile data | While the account is active and generally up to 90 days after closure, except for records needed for security, disputes, legal compliance, or recovery. |
| Project and application content | While required to provide the service. Following account closure or deletion, active copies are generally deleted or de-identified within 90 days; encrypted backups may remain for up to 180 days before cycling out. |
| Usage and security logs | Generally up to 12 months, or longer where required for an active security investigation, legal claim, or compliance obligation. |
| Support communications | Generally up to 3 years after the ticket or relationship closes, unless a shorter period is appropriate or longer retention is required for a dispute. |
| Billing, tax, and accounting records | For the period required by applicable tax, accounting, corporate, and anti-fraud laws. |
| Recruitment data | Generally 12 months after the recruitment process, unless you consent to longer retention or law requires otherwise. |
FloNeo uses reasonable technical and organisational measures designed to protect personal data against unauthorised access, alteration, loss, misuse, or disclosure. Measures may include:
No system is completely secure. You are responsible for protecting your account credentials, using strong authentication, limiting the personal data placed in test environments, and promptly reporting suspected misuse.
Depending on your location and the applicable law, you may have the right to:
Email admin@floneo.co with the subject "Privacy Request". Describe your request and the account, email address, or interaction it relates to. We may need to verify your identity and authority before acting. We will respond within the period required by applicable law.
You can unsubscribe using the link in an email, reply STOP or use the provided opt-out method for eligible WhatsApp communications, change available account preferences, or contact us. Service, security, billing, and legal notices may still be sent when necessary.
Please contact FloNeo first so we can investigate. You may also complain to the Data Protection Board of India or another competent supervisory authority where you live or work, where applicable.
FloNeo is not directed to children under 18. A person under 18 should not create an account or submit personal data unless FloNeo has implemented the required age-verification and verifiable parental-consent process for that service. If we learn that a child's data was collected without the required authorisation, we will take reasonable steps to delete or restrict it.
FloNeo may link to or integrate with third-party websites and services. Their privacy practices are governed by their own notices. Review those notices before authorising an integration or sending data to a third party. Disconnecting an integration stops future transfers through FloNeo but may not delete data already received by the third party.
We may update this Policy when our products, providers, business model, or legal obligations change. We will post the revised version with a new "Last updated" date. If a change materially affects how we use personal data, we will provide an additional notice or request new consent where required.
For business-customer application data, please identify the relevant customer organisation or workspace. For security incidents, include the date, affected account, and a concise description, but do not email passwords or full payment-card details.
© 2026 FloNeo. All rights reserved.
