Privacy Policy

1. Who we are and what this covers

This Privacy Policy explains how Hedgeling LLC, a Utah limited liability company ("Hedgeling", "we", "us") collects, uses, and shares personal data when you visit this website, install the @hedgeling/i18n package, or use the hosted console (together, the "Service"). It applies to account holders, team members invited to a workspace, and visitors.

When you use the Service on behalf of an organization, that organization controls the content it submits and we process that content on its instructions. This policy describes what we do with it.

2. What we collect

Account data. Email address, display name, password hash (held by Amazon Cognito, not by us), organization name, role and team membership, the email domain of the workspace owner, and your acceptance of the current Terms and Privacy Policy versions.

Source strings and translations. The user-facing strings extracted from your code, the surrounding code context used to translate them accurately, translations and their revision history, glossaries, personas, style guides, imported documents (normalized text only; original binary files are discarded after parsing), review comments, and console chat messages.

Usage and billing records. Which features you use, how many strings, locales, seats, and AI credits you consume, provider token counts, plan and subscription state, invoices and payment status, and budget alerts. Card details are collected and stored by Stripe, never by us.

Credentials. Service credentials and entitlement leases issued to your projects (we keep only a hash of credentials), and any AI provider keys you connect (stored encrypted).

Logs and security records. IP address, browser or client version, request paths, timestamps, sign-in events, rate-limit counters, and audit records of who changed what in a workspace.

This website. With your permission, we use Google Analytics through Google Tag Manager to measure page visits, referral sources, interactions, and device information. Analytics cookies are optional; Google receives this usage data only after you accept analytics. We do not enable advertising personalization. Google Fonts receives your IP address when fonts load, and our host records standard access logs.

The command-line package. The package sends no telemetry to us. When you run a translation with your own provider key, it sends source strings directly from your machine to the provider you configure. When you use hosted features, it talks to the console with your service credential.

3. How we use it

• to provide the Service: extracting, storing, translating, reviewing, and delivering your strings;
• to authenticate you and enforce permissions, plan limits, and entitlements;
• to bill you, detect and prevent abuse (including checking that a person claims only one free workspace), and reconcile usage;
• to secure the Service, investigate incidents, and keep audit history;
• to support you and respond to your requests;
• to send service notices such as credential expiry, limit warnings, and changes to these documents; and
• to comply with legal obligations.

We do not use your source strings, translations, or other customer content to train AI models, and we do not sell personal data. We do not send marketing email without your consent.

4. Service providers we share data with

We use these providers to run the Service. Each processes data only as needed for its role.

• Amazon Web Services (AWS): hosting, databases, storage, and backups for the console.
• Amazon Cognito: account creation, sign-in, password storage, and verification email.
• Stripe: checkout, payment methods, invoices, and the customer billing portal.
• Google (Gemini) and Meta (Llama): when you use managed AI on our platform key, the strings and context being translated are sent to the selected provider's API for inference.
• GitHub: when you connect a repository, we read the source files you choose and, at your request, open pull requests with translations, using the access you grant.
• Google Workspace: email you send to our support and sales addresses.
• Google Fonts: web fonts on the marketing site, as described in section 2.

We may also disclose data when required by law, to protect the rights and safety of Hedgeling, our customers, or others, or as part of a merger, acquisition, or sale of assets (in which case this policy continues to apply to the transferred data).

5. Bring-your-own-key (BYOK) data flow

If you connect your own AI provider key, inference requests for your workspace go to that provider under your key, and the provider's privacy policy and data-handling terms govern that processing. We store the key encrypted with keys held in our server-side secret store, reveal only its last four characters in the console, record masked audit events when it changes, and never return it in plain text. Removing the key in the console does not revoke it with the provider.

When you run the package locally with your own key, nothing about that translation passes through Hedgeling.

6. Retention and deletion

We keep customer content for as long as your workspace exists. Ending a subscription does not delete your data; you keep read and verified-export access for a grace period of at least 30 days. Deletion starts only when an authorized user requests deletion of a project or organization in the console, which opens a 30-day export-only window. After that window we purge translation content: source strings, translations, context, glossaries, prompts, personas, imported documents, chat and AI payloads, and content snapshots in audit records. Organization deletion also removes memberships, credentials, invitations, and billing contact data.

We retain a minimal set of records after deletion for accounting, security, and legal purposes: billing, invoice, tax, and payment facts; aggregate usage measurements with content removed; legal acceptance evidence; the record that a free workspace was claimed, with its email removed; and audit action, actor, and time records without content.

Purged content may remain in encrypted database backups for a short period (currently up to seven days) before those backups expire. Signed payment-provider event payloads are redacted after 90 days.

Deleting a workspace does not delete your individual account if you belong to other organizations. To delete your account entirely, contact us (section 10).

7. Security

We protect data with encryption in transit (HTTPS) and at rest, role-based access control, tenant isolation, encrypted storage of provider keys, hashed storage of service credentials, signed short-lived entitlement leases, rate limiting, and audit logging. No system is perfectly secure; if you discover a vulnerability, please report it privately to support@thehedgeling.com rather than in a public issue.

8. International transfers

The console is hosted on AWS in the United States, and our providers may process data in the United States and other countries. If you use the Service from elsewhere, your data will be transferred to and processed in those locations. Where required, we rely on the providers' standard contractual safeguards for such transfers.

9. Your rights

Depending on where you live, you may have the right to access, correct, export, restrict, or delete your personal data, to object to certain processing, and to complain to a supervisory authority. You can update account details and export your catalogs in the console at any time. For other requests, contact us atsupport@thehedgeling.com. We will verify your identity before acting on a request and respond within the time required by law. If you are a team member of a customer's workspace, we may direct your request to that customer.

10. Contact and requests

Privacy questions and requests: support@thehedgeling.com.

11. Children

The Service is for businesses and developers and is not directed at children. We do not knowingly collect personal data from anyone under 16 (or a higher age where local law requires). If you believe a child has provided us data, contact us and we will delete it.

12. Cookies and local storage

The console uses strictly necessary cookies and browser storage to keep you signed in and protect against cross-site request forgery. The marketing site stores your analytics choice in local storage for up to 180 days. Analytics cookies are used only after you accept. You can change your choice or withdraw consent using Analytics settings on any marketing page.

13. Changes to this policy

We may update this policy from time to time. Each version carries a version date at the top of this page. For material changes we will notify account holders by email or in the console before the new version takes effect, and the console may ask you to re-accept it.