DocumentationAccount
Data, privacy and security
What Praised stores, how long it is kept, who can sign in and how, and where changes are recorded.
Praised stores your account details, your billing details and your measurement data. Every request resolves to one workspace, and data access is scoped to that workspace.
What Praised stores#
Identity: your email address, your name if you give one, and your workspace. A password is stored only as a PBKDF2-SHA256 hash with a per-user salt.
Billing: your plan and your invoice history. Card details are entered directly with Stripe and never reach Praised’s servers.
Product usage: which features an account used and when, stored against the workspace.
Measurement data: the brands, questions and pages you track, the readings computed from the answers, and the findings and content you create. No other customer can open your brand, your question list or your readings.
How answers are stored#
An answer to a tracked question is stored once, keyed by the question text, the engine, the model, the place and the language. The stored answer carries no workspace, no brand and no record of who asked.
On Enterprise, a question marked private is never answered from the shared store, and its answers never serve another workspace.
Praised sends AI providers the questions about brands, products and categories, and the text of public pages that a page audit, a brand profile or a draft reads. Customer lists and account details are not sent.
Hosting and encryption#
Praised is hosted on Railway, which holds the application databases and their backups. All traffic is served over TLS.
Credentials for connected tools, such as single sign-on client secrets and Google service-account keys, are encrypted at rest. A single sign-on client secret is never returned by any endpoint.
Workspace API keys and personal API keys are stored only as hashes, shown once when they are made, and can be revoked at any time.
How long data is kept#
Raw AI-crawler requests are kept for a number of days set by the plan. Older days are kept as daily totals.
| Plan | Raw crawler requests kept |
|---|---|
| Free | 90 days |
| Pro | 455 days |
| Scale | 455 days |
| Agency | 730 days |
| Enterprise | 730 days |
Account and measurement data are kept for as long as the account exists.
In a free tool, the query, the domain and the tool are kept for 18 months and then deleted, with no IP address or visitor identifier stored beside them.
Signing in#
You can sign in with an email address and password, or with Google. With Google, Praised receives your email address and no password.
Single sign-on through OIDC or SAML 2.0 is on every paid plan, and the Free plan does not include single sign-on. An Owner sets single sign-on up in Settings › Team & access › Single sign-on.
Claiming an email domain for single sign-on needs a verified member address at that domain. A domain routes to one workspace only.
SCIM provisioning lets a directory such as Okta or Entra ID create, deactivate and remove members. Removing a member through SCIM ends that member’s live sessions.
Audit log#
The audit log records sensitive changes in the workspace, including sign-ins, API keys, members and invites, roles, single sign-on, connectors, shares and workspace settings.
Open the audit log in Settings › Team & access › Audit log. Only an Owner can read the audit log, and entries cannot be edited or cleared.
Certification and vulnerability reports#
Praised is not certified against SOC 2 or ISO 27001.
Report a vulnerability to hello@praised.co with enough detail to reproduce the issue.
Not answered here? Contact us, or check your website free.