Revecto
Help

Security

How Revecto handles your data and keeps renders safe.

Transport

The API is served over HTTPS only, and HTTP requests are redirected to HTTPS. HSTS is sent for one year, subdomains included.

API keys

A key is shown once, when you create or roll it, and is stored only as a one-way hash. Disable, roll or delete a key at any time; see Authentication.

Documents and templates

DataHandling
Documents and PDFsProcessed in memory, not stored.
Templates and their assetsStored until you delete them.

Each account's keys, templates and files are separated from other accounts'.

Call log

Each call records:

FieldContent
EndpointThe endpoint called.
StatusThe HTTP status of the response.
DurationHow long the call took.
SizesThe size of the HTML and of the PDF.
Request idThe X-Request-ID of the call.
EngineThe engine used.
ErrorThe error code and message, when the call failed.
Skipped resourcesThe number of skipped resources, with up to ten reasons and URLs (without query string).
TimeWhen the call was made.

It never contains your document or the PDF.

Rendering

AreaBehavior
ScriptsChromium does not run them.
Remote resourcesFetched by Revecto, not by the renderer, under fixed limits. See Remote resources.

Chromium sessions

AreaBehavior
SessionEach project gets its own browser session; no other project or customer renders in it.
NetworkThe browser makes no network request. Remote resources are fetched by Revecto before the render; see Remote resources.
LifetimeA session closes after five minutes without a Chromium render of the project.

Where data lives

Each project has a region, fixed when you create it, and the host of that region; see Regions. For subprocessors, locations and how long data is kept, see the privacy policy.

Error reports

Reports of errors in Revecto carry no request data or headers. A user appears in them only as an id.

Report a vulnerability

Email support@revecto.dev.

On this page