Redaxa 0.3.1

Redaxa 0.3.1 — its own update-signing key

No feature changes. This release exists to fix one thing: Redaxa's
auto-updater trusted the same signing key as PC Tweaker and the PC Tweaker
Uninstaller — three separate products verifying updates against one shared
private key. A compromise of that one key, together with push access to any
one of the three repositories, could have signed a malicious update for all
three install bases at once, not just the product actually breached.

What changed

• A new, Redaxa-only Ed25519 keypair now signs its updates. This release is
  still signed with the old shared key, because that is the only key
  existing 0.3.0 installs trust — it is what lets this update reach them at
  all. From the release after this one onward, Redaxa signs only with its
  own key.
• Nothing else moved: same binary, same behaviour, same account data.

If you're on 0.3.0 already

You update to this release exactly as you would any other — nothing to do
by hand. If you skip checking for updates for a long stretch and land
directly on a future release without passing through this one first, the
auto-update check for that one jump may fail silently, since your app would
still be trusting the old key. A normal manual install fixes it, the same
as installing 0.3.0 the first time did.

Redaxa 0.3.0

New

• New brand mark: a padlock with a face, replacing the plain violet R monogram. This ships in the desktop app, matching the icon already live on the Chrome Web Store listing.

Fixed

• Dashboard history rendering now escapes identifiers and uses safe DOM APIs instead of building HTML from strings.
• Hardened CORS handling.
• Folded /api/auth-config into /api/auth/session to stay under the platform's function cap.

Redaxa 0.2.0 — formerly PromptShield

Redaxa 0.2.0 — formerly PromptShield

A rebrand, not a rewrite. Every feature, every guarantee, every line of the
scanning and policy engine is unchanged: prompts are still checked over an
encrypted connection and discarded immediately, nothing is ever logged or
stored, the free tier stays free forever.

Why the name changed

"PromptShield" turned out to already be in use by several unrelated
products — including an established one with its own domain and users. Best
to fix that now, while this product is still small, than to build years of
brand equity on a name someone else can credibly claim.

Redaxa is unclaimed: no existing extension, app, or product uses it,
across every search we ran before committing to it.

What actually changed

• New name, new mark (a redacted "R" — the metaphor is the product), new
  accent color across the web app, dashboard, browser extension and desktop
  app.
• Browser extension re-submitted to the Chrome Web Store under the new name
  and icon.
• Desktop app identifier changed (com.aurelioavila.redaxa) — existing
  PromptShield desktop installs will not auto-update across this change and
  need a fresh install of 0.2.0.

What did not change

• The API, the scanning engine, the policy engine, account data, API keys,
  organization settings — all untouched. Signing in with your existing
  account works exactly as before.
• The web app's URL stays where it is for now (a dedicated domain is
  planned, not yet purchased) — bookmarks keep working.
• Pricing, plans, and the free tier.

PromptShield 0.1.11

PromptShield 0.1.11

Layout fix: the Organization activity admin snapshot (metrics, per-member bars, CSV export) now spans the full card width instead of being squeezed into one grid column.

PromptShield 0.1.10 — desktop catch-up

PromptShield 0.1.10 — desktop catch-up

The desktop app picks up everything the web dashboard gained since 0.1.9 was cut:

• Admin snapshot in Organization activity: team checks, flagged, blocked, top category, per-member breakdown, and a metadata-only CSV export.
• Faster Organization panel (prefetched and cached — no more late pop-in).
• Activity cards no longer overflow with long member emails.
• First release delivered through the new auto-updater.

PromptShield 0.1.9 — the privacy control layer

PromptShield 0.1.9 — the privacy control layer

PromptShield grows from a scanner into a control layer: organizations, shared policies, explainable decisions, and a metadata-first audit trail.

• Organizations. Business workspaces are now real organizations with owner/admin/member roles. Accepting a team invite joins the workspace automatically.
• Shared protected terms. An admin protects a term once — a project codename, a client name — and every member's checks flag it, on every device and surface.
• Organization policies. Per category (credentials, financial, personal, protected terms) an admin chooses Warn, Redact or Block. Block removes "Send anyway" in the browser extension: the prompt does not leave until it is fixed.
• Explainable decisions. Every scan now returns the rule that decided and a human-written reason, shown in the dashboard results, the extension panel, and the send-interception modal.
• Audit trail, metadata only. Every check leaves an event — surface, detection kinds, decision — never the prompt, never a value, by table design. Your activity (all devices) and organization activity (owners/admins) are visible in the dashboard.
• Desktop auto-update. The desktop app now checks for signed updates at startup and installs them with one click.
• Landing: an always-visible Dashboard link.

Nothing about the core promise changed: prompts are scanned and discarded. The audit trail cannot contain content because its table has no column to put it in.

PromptShield 0.1.8 — the landing becomes the demo

Web release: redesigned landing where an animated shield card replays a real scan (raw → detection → safe), honest four-category coverage of what the scanner detects, a four-step 'before it leaves your screen' flow, and a fixed PWA install control. Live at https://promptshield-beta.vercel.app — and it shipped the same night as PC Tweaker 1.0.0 'Control Room' and PC Tweaker Uninstaller 0.2.0. One suite, one account. Desktop binaries unchanged (0.1.7).

PromptShield v0.1.7

Changelog

v0.1.7 — 2026-08-13

• Desktop session tokens now live in Windows Credential Manager instead of
  the webview's localStorage, closing a real disk-based token-theft path.
• Fixed a CORS origin mismatch (http://tauri.localhost vs the real
  https://tauri.localhost) that made the desktop app look signed out on
  every reopen until you clicked "Log in" again.
• Added a strict Content-Security-Policy to the production deployment
  (previously only the local dev server had one).
• api/auth/callback.ts no longer trusts a client-supplied refresh token
  paired with an access token on faith — it's now verified against Supabase.
• New browser extension (Chrome, MV3) for ChatGPT, Claude, Gemini, Copilot
  and Perplexity: a "Check" button that scans the composer before you send.
• Contextual detection: names right after a greeting ("Dear John Smith,"),
  street addresses.
• Fixed a rule-ordering bug where the phone-number pattern could corrupt an
  IBAN before the IBAN rule ever saw the full string, when all scan
  categories were enabled together (the real default).
• Full security audit: verified Stripe webhook signature checks, IDOR
  protection, rate limiting coverage, and no hardcoded secrets.