Contract terms

Terms of Service

Terms of Service for Flapy, structured for an email SaaS product with OAuth access, third-party integrations, artificial intelligence, subscriptions and personal data processing.

Draft version

Last updated: April 26, 2026

Points to finalize before publication

  • Operator identity included: Geno studio Ltd, a company registered in England and Wales under number 17113844, registered office Suite 3H, The Old Courthouse, Chapel Street, Dukinfield, United Kingdom, SK16 4DT.
  • Complete before publication where required: legal representative, dedicated legal email, hosting provider details, tax or VAT number and any mandatory local notices.
  • Have these terms reviewed by legal counsel in the operator jurisdiction and in the markets targeted by Flapy.
  • Keep these terms aligned with the Privacy Policy, DPA, subprocessors list and Google/Microsoft OAuth configuration before public launch.
1

Operator identity

The Flapy service is published and operated by Geno studio Ltd, a company registered in England and Wales under number 17113844, with its registered office at Suite 3H, The Old Courthouse, Chapel Street, Dukinfield, United Kingdom, SK16 4DT.

Because the operator is registered in England and Wales, French company identifiers such as SIREN, RCS or French share-capital notices are not used. The applicable identifiers are the legal name, company number, registration jurisdiction and registered office.

Before publication, add any extra mandatory details required in the markets where Flapy is offered, such as a legal representative, legal contact email, hosting provider, tax identifiers or local notices.

2

Purpose of these terms

These Terms of Service govern access to and use of Flapy, a SaaS email assistance service that can connect Gmail or Outlook inboxes, classify conversations, prepare draft replies, track follow-ups and enrich answers with connected third-party tools.

Creating an account, completing an OAuth connection, using the application or subscribing to a plan means accepting these terms, subject to mandatory rules that may apply in the user jurisdiction.

3

Definitions

  • Service: the Flapy platform, website, web application, APIs and related features.
  • User: any natural person accessing the Service for themselves or on behalf of an organization.
  • Customer: the person or organization subscribing to or using the Service.
  • Customer Data: emails, contacts, drafts, account information, metadata, connected integration data and content entrusted to the Service.
  • Connectors: third-party integrations such as Gmail, Outlook, Shopify, Stripe, custom APIs or other tools enabled by the Customer.
4

User account and OAuth access

Access to the Service may require creating an account and connecting a Gmail or Outlook account through OAuth. Flapy should never request the raw password for an email inbox.

The User must have the rights needed to connect an inbox, prepare or send replies, activate connectors and process third-party data present in conversations.

The Customer remains responsible for internal access management, revoking accounts that no longer need the Service and protecting sessions, links and administrative credentials.

5

Service features

  • Email triage, categories, priorities and conversation processing states.
  • AI-assisted drafts, rewriting and answer improvement based on available context.
  • Connection to external sources when the Customer enables connectors for operational context.
  • Tone preferences, corrections, business rules and signals used to improve future drafts.
  • Automations, reminders, notifications and workflows depending on the subscribed plan.
6

Subscription, free trial and payment

Plans, prices, currencies, taxes, usage limits, commitment periods and included features are those shown on the pricing page or in the accepted quote.

Unless stated otherwise, subscriptions are billed in advance monthly or annually and may renew automatically until cancelled.

If a free trial is offered, the site or checkout flow must specify its duration, whether a payment card is required, whether billing starts automatically and how cancellation works.

Refunds, cancellations, plan changes, failed payments, late payments and suspension rules must be made clear before commercial launch.

7

Acceptable use

  • Do not use Flapy to send spam, unsolicited campaigns, misleading, fraudulent, unlawful, hateful, discriminatory or rights-infringing content.
  • Do not process sensitive or regulated data without the required legal basis, authorization and security framework.
  • Do not bypass technical limits, security, billing mechanisms, access controls or OAuth provider restrictions.
  • Do not connect accounts, shops, payment tools or data sources without sufficient authority.
  • Do not send AI-generated drafts without human review when a reply involves a commercial, legal, financial, medical, employment or otherwise sensitive decision.
8

Artificial intelligence and human validation

Flapy may use artificial intelligence models to classify, summarize, analyze or draft text. These outputs support writing and organization; they are not guaranteed final decisions.

The Customer and Users must review, correct and approve drafts before sending. Flapy does not guarantee that generated content is complete, accurate, appropriate or free of omissions.

Refunds, disputes, cancellations, personal data, contractual obligations, sensitive situations and policy exceptions require stronger human validation.

9

Personal data

Using Flapy may involve personal data such as User identity, connected emails, message contents, contacts, conversation metadata, generated drafts, preferences, support data, payment information and connector data.

For Customer Data and the Customer contacts, the Customer will usually act as controller and Flapy as processor, except for cases described in the Privacy Policy.

The Privacy Policy should describe purposes, legal bases, data categories, retention periods, recipients, international transfers, data subject rights and privacy contact details.

10

Google and Microsoft data

When a User connects Gmail or Outlook, Flapy may access data authorized through accepted OAuth scopes, such as profile, email address, messages, metadata, contacts and actions needed to prepare, modify or send drafts.

Flapy must limit use of Google and Microsoft data to visible Service features, must not sell that data, must not use it for targeted advertising and must limit human access to support, security, legal obligations or explicit Customer requests.

A User can revoke access from their Google or Microsoft account, but data already synchronized may remain for the periods described in the Privacy Policy unless an applicable deletion request is accepted.

11

Third-party connectors

The Customer may connect third-party services such as Shopify, Stripe or a custom API. These services remain subject to their own terms, privacy policies, usage limits, permissions and availability.

Flapy is not responsible for outages, restrictions, API changes, compliance decisions, fees or processing performed by third-party services outside Flapy reasonable control.

12

Data processing and DPA

When Flapy processes Customer Data on behalf of the Customer, the parties should enter into a data processing agreement or DPA that matches the applicable law.

The DPA should cover documented instructions, data categories, purposes, security measures, subprocessors, international transfers, assistance with rights requests and deletion or return of data.

Before public launch, publish or provide on request the active subprocessor list, including hosting, database, AI, email, payment, support, monitoring and transactional email providers.

13

Security and confidentiality

Flapy implements reasonable technical and organizational measures to protect Customer Data, including encrypted transport, access controls, logs, revocation mechanisms and encryption of OAuth secrets at rest where the architecture supports it.

The Customer must protect its own accounts, devices, Users and permissions, and must notify Flapy promptly of suspected unauthorized access, account compromise or misuse.

Non-public information exchanged through the Service is confidential unless disclosure is required by law, agreed in writing, needed to provide the Service or already public.

14

Cookies and trackers

Flapy may use cookies or similar technologies needed for authentication, security, language preference, Service operation or remembering a consent choice.

Non-essential trackers such as analytics, advertising, retargeting or social modules that set trackers require prior information and consent where applicable law requires it.

15

Intellectual property

Flapy, its interface, brands, logos, texts, visuals, components, models, code, methods and distinctive elements remain the property of the operator or its licensors.

The Customer keeps its rights in Customer Data and grants Flapy only the rights needed to host, process, analyze, transform, display and transmit that data to provide, secure, maintain and improve the Service under these terms and the Privacy Policy.

16

Availability, support and changes

Flapy aims to provide a reliable Service but does not guarantee uninterrupted availability unless a separate service level commitment applies.

The Service may evolve, be corrected, temporarily suspended or limited for maintenance, security, compliance, abuse, provider incidents or technical constraints.

17

Suspension and termination

Flapy may suspend or limit access in case of abusive use, security risk, breach of these terms, unpaid invoices, OAuth provider request, legal obligation or risk to third parties.

The Customer may cancel a subscription under the terms shown in the account, quote or commercial terms. The cancellation process, effective date, data handling and post-termination access period must be made clear before launch.

At the end of the contract, Flapy deletes or makes Customer Data unavailable according to the Privacy Policy and DPA, subject to backups, legal obligations, disputes and security logs.

18

Liability

Flapy provides a tool that assists email management. The Customer remains responsible for decisions, sent replies, commercial commitments, data, internal policies and compliance toward its own customers, prospects, employees and partners.

To the extent permitted by applicable law, Flapy is not liable for indirect losses, loss of revenue, loss of opportunity, reputational harm, Customer-controlled data loss or unreviewed errors in generated drafts.

Nothing limits liability that cannot be limited by law, including intentional misconduct, bodily injury, fraud or mandatory statutory obligations.

19

Consumers and regulated markets

Flapy is mainly designed for professional use. If the Service is offered to consumers or protected micro-businesses, additional information may be required, such as withdrawal rights, mediation, tax-inclusive prices, online cancellation, statutory guarantees and pre-contractual disclosures.

Before any B2C sale or regulated-market launch, verify the local obligations that apply to the operator country and to the residence country of targeted users.

20

Governing law and jurisdiction

These terms are governed by the law of England and Wales, unless mandatory rules require otherwise for certain users.

Any dispute relating to these terms or the Service is subject to the competent courts of England and Wales, subject to mandatory protective rules that may apply.

Additional documents to prepare

These Terms of Service should be published with a complete Privacy Policy, a DPA for professional customers, a subprocessor list, a cookie notice and legal identification adapted to Geno studio Ltd and its registration in England and Wales.

Ready to try Flapy?

Free 7-day trial, cancel anytime