Home / TypeCrux Privacy

TypeCrux — Privacy Policy

Publisher: RahaKit

Effective date: November 2, 2026

Version: 1.5

Contact:

Summary

TypeCrux is a local-first text expander for Google Chrome. Everything you create with it — your snippets, data tables, contacts, settings and usage statistics — is stored only in your own browser, on your own device (chrome.storage.local). TypeCrux has no user accounts, no server of ours ever receives your content, and the extension contains no analytics, no advertising and no tracking of any kind.

The only network communication the product itself initiates is the validation of a Pro license key with Lemon Squeezy, our payment provider, when you activate or re-check a license. This policy explains all of the above in full, including exactly what we never collect, why the extension asks for each permission, and the small amount of information that exists when you buy Pro or write to us for support.

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

How we make money

We sell TypeCrux Pro subscriptions and lifetime licenses through Lemon Squeezy. We do not sell, rent or monetise your data, and we never will. There is no advertising in the product and no data business behind it. If this ever changed, this policy would have to change first — see "Changes to this policy".

Definitions used in this policy

  • Your Content — the snippets, data tables, contacts and other material you create or import into TypeCrux.
  • Settings & Stats — your preferences and the usage counters the extension keeps locally (for example, how many expansions you have made). These exist only on your device.
  • Personal Data — information that identifies a person. As explained below, the extension itself gives us none; Personal Data only reaches us if you buy Pro (through Lemon Squeezy) or email us for support.

What the extension stores, and where

TypeCrux stores Your Content, your Settings & Stats, any license key you activate, and its own automatic local backups (snapshots) in Chrome's local extension storage on your device. This storage:

  • never leaves your browser except through an export you initiate (the extension can save an export file to your Downloads folder, under your control, when you ask it to);
  • is not synchronised by us to any cloud service;
  • is deleted when you delete the data inside the product or uninstall the extension.

Optional Vault Lock (encryption at rest)

TypeCrux offers an optional Vault Lock. If you turn it on, your library — snippets, tables, contacts, records, stats and local backups — is encrypted inside Chrome's local storage on your device with AES-GCM-256. The key is derived from a passphrase you choose (PBKDF2-SHA-256, 600,000 rounds) and is kept only in the browser's session memory; it is never written to disk, never sent anywhere, and closing the browser locks the vault. While it is locked, the extension shows a lock screen instead of your data.

There is no passphrase recovery, by design: we hold no copy of your passphrase or key, and there is no server to reset it from. The daily backup file in your Downloads folder is sealed with the same passphrase while Vault Lock is on. Vault Lock is free for everyone; it is not a Pro feature. Your settings, language, theme and license stay outside the vault so the lock screen always appears in your own language.

What we never collect

TypeCrux does not collect, record, transmit or sell:

  • your keystrokes, beyond the trigger-detection described below;
  • the text you type, the text of your snippets, or the contents of web pages you visit;
  • your browsing history or a list of websites you use;
  • your clipboard contents (the extension reads the clipboard only when you ask it to — when an expansion you triggered inserts {clipboard}, or when you click a 📋 Clipboard button to create a snippet from what you copied — and nothing is stored or sent anywhere);
  • analytics, telemetry, crash reports or usage statistics of any kind — the statistics shown in the product are computed and kept locally;

The usage counters behind those statistics (expansion count, estimated time saved, active days) and the state of the one-time Chrome Web Store review prompt are likewise stored only on your device, are used only to operate the statistics and that prompt, and are never transmitted anywhere;

  • any advertising identifiers, and it shows no ads.

Trigger detection. To expand your shortcuts, TypeCrux's content script runs on pages you visit and watches what you type locally, inside the page, solely to recognise when you have typed one of your triggers followed by your expand key. Nothing you type is stored, logged or transmitted; a page's content is never collected.

Autofill. Where TypeCrux offers form autofill, it acts only when you explicitly invoke it, shows you a preview, and fills only after your confirmation. The processing happens locally.

The only network communication

The extension initiates exactly one kind of network communication:

  • License validation. When you activate a Pro license key (and on occasional re-checks), the extension contacts Lemon Squeezy's license API, sending the license key and the activation details Lemon Squeezy requires (such as an instance identifier and the product/variant the key belongs to). No snippet content, settings or statistics are ever included.

Two further interactions are handled by Chrome or by you, not by us:

  • Updates. Chrome checks the Chrome Web Store for extension updates; that is Chrome's own behaviour, under Google's policies.
  • Links you open. If you open links from inside the product (for example this policy, the store page or a purchase page), the destination site's own privacy policy applies to that visit.

Buying Pro — payments and Lemon Squeezy

Payments are processed by Lemon Squeezy, which acts as merchant of record. Your payment card details go to Lemon Squeezy and never reach us. Lemon Squeezy shares with us the order details we need to run the store and support you — such as the email address used at checkout, the product purchased and the license key issued. Lemon Squeezy's own privacy policy governs the data it processes:

https://www.lemonsqueezy.com/privacy

When you contact us

If you email us for support, we receive your email address and the content of your message. We use it only to answer you and to keep the conversation coherent. We keep support correspondence only as long as reasonably needed for support and ordinary business records, and you may ask us to delete it at any time (see "Your rights"). This — together with the purchase records held by Lemon Squeezy — is the only Personal Data about our users that exists outside your own device.

The product also offers a Copy diagnostics button (Settings → Help & support). It copies a short report — the extension version, your plan and counts of your snippets, folders, tables and contacts — so you can paste it into a support email if you choose. It never includes the text of your snippets, contact details, anything from your pages or any part of your license key, and nothing is sent unless you paste it into an email yourself.

Why the extension requests each permission

PermissionWhy TypeCrux needs it
storageTo save your snippets, tables, contacts, settings, statistics and local backups in your browser.
clipboardReadTo read your clipboard when you ask it to — inserting {clipboard} content in an expansion you triggered, or creating a snippet from what you copied.
contextMenusTo offer TypeCrux actions in the right-click menu.
alarmsTo schedule local housekeeping such as automatic local backup snapshots.
downloadsTo save export/backup files to your computer when you ask for an export.
scriptingTo insert expanded text into the page you are typing in.
sidePanelTo show the TypeCrux panel beside the page.

TypeCrux requests no host permissions and cannot read or change website data outside the page interactions described in this policy.

Cookies

The extension sets no cookies. This page is part of rahakit.com; what the website itself collects is described in the site's Privacy Policy.

Data security

Your Content never reaches a server of ours, so there is no central store of user content that could be breached. Your local data is protected by Chrome's own profile and extension-storage security on your device, and we recommend keeping your operating system and browser accounts secured.

Data you send us by email is held in our support mailbox, which we protect with strong authentication, and is used only as described above.

Your rights and choices

Inside the product, you are in direct control. You can view, edit, export (in open formats) and delete everything TypeCrux stores, at any time, from Settings → Import / Export and the in-product delete controls. Uninstalling the extension removes its local storage.

For the little data that exists outside your device (support emails, and purchase records held by Lemon Squeezy): if you are in the EU/EEA, the UK, California or another region with privacy rights, you may ask us to access, correct, export or delete your Personal Data, and to object to or restrict its processing. Write to typecrux@rahakit.com and we will respond within 30 days. We will never discriminate against you for exercising these rights. For purchase data, Lemon Squeezy's policy and dashboard govern the records it holds as merchant of record.

Do Not Sell / Do Not Share. We do not sell or share Personal Data for advertising or for any other purpose. There are no trackers to opt out of.

Children's privacy

TypeCrux is a productivity tool not directed at children, and we do not knowingly collect Personal Data from children under 13 (or the minimum age in your country). If you believe a child has sent us Personal Data, contact us and we will delete it.

Changes to this policy

If we change this policy, we will post the new version on this page with a new effective date and an entry in the version history below. Material changes will also be announced inside the product's "What's new" before they take effect. Continuing to use TypeCrux after a change takes effect means the updated policy applies.

Version history

  • 1.5 — Restyled to match the site's other policy pages, and corrected the Cookies section, which still referred to an earlier host for this page. No data practice changed.
  • 1.4 — Removed the "On-device AI" section: the on-device AI feature was removed from the product (extension v0.33.8), so this policy no longer describes it.
  • 1.3 — Added the Chrome Web Store Limited Use adherence statement.
  • 1.2 — Disclosed that the usage counters and the one-time review prompt's state are stored locally and used only to operate the statistics and that prompt; nothing about them is transmitted.
  • 1.1 — Clarified the two user-initiated clipboard reads; documented the Copy diagnostics report.
  • 1.0 — First published version.

This policy describes the TypeCrux Chrome extension published by RahaKit. Questions: typecrux@rahakit.com.