Summary
Ink is a desktop application. The documents you create with it stay on your computer; we never see them. The only personal data we hold on our servers is what you give us when you purchase a license (your email address) and what your computer sends us when it checks for software updates (your IP address, briefly, in our hosting provider's access logs). We do not run analytics, sell data, or share what you do with Ink with anyone.
This policy covers both the get-ink.app website and the Ink desktop application.
Who we are
Ink is published by Springcraft, Inc., a Delaware corporation whose main work is in Physical AI. Ink is a side project — an internal tool we built for our own contract paperwork that turned out too good not to release. That backstory shapes how we treat your data: the goal is to ship a useful piece of software, not to harvest a user base.
For the purposes of GDPR and similar laws, Springcraft is the data controller for personal data described below. You can reach us at privacy@springcraft.ai.
Data we collect
From your purchase
Checkout itself runs on Stripe, not on our servers. We chose Stripe because it's the gold standard for secure online payments — PCI Level 1 certified, used by millions of businesses, and famously serious about data protection. Card number, billing address, and the rest of the payment details go directly to Stripe; we don't store them on our servers (we can view summary information about a payment in the Stripe dashboard, but the underlying card data lives only with Stripe). After your payment succeeds, our license server receives a notification from Stripe containing your email address and a few opaque Stripe references (a customer ID, a checkout session ID, a payment intent ID). Stripe's own privacy policy governs what it collects: stripe.com/privacy.
From that notification our license server creates and keeps one record per license. The record contains:
- Your email address (so we can deliver and re-issue your license key).
- A unique license identifier and the cryptographically signed license token we generate.
- The SKU you bought, the issue date, and the computer cap for the license.
- The opaque Stripe references (so a purchase can be linked to a license).
- When you first activate Ink on a computer, the app sends our license server one activation request. That request is the only time the app talks to the license server for routine operation — after activation, the server signs a local certificate that lives on your computer, and every subsequent launch verifies it offline. Ink does not phone home for licensing on a schedule or to "check in".
- For each computer that successfully activates, we add an activation entry to your license record. The entry holds an opaque identifier (the one the app generated at first launch and stored locally — it counts the entry against your license's computer cap and isn't reversible to anything about you or the underlying hardware), the activation date, and your computer's hostname. The hostname is whatever your operating system reports for the device — that name often includes your first name and a model word (e.g. "Jane's MacBook Pro"). We use it as a UX hint: if you hit the computer cap, Ink shows the list of active computers so you can recognize which old computer to deactivate. So long as you have access to a computer with an active license on it, you can deactivate it from Ink's Settings on that computer, which removes the entry.
- When the app makes one of those activation or sign-out requests, our license server writes a small operational log line — typically a single sentence noting the outcome (e.g. "activation issued" with the SKU) plus AWS's per-invocation execution metadata (request ID, duration, timestamp). We do not log request bodies, IP addresses, license keys, fingerprints, or email addresses. Logs are retained for 30 days and then deleted automatically.
From the website
We do not run per-request access logging on the marketing site. AWS CloudFront, our hosting provider, publishes aggregated metrics to us (request counts, error rates, byte volumes) but these don't contain IP addresses or per-request rows.
There are no analytics, no advertising, no tracking pixels, and no third-party scripts.
From the desktop app
- License validation — when you activate, the app sends your license key, your computer's fingerprint (a hashed identifier so we can enforce your license's computer cap), and your operating system to our license server. This is required for the app to run after the trial period.
- Update checks — when enabled (you can disable this in Settings), the app periodically requests a small JSON file from our hosting endpoint to learn whether a new version is available. The request reaches our hosting provider's logs the same way any web request does (see "From the website" above).
- Crash reporting — none. Ink does not transmit crash reports, error stacks, or telemetry to us or to anyone else.
Data we do not collect
For clarity, here is what Ink does not collect, transmit, or store on our servers:
- The contents of your templates or generated documents.
- The names of your templates, recipients, or signers.
- Any metadata about which documents you create or how often you use the app.
- Analytics or product-usage telemetry of any kind.
- Crash logs, stack traces, or session recordings.
- Cookies for advertising, profiling, or cross-site tracking.
Templating, filling, font rendering, and PDF generation all happen locally on your computer.
How we use the data
- Email address — to deliver your license key, to re-send it if you lose it, and to email you about security or billing matters concerning your account. We do not send marketing email unless you separately opt in.
- License records — to issue and validate licenses, enforce the per-license computer cap, and prevent abuse. License records are also retained for tax and accounting purposes as required by law.
- Server access logs — to keep the service running and to defend against abuse. They are not joined with your purchase records, and we do not build a behavioral profile from them.
Third parties
Ink uses a small number of third-party services to operate. We share with each only what that service needs.
- Stripe (payment processing) — receives your payment details, name, and billing email when you purchase a license. Privacy policy: stripe.com/privacy.
- Amazon Web Services (hosting and email delivery) — hosts the website, the license server, and the update endpoint, and relays the license-delivery email (and other transactional notices) via SES. AWS does not access the data we store; it provides the underlying infrastructure. Privacy notice: aws.amazon.com/privacy.
E-signature platforms (Adobe Sign, SignWell, etc.) are not third parties to us. If you connect one in Ink's Settings, the app talks to that platform directly using credentials you supply — your documents, signers, and field layouts go from your computer to the platform you chose. Springcraft does not see, proxy, or store any of that traffic. Each platform's own privacy policy governs what they do with the data.
Cookies and local storage
The get-ink.app website does not set any cookies of its own. If you click through to Stripe Checkout to complete a purchase, Stripe may set its own cookies on its own domain — those are governed by Stripe's policy.
The Ink desktop app stores its state on your computer: your license token, your application settings, and your templates and document sets in the folder you choose at first-run. Nothing in this local state is transmitted to us except the license-validation and update-check requests described above.
Data retention
- License records — retained for the lifetime of your license, plus the period required by tax and accounting law (typically 7 years in the US). On request we will redact your email and other identifying fields where doing so does not violate our legal-retention obligations.
- License-server operational logs — 30 days, then deleted automatically.
Security
All web traffic to and from get-ink.app and our license server is encrypted in transit (TLS 1.2+). Data at rest in our hosting provider is encrypted using the provider's managed keys. License tokens are Ed25519-signed so a tampered token will fail validation and will not unlock the app.
No system is perfectly secure. If a breach affecting your personal data occurs, we will comply with the notification obligations applicable law imposes on us.
International transfers
Springcraft, Inc. is based in the United States. Our infrastructure
runs on AWS, primarily in the us-west-2 (Oregon)
region. If you are located in the European Economic Area, the
United Kingdom, or another jurisdiction that restricts
cross-border data transfers, your data may be transferred to and
processed in the United States. We rely on the Standard
Contractual Clauses approved by the European Commission for
these transfers.
Your rights
Depending on where you live, you have some or all of the following rights regarding personal data we hold about you:
- The right to access a copy of your data.
- The right to correct inaccurate data.
- The right to request deletion of your data (subject to legal retention obligations).
- The right to receive your data in a portable, machine-readable format.
- The right to object to or restrict processing.
- The right to withdraw consent for any processing that relies on consent.
- The right to lodge a complaint with your local supervisory authority (e.g. your country's data-protection regulator).
To exercise any of these, email privacy@springcraft.ai. We will respond within 30 days. We do not charge for these requests except where they are manifestly unfounded or repetitive.
California residents have additional rights under the CCPA/CPRA, including the right to know what categories of personal information we collect and the right to opt out of any "sale" or "sharing" of personal information. We do not sell or share personal information for cross-context behavioral advertising.
Children's privacy
Ink is a business productivity tool and is not directed at children under 16. We do not knowingly collect personal data from anyone under 16. If you believe a child has provided us personal data, please contact us and we will delete it.
Changes to this policy
We may update this policy from time to time. The version number and effective date at the top of this page will change when we do. We encourage you to review the policy periodically.
Contact
Privacy questions, data-subject requests, and complaints: privacy@springcraft.ai.