Skip to content
Authreads

Legal

Who touches your data, by category.

Every provider that could process personal data on Authreads' behalf, disclosed by category and purpose, never by vendor name.

Stack of sorted outbound parcels and envelopes ready for dispatch

Pending legal review

This page is a draft. It is not legal advice, a certification, or a representation of audited controls, and it will be replaced once reviewed.

What a sub-processor is, here

A sub-processor is any third party that could handle personal data on Authreads' behalf while delivering the platform or this site. We disclose sub-processors by category and purpose (what a function is used for) rather than naming specific vendors or infrastructure in marketing copy. Named vendor agreements and data processing terms belong in your specific agreement with us, available on request once this page has had professional review.

Categories, not a complete legal disclosure

This list reflects the categories of processing that exist today. It is not yet a legally reviewed, complete disclosure and should not be relied on as one. Request the current, complete list directly if it's needed for your own review.

Categories in use

Categories in use today

Transactional email delivery

Purpose

Sending sign-in codes, password-reset and account-security notifications to end users, and contact-form notifications and acknowledgements.

Data involved

Recipient email address and message content generated by Authreads.

Hosting and infrastructure

Purpose

Running the platform and this site.

Data involved

Whatever data is in transit or at rest to serve the request, never disclosed by vendor name in public copy.

Every sub-processor we use is bound to protect data at least as strictly as our own commitments to tenants, and is used only for the purpose disclosed above.

Changes to this list

When this page is finalized after review, material additions or changes to sub-processors will be communicated to tenants with notice, consistent with the agreement each tenant has with us. Until then, treat this page as directional, not contractual. See Trust for the broader compliance posture, and contact us for the current, complete answer.