Privacy notice
In short: the Treelace extension never sends us your code, commit history, names or email addresses, and collects no telemetry. The free edition makes no network requests. Pro sends only your licence key, about once a day. Our website sets no cookies and runs no analytics. To sell Pro we keep a licence id, the plan, your Stripe customer and subscription ids, and the subscription status and dates. Stripe handles payment details.
1. Who is responsible for your data
The controller is Nikah AI Ltd, trading as Treelace, a company registered in England and Wales (number 17199968), Office 1216, 60 Tottenham Court Road, London W1T 2EW. We are registered with the Information Commissioner's Office, registration number ZC176381. Contact us about privacy at privacy@treelace.com. We have not appointed a data protection officer because the law does not require us to.
2. The Treelace extension
The extension runs the git program on your computer and displays the result. Commit messages, author and committer names and email addresses, file contents and diffs from your repositories are processed only on your device, by software you run. We never receive them, so we are not a controller of that data.
- No telemetry. The extension sends no usage data, crash reports or analytics.
- Free edition: no network requests at all.
- Pro licence renewal: when a licence key is stored and renewal is switched on (the default), the extension sends one HTTPS request to
https://treelace.com/api/licence/refreshabout once a day (hourly in the last 3 days before the key expires). The request body is{"key": "<your licence key>"}and nothing else: no machine id, no editor details, no repository information. You can switch it off with the settingtreelace.licence.autoRefresh. - Push and fetch run only when you choose them and connect only to the git remotes configured in your repository, using your own git credentials.
- Stored on your device: your licence key (in your editor's secret storage), the time of the last renewal, the licence id of a subscription the licence service has reported as ended (so Pro stays locked offline), and your graph preferences (last repository, filters, saved views). Interactive rebase writes temporary files (the rebase plan, any new commit messages you typed, and the location of the repository's
.gitfolder) to your system's temporary folder. They are deleted as soon as the rebase finishes or fails. If it pauses, git still needs them, so they are kept, with a note of where they are in the repository's.gitfolder, until the rebase is over, however you end it (continue or abort, in Treelace, in Source Control or in a terminal), and deleted with the note within a few seconds of that. If the editor window was closed by then, they are deleted the next time Treelace runs with that repository open, or otherwise the first time Treelace starts once they are more than 24 hours old. - Links such as "Get Pro" and "Manage subscription" open treelace.com in your web browser only when you click them.
The Visual Studio Marketplace (Microsoft) and Open VSX (Eclipse Foundation) process data about downloads under their own privacy policies. Your editor may collect its own telemetry under its own settings; the Treelace extension does not add to it.
3. What we process, why, and for how long
| Data | Purpose | Lawful basis (UK GDPR Art. 6) | Kept for |
|---|---|---|---|
| Your licence key, sent by the extension (it contains a random licence id, the plan, the products it unlocks and its issue and expiry dates) | Checking your subscription and issuing a renewed key | Contract (6(1)(b)) | Not stored: used to answer the request, then discarded |
| Licence record on our server: licence id, plan, Stripe customer id, Stripe subscription id, subscription status, the start of the current billing period and the paid-through date, whether it is set to cancel, and when the record was created and updated | Delivering, renewing and ending your licence; opening your billing portal | Contract (6(1)(b)) | While the subscription is active, then deleted 90 days after it ends |
| Payment and billing data held by Stripe in our account: your email address, name if given, billing country or address, payment method type, subscriptions, invoices, receipts and refunds | Taking payment, handling cancellations, refunds and disputes, keeping accounts | Contract (6(1)(b)); legal obligation to keep accounting records (6(1)(c)) | Six years after the end of the financial year the transaction falls in (Companies Act 2006 and HMRC record-keeping rules) |
| Your "start now" acknowledgement and its date and time (stored with the Stripe checkout record) | Showing we met the Consumer Contracts Regulations | Legal obligation (6(1)(c)) and legitimate interests in defending claims (6(1)(f)) | With the billing records, six years |
| Email address and receipt or invoice number you type into the recovery page | Finding your purchase in Stripe to show your key again | Contract (6(1)(b)) | Not stored and not logged: used for the lookup, then discarded |
| Your IP address when you use our website or licence service | Delivering pages; limiting repeated requests to stop abuse | Legitimate interests in security (6(1)(f)) | Held in memory for at most one hour for rate limiting; never written to disk. We keep no web access logs |
| Emails you send us (to support@treelace.com or privacy@treelace.com): your address, name and message | Answering you | Legitimate interests in replying (6(1)(f)), or contract if you are a customer | 24 months after the conversation ends |
| Stripe event ids (no personal data) | Processing each payment notification once | Legitimate interests (6(1)(f)) | 30 days |
We do not use your data for marketing, we send no newsletters, we do not profile you, and we make no automated decisions with legal or similarly significant effects. We do not sell or share your data for advertising.
4. Who we share it with
- Stripe (Stripe Payments UK Ltd and its affiliates, including Stripe, Inc. in the United States) processes payments and provides the checkout and billing portal pages. Stripe collects your payment details directly and uses some data, for example for fraud prevention and to meet its own legal duties, as an independent controller under the Stripe privacy policy. Our account uses Stripe's managed payments service, so the checkout page shows the sale as "Sold through Onelink"; Onelink, Stripe's reseller, is then also a controller of the payment data under its own privacy policy, which the checkout page links to.
- OVH Ltd hosts our website and licence service on servers in London, United Kingdom, as our processor.
- Cloudflare, Inc. receives email sent to support@treelace.com and privacy@treelace.com through its Email Routing service, as our processor, and forwards it to the mailbox where we read it. That mailbox is provided by Google LLC (Gmail), which processes the mail under Google's own terms and privacy policy.
- Professional advisers, and courts, regulators or law enforcement where the law requires it.
5. International transfers
Our servers are in the UK. Stripe, Cloudflare and Google may process data in the United States. Those transfers rely on the UK Extension to the EU-U.S. Data Privacy Framework (the "UK-US data bridge") for organisations certified under it, and otherwise on the UK International Data Transfer Addendum to the standard contractual clauses. You can ask us for more detail.
6. Your rights
You have the right to ask for a copy of your data, to have it corrected, to have it deleted, to restrict or object to our use of it, and to receive data you gave us in a portable format. Email privacy@treelace.com. We reply within one month. To protect your data we may ask you to prove the request is yours, for example by giving the receipt number of your purchase. We may not be able to delete billing records we must keep by law, but we will tell you if so.
7. Complaints
Please contact us first. You also have the right to complain to the Information Commissioner's Office: ico.org.uk/make-a-complaint, telephone 0303 123 1113, Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF.
8. Security
Our website and licence service are served only over HTTPS with strict security headers. Licence keys are signed with an Ed25519 key that is kept off the application code. Card details never reach our servers. We keep the licence database deliberately small, so that little is at risk if something goes wrong.
9. Changes to this notice
If we change how we use personal data, we will update this page and its date before the change takes effect.