Draft for review, not yet in effect

Version 0.1 · 17 October 2026

This document is a working draft for review by Magynta's management and legal counsel. It does not bind anyone yet and is not legal advice. Highlighted items are still to be confirmed.

Legal

Terms of Service

Version 0.1 · Draft of 17 October 2026

These Terms of Service ("Terms") govern access to and use of Feldr, provided by Magynta Technologies Private Limited ("Magynta", "we", "us" or "our"). They apply between Magynta and the organisation that signs up for Feldr or signs an order form for it (the "Customer" or "you").

By starting a free trial, signing an order form, or clicking to accept these Terms, the person doing so confirms that they have authority to bind the Customer. If they do not have that authority, they must not use Feldr.

1. Definitions

  • "Service": the Feldr browser extension for Chrome, Firefox and Edge (the "Extension"), the Feldr admin dashboard, the Feldr API, and any related documentation and support.
  • "Customer Data": personal data and other data that the Service processes on the Customer's behalf, described in the Data Processing Agreement ("DPA").
  • "End User": a person the Customer allows to use the Extension or the dashboard, usually an employee or contractor.
  • "Admin": an End User with access to the Customer's Feldr dashboard.
  • "Order Form": an order, quote or online sign-up that names the plan, the number of seats, the billing period and the price.
  • "Seat": one End User protected by the Extension during the Subscription Term.
  • "Subscription Term": the period of a paid plan stated in the Order Form, including renewals.

2. Accounts and organisations

The Customer creates an organisation in Feldr and invites its Admins and End Users. The Customer is responsible for who it invites, for the accuracy of the information it gives us, and for everything done under its accounts.

Every Admin must sign in with a password and multi-factor authentication. On the Business and Enterprise plans the Customer may also connect its Microsoft or Google single sign-on and SCIM provisioning. Admins must keep their credentials confidential and tell us promptly of any unauthorised use.

An organisation is linked to the email domains it controls. A domain other than the signing-up Admin's own is added only through Feldr support, so that one organisation cannot claim another's people.

The Customer decides how Feldr is configured: which rules and frameworks are on, whether a finding is blocked, warned about or allowed, and who can see incidents. The Customer is responsible for informing its End Users that Feldr is in use and for any notices or consents its own law requires towards them.

3. Plans, free trial and seats

Feldr is sold per user per month in US dollars. The plans are Team, Business and Enterprise, with the features listed on the pricing page at the time of the Order Form:

  • Team

    Monthly billing
    $5.25 per user per month
    Annual billing
    $4.20 per user per month, billed annually
    Minimum
    10 seats
    Incident history kept
    90 days

  • Business

    Monthly billing
    $10.50 per user per month
    Annual billing
    $8.40 per user per month, billed annually
    Minimum
    25 seats
    Incident history kept
    1 year

  • Enterprise

    Monthly billing
    Contact sales
    Annual billing
    Contact sales
    Minimum
    500 seats
    Incident history kept
    the period in the contract

3.1 Free trial

Team and Business start with a 14-day free trial for the organisation, with the features of the chosen plan. The trial is free of charge and provided "as is" (section 12 applies in full).

Before the trial ends, the organisation's Admins receive one reminder email.

When a trial ends without a paid plan, protection stops. The Extension no longer checks prompts or files, and it tells each End User clearly that Feldr is not protecting them. Text and files are then sent to AI sites without any check by Feldr. The Customer is responsible for any data its End Users send after protection has stopped. Protection resumes when a paid plan starts. [OWNER TO CONFIRM: how long the organisation's settings and incident history are kept after an unpaid trial ends before they are deleted]

3.2 Seats

The Customer buys a number of seats, at least the plan's minimum (Team 10, Business 25; Enterprise as quoted).

Admins are warned when the organisation uses 90% of the seats bought. Up to 10% more End Users than seats bought are allowed for a grace period of 14 days. After the grace period no new End Users can be added until more seats are bought; End Users already added stay protected.

[OWNER TO CONFIRM: whether seats used above the number bought during the grace period are invoiced, and at what price]

3.3 Changing plans

The Customer may move between plans and add seats during the Subscription Term. A feature used beyond the Customer's plan is reviewed by Feldr support case by case; nothing is switched off automatically without notice.

[OWNER TO CONFIRM: how upgrades, downgrades and seat reductions are priced mid-term (pro rata or from the next billing period), and whether seats can be reduced before the term ends]

4. Fees, billing and taxes

Fees are per seat per month in US dollars, billed monthly or annually. Annual billing costs 20% less per month than monthly billing. Enterprise prices, volume pricing and invoice terms are set in the Order Form.

Payment is by bank transfer against our invoice. Card payments may be offered later. [OWNER TO CONFIRM: payment method (plan decision 12 / story 91.14), invoice due date (for example 30 days), currency of the bank account, and late-payment interest or fees]

Fees exclude taxes. The Customer pays any applicable taxes, such as GST or VAT, other than taxes on our income. [OWNER TO CONFIRM: tax treatment for customers in India and in each GCC country, including reverse charge and withholding tax]

Fees are non-refundable except where these Terms or the Order Form say otherwise. [OWNER TO CONFIRM: refund policy, including for annual plans cancelled early]

We may change our list prices with at least [OWNER TO CONFIRM: notice period, for example 30 days] notice. A change applies from the Customer's next renewal, not during a paid Subscription Term.

5. Acceptable use

The Customer and its End Users must not:

  • use the Service in breach of any law, including data protection, employment and export-control laws;
  • copy, modify, reverse engineer, decompile or create derivative works of the Service, except where the law allows it despite this restriction;
  • probe, scan or test the Service's security without our written permission, or bypass its access controls or usage limits;
  • access another organisation's data, or attempt to;
  • resell, sublicense or provide the Service to third parties, unless agreed in writing;
  • use the Service to build a competing product, or to benchmark it publicly without our consent;
  • upload malicious code, or interfere with the Service or its infrastructure;
  • send content through the Service (for example a "Send anyway" reason or a request typed in the Extension) that is unlawful or infringes others' rights.

End Users may be offered a choice to send content anyway after a warning. The Customer's rules decide when that choice exists, and the Customer is responsible for that content.

6. Customer data and confidentiality

6.1 What the Service processes

The Extension checks text, pasted content and attached files on the End User's device. Prompt text, file contents and the full detected values are never sent to Magynta. When a check finds sensitive data, the Extension sends an incident record: the kind of data found (the rule's label), a masked preview that contains no character of the value, the file name if a file was involved, the AI site, the End User's email, the browser, the outcome and any reason the End User gave. The full list is in the Privacy Policy and the DPA, Annex 1.

6.2 Ownership and use

The Customer owns Customer Data. We process it only to provide, secure and support the Service, as instructed by the Customer and as set out in the DPA, which forms part of these Terms. We do not sell Customer Data and do not use it for advertising.

We may use aggregated service metrics that identify neither the Customer nor any person (for example counts of detections per rule) to operate and improve the Service. [OWNER TO CONFIRM: whether masked false-positive feedback (the masked shape and model features of a finding an Admin marks as a false positive) may be used to improve detection for all customers, or only for the Customer]

6.3 Confidentiality

Each party keeps the other's confidential information confidential, uses it only for this agreement, and shares it only with its staff, contractors and advisers who need it and are bound by similar duties. This does not apply to information that is public through no fault of the receiving party, was already known to it, is independently developed, or must be disclosed by law (with notice to the other party where lawful).

These duties last during the agreement and for [OWNER TO CONFIRM: number of years] after it ends, and for trade secrets as long as they remain trade secrets.

6.4 Security

We protect Customer Data with the measures in the DPA, Annex 2, including encryption in transit (TLS), encryption of stored secrets, multi-factor authentication for Admins, and an audit log of Admin actions.

7. Service availability and support

Our target is 99.5% monthly availability of the Feldr API and dashboard, excluding planned maintenance announced in advance. Detection runs in the browser: if the API cannot be reached, the Extension keeps checking prompts with the organisation's last rules and sends incident records once the API is back.

This target is not a service-level agreement and gives no service credits unless an Order Form says so. [OWNER TO CONFIRM: whether Business has a contractual uptime commitment and service credits]

The 99.9% uptime service-level agreement listed for Enterprise applies only when it is written into the Customer's Order Form. [OWNER TO CONFIRM: Enterprise 99.9% SLA terms and service credits; this depends on the high-availability work (go-live 91.1 to 91.2), which is parked]

Support is by email, Sunday to Thursday, 09:00 to 18:00 Gulf Standard Time, except public holidays. Our first-response targets are: Critical, 4 working hours; High, 1 working day; Normal, 2 working days. Business has priority support; Enterprise support is as contracted. [OWNER TO CONFIRM: support email address (support@magynta.com does not exist yet) and the public holidays observed]

We may change the Service, for example to add AI sites, rules or features, or to follow changes made by browsers and AI sites. We will not materially reduce the core protection of a paid plan during its Subscription Term.

8. What Feldr can and cannot do

Feldr reduces the risk of sensitive data reaching AI assistants. It does not remove that risk. In particular:

  • detection uses rules and an on-device model and can miss data or flag data that is not sensitive;
  • Feldr protects only the AI sites and browsers listed in the documentation, and only where the Extension is installed and signed in;
  • Microsoft Edge does not allow extensions on Microsoft Copilot, so in Edge Feldr can block Copilot but cannot check prompts there; Copilot is protected in Chrome and Firefox;
  • assistants built into AI browsers, desktop apps and mobile apps are outside the Extension's reach;
  • AI sites change their pages, and protection on a site may be interrupted until we adapt the Extension;
  • an End User who removes the Extension, or whose trial or subscription has ended, is not protected (the Customer is told when the Extension is removed).

The Customer remains responsible for its own data-protection programme, policies and training.

9. Suspension and termination

9.1 Term

These Terms apply from the start of the trial or the Order Form until all Subscription Terms have ended. A Subscription Term renews for the same period unless either party gives notice before the renewal date. [OWNER TO CONFIRM: whether plans renew automatically, and the notice period for non-renewal]

9.2 Suspension

We may suspend the Service, wholly or for some End Users, if: an invoice is unpaid [OWNER TO CONFIRM: number of days] days after its due date and after written notice; the Customer or its End Users breach section 5; or suspension is needed to prevent a security threat or comply with law. We will give notice beforehand where reasonable, limit the suspension to what is needed, and restore the Service once the reason is resolved.

During a suspension, protection stops as described in section 3.1.

9.3 Termination

Either party may end the agreement by written notice if the other materially breaches it and does not cure the breach within [OWNER TO CONFIRM: cure period, for example 30 days] of notice, or becomes insolvent.

[OWNER TO CONFIRM: whether the Customer may terminate for convenience, and whether prepaid fees are refunded in that case]

9.4 Data at the end

During the Subscription Term Admins can export incidents (CSV and PDF reports) and, on Business and Enterprise, the audit log. After the agreement ends the Customer may request an export for [OWNER TO CONFIRM: export window, for example 30 days]. We then delete Customer Data as set out in the DPA, section 13, except where the law requires us to keep it.

Sections 4 (unpaid fees), 6.3, 9.4, 10, 12, 13, 14, 15 and 17 survive termination.

10. Intellectual property

Magynta and its licensors own the Service, including the Extension, its detection rules and models, the dashboard and the documentation. During the Subscription Term we grant the Customer a non-exclusive, non-transferable right to use the Service for its internal business purposes under these Terms. No other rights are granted.

The Customer owns its Customer Data and its own rules and settings. If the Customer gives us feedback or suggestions, we may use them freely without obligation.

The names Feldr and Magynta and their logos are our trademarks. Third-party product names (for example ChatGPT, Copilot, Chrome) belong to their owners and are used only to describe compatibility.

11. Third-party services

The Service works with services we do not control: the AI sites it protects, browsers and their extension stores, and services the Customer connects (Microsoft or Google sign-in, SCIM, Slack, Microsoft Teams and webhook alerts). The Customer's use of those services is governed by their own terms. We are not responsible for them, and a change by one of them may affect the Service (section 8).

12. Warranties and disclaimer

We warrant that, during a paid Subscription Term, the Service will perform materially as described in its documentation and that we will not materially decrease its security. If it does not, the Customer's remedy is for us to correct the issue or, if we cannot within a reasonable time, for either party to end the affected subscription and for us to refund prepaid fees for the remaining period.

Each party warrants that it has the authority to enter into this agreement.

Except as stated in this section, and to the extent the law allows, the Service is provided "as is" and "as available". We do not warrant that it will be uninterrupted or error-free, or that it will detect all sensitive data. We disclaim all other warranties, express or implied, including merchantability, fitness for a particular purpose and non-infringement.

13. Limitation of liability

Neither party is liable for indirect, incidental, special, consequential or punitive damages, or for loss of profits, revenue, goodwill or data, even if told they were possible.

Each party's total liability arising out of or relating to this agreement is limited to [OWNER TO CONFIRM: liability cap, for example the fees paid or payable by the Customer in the 12 months before the event giving rise to the claim].

[OWNER TO CONFIRM: exclusions from the cap and from the exclusion of indirect damages, for example the Customer's payment obligations, breach of confidentiality, data-protection breaches (or a separate, higher cap for them), indemnities, and fraud or wilful misconduct]

During a free trial our total liability is limited to [OWNER TO CONFIRM: trial liability cap, for example USD 100].

Nothing in these Terms limits liability that cannot be limited by law.

14. Indemnity

We will defend the Customer against a third-party claim that the Service, used as permitted, infringes that party's intellectual property rights, and pay the damages and costs finally awarded or agreed in settlement. If such a claim is made or likely, we may get the right for the Customer to keep using the Service, modify it so it no longer infringes, or end the affected subscription and refund prepaid fees for the remaining period. We have no obligation for claims caused by Customer Data, by combination with things we did not provide, or by use in breach of these Terms.

The Customer will defend us against a third-party claim arising from Customer Data, from the Customer's or its End Users' breach of section 5, or from the Customer's failure to give its End Users the notices or obtain the consents its law requires, and pay the damages and costs finally awarded or agreed in settlement.

The party seeking defence must notify the other promptly, give it control of the defence and settlement, and cooperate reasonably. [OWNER TO CONFIRM: whether mutual indemnities are wanted at all for the Team plan, and whether they sit inside or outside the liability cap]

15. Governing law and disputes

This agreement is governed by the laws of [OWNER TO CONFIRM: governing law, for example India].

The parties will first try to settle any dispute through good-faith discussion between senior representatives for [OWNER TO CONFIRM: number of days]. Any dispute not settled will be resolved by [OWNER TO CONFIRM: forum: the courts of a named city, or arbitration under named rules, seat, language and number of arbitrators; consider a different forum for GCC customers].

Either party may seek urgent injunctive relief in any competent court.

16. Changes to these Terms

We may update these Terms. We will tell Admins by email and on this page at least [OWNER TO CONFIRM: notice period, for example 30 days] before a material change takes effect. Changes apply from the Customer's next renewal unless they are required by law or the Customer agrees earlier. Terms signed in an Order Form prevail over this page.

17. General

  • Order of precedence: an Order Form, then the DPA (for data protection), then these Terms.
  • Entire agreement: these Terms, the DPA and the Order Forms are the whole agreement on their subject and replace earlier discussions. Terms on a Customer purchase order do not apply.
  • Assignment: neither party may assign this agreement without the other's consent, except to a successor in a merger or sale of substantially all of its business, with notice.
  • Force majeure: neither party is liable for delay caused by events beyond its reasonable control, other than payment obligations.
  • Notices: to us at the address below; to the Customer at the email of its account owner or as in the Order Form.
  • Publicity: we may name the Customer as a customer only with its consent.
  • Independent parties, no third-party beneficiaries, severability and waiver apply as usual: an unenforceable clause is limited to what is enforceable, and not enforcing a right is not a waiver of it.
  • Language: these Terms are written in English. A translation is for convenience; the English text prevails. [OWNER TO CONFIRM: whether an Arabic version is needed and which text prevails for GCC customers]

18. Contact

Magynta Technologies Private Limited [OWNER TO CONFIRM: exact registered legal name, corporate identification number and registered office, if different from the postal address below]

Postal address: B2 Golden Orchid, Plot No. 136, Sector 11, PCNTDA, Chikhali Pradhikaran, Pune - 411019, India

Email: dpo@magynta.com for privacy and legal notices. [OWNER TO CONFIRM: a separate contact address for legal notices and for sales]