Trust & security

Straight answers for your security review.

What Swiftly stores, where it lives, who can reach it, and how it leaves — written for the person who has to sign off.

Send us your questionnaire

Last updated September 2026

Data handling

What we store — and what we never touch.

Swiftly holds only what it needs to run your account and produce your work. Everything in it came from you.

What we store

The information you provide.

Account details and subscription status
Your Context Binder — the marketing information you choose to add
Project briefs, research, plans, and the assets Swiftly produces
Usage records for allowances and support

What we never store

The things that stay out of reach.

Card numbers — payment details live with our payment processor, end to end
Plaintext passwords — credentials are stored only as cryptographic hashes
Anything pulled from your systems without you — Swiftly holds only what you provide or approve

The stack

Where your data actually lives.

Swiftly runs on four layers of infrastructure. Each one touches a specific slice of your data, and nothing else.

Layer	Role	Posture
AI processing	Produces your research, plans, and drafts through a commercial AI API	Inputs and outputs are not used to train models under the provider's commercial terms
Cloud infrastructure	Application hosting, database, and authentication	Traffic served over TLS; stored data encrypted at rest; credentials hashed, never kept in plaintext
Third-party data APIs	Search, media, and market intelligence for research and brand monitoring	Sent only the lookup terms a request needs — keywords, brand names, domains. Your Context Binder and your work are never shared with these services
Payments	Billing and subscriptions	Card data never touches Swiftly's servers — handled end to end by a dedicated payment processor

Swiftly talks to its AI provider directly — no middleware, no resellers in the path between your Context Binder and the model. A current list of the providers behind each layer is available on request.

AI and your data

Your data produces your work. Nothing else.

Your Context Binder and project content are sent to the AI layer to produce your research, plans, and drafts. That content is not used to train models, and it is never used to build anything for another customer.

In transitEvery connection is encrypted over TLS.

At restStored data is encrypted in the database.

AccessProduction access is limited to the people who operate the platform, on a need-to-do-the-job basis. Your content is not opened by a person unless you ask for help with it.

Usage monitoringPlatform activity is logged and monitored, so unusual access or abuse gets noticed.

IsolationYour workspace data is scoped to your account. No customer's content informs another's.

ExportYour Binder and your assets are yours. Take them with you any time.