Skip to content
AmazFlow
ProductWorkIQSolutionsSecurityPricingCompany
Sign inTry the demoTalk to sales
ProductWorkIQSolutionsSecurityPricingCompany
Sign inTry the interactive demoTalk to sales

INTERNAL / Build-Pending-IT

INTERNAL — not customer-facing until Legal clears

This is an INTERNAL preview surface. It is not an EXTERNAL publish. Claims Clearance for new EXTERNAL wording remains with CLO.

Title
Evidence Retention Policy
Version
GATED
Effective date
set on publish after MSA greenlight
Last updated
set on publish after MSA greenlight
Contact
legal@amazflow.com
LEGAL

Evidence Retention Policy

INTERNAL USE — OPERATOR / DESIGN-PARTNER OPS. Same substance as the gated customer draft. Safe for internal runbooks, IT release-readiness, and answering “how long do we keep evidence?” inside AmazFlow. Do not paste Term+30 into customer-facing marketing, the Security page, or the Privacy schedule as a binding public promise until MSA §9.6 is greenlit. For external conversation before greenlight, use Claims Clearance: “as agreed in the Order Form / MSA.”

Contents
  1. Gated status
  2. Operator summary
  3. One-liners
  4. Related documents

1. Gated status

GATED — PENDING JAYLEN GREENLIGHT

The default retention period (Subscription Term + thirty (30) days) mirrors MSA Draft v0.2 §9.6. Until that section is founder-greenlit and the MSA is customer-ready, do not treat this as a standing customer commitment. Until greenlight, point prospects to: “Evidence and audit retention is as agreed in the Order Form and MSA.” (Claims Clearance v0.1.)

INTERNAL USE — OPERATOR / DESIGN-PARTNER OPS

Same substance as the gated customer draft. Safe for internal runbooks, IT release-readiness, and answering “how long do we keep evidence?” inside AmazFlow. Do not paste Term+30 into customer-facing marketing, the Security page, or the Privacy schedule as a binding public promise until MSA §9.6 is greenlit. For external conversation before greenlight, use Claims Clearance: “as agreed in the Order Form / MSA.”

2. Operator summary

  1. Evidence Records = workflow run history, verification results, evidence captures, approval/escalation history, and related audit history for that Customer’s Workflows.
  2. Target default (aligned to MSA Draft v0.2 §9.6 and IT design-partner bar): retain for Subscription Term + 30 days after that Subscription Term ends, unless the Order Form sets a different window.
  3. Export: during that window, Customer may request export of Evidence Records with other Customer Content (MSA Draft §8.7 — 30-day export window on written request). After the retention window, delete or de-identify per DPA, except law / dispute / enforcement holds.
  4. Backups: live delete ≠ instant backup purge; Privacy schedule backup window (≤35 days) still applies.
  5. Access: Customer admins + AmazFlow need-to-know operators; logged; prefer run IDs over pasting regulated records into support tools (Subprocessors / AUP posture).
  6. Honesty: evidence packs = runs / checks / approvals. Not business-outcome warranties. Not SOC 2. Not blanket HIPAA.
  7. Until founder greenlight: do not tell customers the Term+30 default is already a standing AmazFlow public policy; say retention is as agreed in OF/MSA, and keep Term+30 as the internal design-partner / draft-MSA target.

3. One-liners

Operator one-liner (internal). We retain Evidence Records for the subscription term plus 30 days as our draft-MSA / design-partner default; OF can override; export on request during the window; packs document runs, verification, and approvals — not certifications or business outcomes.

External one-liner (pre-greenlight). Every design-partner workflow we call live keeps a retrievable evidence and audit trail. Retention is as agreed in your Order Form and MSA.

4. Related documents

Processing of Customer Personal Data: Data Processing Agreement. Website / AmazFlow-as-controller data: Privacy Policy. Security controls (no fake certifications): Security. Acceptable configuration of high-impact actions: Acceptable Use Policy.

Contract and retention questions: legal@amazflow.com. Security inquiries: security@amazflow.com. Privacy requests (website / AmazFlow-controller data): privacy@amazflow.com.

Legal hubPrivacyData Processing AgreementSecurity
Privacy · Terms · Legal hub

AmazFlow, LLC · a Georgia limited liability company · All legal documents

AmazFlow

The execution layer for operations.

© 2026 AmazFlow. All rights reserved.
PlatformProductWorkIQSolutionsPricingTry the interactive demoSign in
TrustSecurityLegal & Trust CenterPrivacyData ProcessingSubprocessorsCookie PolicyTermsAcceptable Use
CompanyAboutContactsales@amazflow.comsecurity@amazflow.com