How Storgy handles your data

Seven external services process Storgy customer data. Each is listed below with its specific purpose. The same list with direct privacy-policy links lives on the Trust & compliance page. If we add or remove a sub-processor, this list is updated and the date band above is bumped.

• Anthropic — AI model inference for editorial drafts
• OpenAI — Editorial phrasing pass — no customer-submitted text
• Resend — Transactional email (magic-link auth, digests)
• Paddle — Payment processing (merchant of record, pre-Stripe subscriptions)
• Stripe — Payment processing and tax calculation (current subscriptions)
• Hetzner — Application + database hosting (EU)
• Cloudflare — Authoritative DNS

Storgy runs Google Analytics 4 (GA4). GA4 sets cookies, records the pages you view, and reports an IP-derived approximate location to us in aggregate. Google also processes your IP address as a transit-only signal — they truncate it before it reaches our reports. We use this only to see which pages people read and where readers come from; we don’t sell or share this data.

You can opt out by installing the Google Analytics Opt-out Browser Add-on, by blocking analytics cookies in your browser, or by using any standard tracker-blocking extension. Storgy works fine without GA4.

When you submit a poem to the Poem Analyzer, we store four things in our database:

• The poem text you pasted (plus the title and author you optionally provided), so the analysis lives at a permanent shareable URL.
• The Claude-generated analysis, so we don’t pay to regenerate it every time the URL is opened.
• A salted SHA-256 hash of your IP address, kept only for rate-limiting. We never store your raw IP, and the salt means the hash can’t be reversed against a precomputed table.
• A short ID (the part in the URL after /tools/poem-analyzer/) so the result is reachable.

If you are signed in, the submission is also linked to your account id, so it appears in your own archive and in the data export at /settings/. A submission made while signed out carries no account identifier at all.

Result pages are public — anyone with the URL can see them — so don’t paste anything into a tool that you wouldn’t want read. Saved runs stay private to your profile unless you tick “Share on profile”.

The AI tools enforce four limits, all keyed off the salted IP hash described above: a burst limit of ten runs per five minutes, your plan’s credit allowance, a per-IP daily ceiling that applies to anonymous and free accounts only, and a site-wide daily cap that protects us from runaway model costs. The IP hash is held in our cache for the rate-limit window only.

Reading is never rate-limited, and the deterministic tools — the syllable counter, rhyme-scheme finder, citation generator and the rest — carry only a flood guard, since they make no model call.

One external service receives the text you submit to a tool: Anthropic, which runs Claude, the model that produces the analysis. Their privacy policy applies, and their API terms state they don’t train on inputs from API customers by default.

We also use OpenAI, but not on anything you write. It runs a phrasing pass over our own editorial content before we publish it — poem-page study scaffolds, reading guides, and similar. Nothing you paste into a tool, and nothing you write at the Writing Desk, is sent to it.

Anthropic receives only the text of that one request — never your IP, your hash, your email, or any other metadata.

Two third-party analytics tools run on the public site:

• Google Analytics 4 (typically _ga, _ga_*) — page and traffic measurement.
• The Meta pixel — measures advertising we have run. It is a social -network tracker, and we would rather name it here than let you find it in your network tab.

Storgy’s own cookies are functional rather than advertising ones:

• A session cookie when you are signed in.
• A one-time marker for your free anonymous AI run, and another for the free anonymous study-sheet download.
• A first-touch record of how you arrived — landing page, referring site, and any campaign parameters on the URL.
• A referral code, if you followed someone’s referral link.

Both analytics loaders are switched off entirely on pages reached by a secret link, such as a shared Writing Desk draft: on those pages the URL is the credential, and it should not be reported to anyone.

You can block all of the analytics — with a tracker-blocking extension, by blocking analytics cookies, or with Google’s opt-out add-on. Storgy works fine without them.

Submissions to the analyzer are kept indefinitely so the permalinks keep working. If you want a specific submission deleted, email hello@storgy.com with the URL — we’ll remove it. GA4 data is retained per Google’s defaults; you can request its deletion at the same address.