Home › Security

Security at TextSight.

How we keep your account and your content safe — written plainly, with no claims we can't back up.

Last updated June 2026 Operator Lacewing Technologies Report an issue security@textsight.ai

Overview

The short version:
  • All traffic runs over HTTPS/TLS, with HSTS enabled, behind Cloudflare.
  • Passwords are hashed with bcrypt — we never store them in plain text.
  • Optional two-factor authentication (TOTP) and passkeys are available on your account.
  • Payments are handled entirely by Stripe; we never see or store your full card number.
  • Free scans are processed transiently and are not stored or used to train models.

TextSight is operated by Lacewing Technologies. We're a focused team, so we keep our security posture simple, transparent, and honest: we describe what we actually do, and we use measured language rather than marketing superlatives. This page explains the controls in place today. If something on this page isn't clear, email security@textsight.ai.

Data encryption

In transit

All connections to TextSight — the web app, the marketing site, and our APIs — are served over HTTPS/TLS. We enforce HTTP Strict Transport Security (HSTS) so browsers always connect over an encrypted channel, and all traffic is fronted by Cloudflare for TLS termination and edge protection.

At rest

Account data is stored in a managed PostgreSQL database, with Redis used for queues and short-lived job state. Storage volumes are encrypted at rest by our managed-infrastructure providers.

Authentication & account security

Payment security

All payments and subscription billing are handled entirely by Stripe, a PCI-DSS compliant payment processor. Your card details are entered directly into Stripe's secure fields — TextSight never sees or stores your full card number. We only keep the non-sensitive billing metadata Stripe returns to us (such as plan, status, and the last four digits) needed to run your subscription.

How we handle your content

This is the part most people care about. The full details live in our Content Handling Policy and Privacy Policy.

Infrastructure & hosting

TextSight runs on established, reputable infrastructure providers, each used for a specific purpose:

ComponentProviderPurpose
Application backendDigitalOceanApp servers & API
Marketing siteVercelStatic marketing & tools pages
AI-detection modelSelf-hosted (Hetzner, EU)Dedicated servers running our own detection model
Generative featuresAnthropic (Claude) APIAI rewriting & generative tools
Image / audio detectionSightengineImage and audio detection
Edge / DNS / TLSCloudflareHTTPS, HSTS, DDoS & edge protection
DatabaseManaged PostgreSQLAccount & application data
Queues / cacheRedisBackground jobs & job state

Our AI-detection model is self-hosted on dedicated servers in the EU (Hetzner) rather than a third-party detection API, which keeps the core detection pipeline under our direct control.

Monitoring & logging

For what these tools collect and how long we keep it, see our Privacy Policy and Cookie Policy.

Access control

Responsible disclosure / report a vulnerability

Found a security issue? We welcome reports from security researchers. Please email security@textsight.ai with details and steps to reproduce. Our machine-readable contact is published at /.well-known/security.txt.

We ask that you give us a reasonable opportunity to investigate and fix an issue before any public disclosure, avoid accessing or modifying other users' data, and avoid actions that could degrade the service (such as denial-of-service testing or spam). Acting in good faith under this guidance, we won't pursue action against you for your research.

Your data rights

Security and privacy go together. You can review what data we hold and how we use it, and exercise your rights, through these documents:

To request access to or deletion of your data, you can delete saved scans and your account from your settings, or email privacy@textsight.ai.

Contact