Privacy Policy

How Field Logic Ltd handles personal data through grith.ai and the grith product.

Last updated:

1. Who we are

This Privacy Policy is published by Field Logic Ltd ("Field Logic", "we", "us"), company number 15380264, registered in England and Wales and trading as grith. Our registered office is 3rd Floor, 86-90 Paul Street, London, England, EC2A 4NE. We are the controller for account, billing, website, and support data. For customer data submitted through team cloud features, we generally act as a processor under our Data Processing Agreement.

Contact for privacy / data-protection enquiries: privacy@grith.ai.

2. What this policy covers

This policy describes how we handle personal data when you:

  • visit grith.ai or docs.grith.ai;
  • create a grith account or sign in via GitHub;
  • subscribe to a paid tier through Polar;
  • email us, fill in the contact form, or report a vulnerability;
  • run the grith product with cloud-sync features enabled.

The grith product itself runs locally on your machine. Most data processing - proxy evaluations, audit logs, supervisor traces - stays on your device unless you explicitly enable a feature that sends data to our servers (see section 3.5 Product telemetry and cloud sync).

3. What we collect and why

3.1 Website visitors

  • Server logs - IP address, user-agent, requested URL, referrer, timestamp. Retained for up to 30 days for security and abuse-prevention purposes. Lawful basis: legitimate interests (operating and securing the service).
  • PostHog analytics (anonymous) - before you answer the cookie banner, we record pseudonymous page views in a storage-free mode: nothing is written to or read from your device, and the identifier lives only for the current page load, so you are not recognised across visits and no profile is built. Lawful basis: legitimate interests (understanding aggregate site usage). This mode does not run if you decline or send a GPC/Do Not Track signal.
  • PostHog analytics (consented) - if you accept analytics cookies, the same usage events (page views, navigation paths, and feature interactions) gain a persistent randomly generated identifier, so returning visits can be recognised. We do not identify you in PostHog from your grith account. See our Cookie Policy for the cookie names and retention. Lawful basis: consent.
  • Analytics routing - in both modes, analytics requests go to grith.ai/ingest and are forwarded by our server to PostHog's EU region (eu.i.posthog.com), so they are not dropped by content blockers. We forward your IP address to PostHog for coarse geolocation, and never forward your session cookie.
  • Consent state - your cookie-banner choice is stored in your browser's localStorage ascookie_consent (value yes / no). This is essential and never leaves your device.

3.2 Account holders

When you create an account:

  • Email address - required for sign-in, transactional email (verification, licence delivery, billing), and support correspondence. Lawful basis: contract.
  • Name and avatar - only if you sign in via GitHub OAuth. We receive your public GitHub profile (name, username, avatar URL, primary email). Lawful basis: contract.
  • Authentication and device tokens - issued and managed by Better Auth, stored server-side and, for website sessions, as a secure HTTP-only cookie in your browser. Device-login and API credentials are associated with your account. Lawful basis: contract.
  • Encrypted LLM provider keys - if you store OpenAI / Anthropic / OpenRouter / Ollama keys in your grith account, they are encrypted at rest with AES-256-GCM using a key derived from a server-held master secret. The Service decrypts a key only when returning it to an authorised administrator for the team that stored it; plaintext keys are not logged. Lawful basis: contract.

3.3 Paid subscribers

Payment is processed by Polar; we do not see or store your card details. From Polar we receive and store the subscription ID, tier, status, billing email, and subscription lifecycle events (created, renewed, cancelled, refunded). Lawful basis: contract.

3.4 Contact / support correspondence

If you email us or use the contact form, we hold the contents of your message together with your email address for as long as the enquiry remains open, plus a reasonable backlog period (typically 24 months). Lawful basis: legitimate interests (handling and improving customer support) or consent.

3.5 Product telemetry and cloud sync

The grith product supports optional features that send data to our servers:

  • Audit pipeline (Pro / Enterprise) - when enabled, condensed audit records are pushed to our backend for cross-device review and team-level reporting. Records can include the team and account identifiers, session and project names, supervised tool, tool-call type, decision, scores, model/provider identifiers, token counts, cost estimate, and timestamps. They do not include the underlying file contents, prompts, command arguments, or network payloads. Audit sync can be disabled at any time.
  • Update checks - the daemon may query the public GitHub Releases API to check for new versions. This reveals your IP and user-agent to GitHub; we receive no data from this call.
  • Licence validation (Pro / Enterprise) - periodic signed-licence checks against our backend. We log your account ID and the timestamp.

Where features are explicitly opt-in or opt-out, the lawful basis is contract (delivering the feature you chose to use); where they support security and abuse prevention the basis is legitimate interests. Local-only usage of the open-source product never sends data to our servers.

4. Sub-processors

We rely on the following processors to deliver the service. Each is bound by a data-processing agreement and operates within the regions stated.

ProcessorPurposeRegion
Amazon Web Services (Amplify, RDS, S3, SES)Hosting, database, email deliveryus-east-1 (N. Virginia, USA)
PolarPayment processing and subscription managementEU / US (per Polar's sub-processor list)
PostHogProduct analytics (anonymous before consent, persistent after)EU (Frankfurt)
GitHub (Microsoft)OAuth identity provider; source-hostingUS
CloudflareCDN / DDoS mitigation in front of grith.aiGlobal edge

We will give at least 30 days' notice before introducing a new sub-processor that materially changes how personal data is handled.

5. International transfers

Our primary hosting, database, and email infrastructure runs on Amazon Web Services in the United States (us-east-1, N. Virginia). Personal data of UK / EEA users is therefore transferred to and processed in the US. Other processors that handle data outside the UK / EEA include GitHub and Polar's US infrastructure. These transfers are covered by an adequacy decision where one applies (the EU-US Data Privacy Framework and its UK extension) and otherwise by the UK International Data Transfer Addendum / EU Standard Contractual Clauses with appropriate supplementary measures.

6. How long we keep your data

  • Server logs: up to 30 days.
  • PostHog analytics: up to 12 months.
  • Account and team data: while your account is active. Following a verified deletion request, we delete or anonymise it unless we must retain specific records for legal, security, or dispute purposes.
  • Billing records: 7 years (UK tax / VAT requirement).
  • Support correspondence: 24 months.
  • Audit-pipeline data (Pro+): per the retention you configure, default 90 days.

7. Your rights

Under UK GDPR you have the right to:

  • access the personal data we hold about you;
  • rectify inaccurate data;
  • erase your data (subject to legal-retention exceptions);
  • restrict or object to processing;
  • data portability (receive a copy in a machine-readable format);
  • withdraw consent at any time, where consent is the lawful basis;
  • lodge a complaint with the Information Commissioner's Office (ICO), the UK supervisory authority.

Email privacy@grith.ai to exercise any of these rights. We normally respond within one month, subject to any extension permitted by data-protection law. We do not use the data covered by this policy for solely automated decisions that produce legal or similarly significant effects.

8. How we protect your data

Technical and organisational measures we take:

  • TLS in transit for all public endpoints.
  • Encryption at rest for stored secrets (provider keys, license signing key).
  • Hashed-and-salted passwords (where used); session tokens issued and rotated by Better Auth.
  • Secret material kept in a managed password vault, not on developer disks.
  • Audit logging on production database access.
  • Annual review of sub-processors and contracts.

If we become aware of a personal-data breach that is likely to result in a risk to your rights and freedoms, we will notify the ICO within 72 hours and, where the risk is high, notify affected users without undue delay.

9. Children

The grith service is not directed at children under 16. We do not knowingly collect personal data from children.

10. Changes to this policy

We may update this policy when our practices change or when legal requirements evolve. Material changes will be announced on this page and (for account holders) by email at least 30 days before they take effect. The "Last updated" date at the top of this page always reflects the current version.

11. Contact

Field Logic Ltd, company number 15380264, registered in England and Wales. Registered office: 3rd Floor, 86-90 Paul Street, London, England, EC2A 4NE. Privacy enquiries: privacy@grith.ai. Other legal matters: legal@grith.ai. Security vulnerabilities - please follow our Security Policy rather than emailing privacy@.

Field Logic Ltd (company no. 15380264), registered in England and Wales. Registered office: 3rd Floor, 86-90 Paul Street, London, England, EC2A 4NE. Privacy / data-protection enquiries: privacy@grith.ai. Other legal enquiries: legal@grith.ai.