Terms of service

These Terms of Service ("Terms") govern your access to and use of the Polyfence platform, API, and related services ("Service") operated by Polyfence ("we", "us", or "our"). By accessing or using the Service, you agree to be bound by these Terms.

If you are using the Service on behalf of an organization, you represent that you have the authority to bind that organization to these Terms.

Account registration

To use the Polyfence platform, you must create an account using a supported authentication method (GitHub, Google, or email magic link). You are responsible for:

• Maintaining the security of your account credentials
• All activity that occurs under your account
• Notifying us immediately of any unauthorized access
• Ensuring that your account information is accurate and up to date

You may not share your account with others or create multiple accounts to circumvent usage limits.

API usage and rate limits

Your use of the Polyfence API is subject to usage quotas and a per-second rate limit, which we set and may adjust to protect the Service and ensure fair use for all accounts. If an API request is refused for going over the limit, the response says what the limit was. Limits may change as your plan or our Service evolves, and what a response reports is informational and not part of these Terms.

During Early Access most usage quotas are open; a per-second API rate limit applies for infrastructure protection. We reserve the right to set, change, throttle, or suspend access where usage patterns indicate abuse, automated scraping, or behavior that degrades the Service for other users. We may throttle or suspend immediately to protect the Service or address abuse; for planned reductions to your standard published limits, we will give reasonable advance notice.

API key security

API keys grant programmatic access to your Polyfence account. You are solely responsible for:

• Keeping your API keys confidential and secure
• Never sharing API keys in public repositories, client-side code, or insecure channels
• Revoking compromised keys immediately via the dashboard
• All API calls made using your keys, regardless of who made them

Polyfence stores API keys as SHA-256 hashes. We cannot recover your key after creation. If lost, you must generate a new one.

Acceptable use

You agree not to use the Service to:

• Violate any applicable law or regulation
• Scrape, crawl, or systematically extract data from the Service beyond normal API usage
• Circumvent rate limits, usage quotas, or other technical restrictions
• Interfere with or disrupt the Service or its infrastructure
• Transmit malicious code, viruses, or harmful data through the API
• Impersonate another user or misrepresent your affiliation with any entity

Violation of these terms may result in immediate suspension or termination of your account.

Service availability

Polyfence is in Early Access and runs on a best-effort basis. We aim for high availability and do not guarantee uninterrupted access.

We may perform scheduled maintenance, deploy updates, or modify the Service at any time. We will provide reasonable advance notice for changes that materially affect your use of the Service.

Data handling

Your zone data, API configurations, and account information are stored securely on Polyfence infrastructure. We take data protection seriously:

• Zone data is isolated per account or workspace. Our staff can reach it through internal admin tools, as the privacy policy describes, including which of that access is recorded
• Account data is retained for the duration of your account and deleted when you delete it, apart from the few records the privacy policy lists as outlasting deletion

For full details on how we collect, use, and protect data, see our Privacy Policy.

Open source SDKs

The Polyfence client SDKs (Flutter, React Native, native Kotlin/Swift, and embedded C) are licensed under the MIT License. The SDK license is separate from these SaaS Terms of Service.

• The SDKs are provided "as is" without warranty of any kind, express or implied
• Telemetry in the mobile SDKs is enabled by default and can be opted out with a single configuration flag (see our Privacy Policy for details on what is collected). The embedded C library does not include telemetry.
• Community contributions are accepted under the MIT License
• Use of the SDKs does not require a Polyfence account, though some features require API access

Your app's users

Polyfence is for developers and businesses. If you put a Polyfence SDK, library or firmware in an app or a device, the people who use it are your users, not ours. We never ask who they are. They are your responsibility. In particular:

• You tell your users, in your own privacy policy, what your app does with their location and that it uses Polyfence. That includes the anonymous performance telemetry our mobile SDKs send to us, which is on by default (our Privacy Policy lists what it contains).
• You have a lawful basis for anything your app or device sends to us, including coordinates sent to the evaluate API or through LoRaWAN, and you get any consent the law requires before it is sent, wherever your users are.
• If your users, or the law where they are, need telemetry off, you turn it off in your app. Our SDKs do this with one setting.

Paid plans

There are no paid plans yet. Polyfence is in Early Access and nobody is billed. When paid plans arrive they will have their own terms, and an Early Access account is never moved onto one without you asking for it.

Intellectual property

Your data: You retain all rights to the zone data, configurations, and content you upload to Polyfence. We do not claim ownership of your data.

Our platform: The Polyfence platform, API, documentation, branding, and all related intellectual property remain the property of Polyfence. These Terms do not grant you any rights to use our trademarks, logos, or branding without prior written consent.

Limitation of liability

1. What we do not limit. Nothing in these Terms limits or excludes either party's liability for: (a) death or personal injury caused by its negligence, or by the negligence of its employees, agents or subcontractors; (b) fraud or fraudulent misrepresentation; or (c) anything else that cannot lawfully be limited or excluded.

2. Our commitment, and what we do not promise. We will provide the Service with reasonable care and skill. Apart from that and anything else these Terms expressly say, and to the extent the law allows, the Service is provided "as is" and "as available": we make no other promise about it, whether implied by statute, common law or otherwise, including that it will be available without interruption, free of errors, or fit for any particular purpose. The SDKs are provided under their own open-source licences.

3. Losses neither party is liable for. Subject to clause 1, neither party is liable to the other, whether in contract, tort (including negligence), breach of statutory duty or otherwise, for: (a) loss of profit, revenue or anticipated savings; (b) loss of business, contracts or opportunity; (c) loss of goodwill or damage to reputation, in each case whether direct or indirect; or for (d) any indirect or consequential loss.

4. Your data. If your data is lost or corrupted because we broke these Terms or were negligent, we will use reasonable efforts to restore it from our most recent backup, and we will pay your reasonable costs of re-entering or restoring anything we cannot restore. That is the extent of our liability for lost or corrupted data, and it counts towards the limit in clause 5. You can export your zones from the dashboard at any time, and you should keep your own copy of anything you cannot afford to lose.

5. The overall limit. Subject to clauses 1 and 6, each party's total liability to the other for all claims arising out of or in connection with these Terms or the Service, whether in contract, tort (including negligence), breach of statutory duty or otherwise, is limited, for all claims arising in any Liability Year taken together, to the greater of: (a) £100; and (b) the total Fees paid or payable for the Service for that Liability Year. "Liability Year" means each period of 12 months beginning on the date you first accepted these Terms, or on an anniversary of that date. A claim arises in the Liability Year in which the event giving rise to it first occurred. "Fees" means the amounts paid for the Service, whether paid to us or to a reseller selling the Service on our behalf.

6. What the limit and exclusions do not cover. Clauses 3 and 5 do not apply to: (a) your obligation to pay Fees; (b) your liability for breach of Acceptable use or Your app's users; or (c) your liability for infringing our intellectual property rights.

7. Data protection claims. Nothing in these Terms limits any right that a person whose data you send us has against you or us directly under data protection law.

8. Why these limits. We provide the Service free of charge during Early Access, and these limits reflect that. You know better than we do what a failure of the Service would cost your business, and you are better placed to insure against it. If you need us to accept a higher limit, contact us at hello@polyfence.io before you rely on the Service; we may be able to agree one in writing, for a fee.

Termination

You may terminate your account at any time by contacting us or through the dashboard settings. We may suspend or terminate your access if:

• You violate these Terms or our Acceptable Use policy
• Your use of the Service poses a security risk to other users
• Required by law or regulation

Upon termination, your right to use the Service ceases immediately. If you delete your account, your data is deleted as the privacy policy describes, including the table of the few records that outlast deletion and why each one does. If we terminate your account for cause, we may retain data as required by law or for legitimate security purposes.

Changes to these terms

We may update these Terms from time to time. Every change moves the "Last updated" date at the top of this page. We do not email updates to these Terms, and where the law requires us to give you notice of a change, we will.

Continued use of the Service after changes take effect constitutes acceptance of the updated Terms. If you do not agree to the updated Terms, you must stop using the Service and close your account.

Governing law

These Terms are governed by and construed in accordance with the laws of the jurisdiction in which Polyfence operates, without regard to conflict of law principles. Any disputes arising from these Terms or the Service shall be resolved in the courts of that jurisdiction.

Questions? hello@polyfence.io