Openwake · evidence pack

Front

https://front.com · record 567 · read 2026-10-13 · rules/v1 · generated 2026-10-23 04:12 UTC

Facts

Trains on customer data
unclear
No supporting text found in the documents read.
privacy policy · https://front.com/privacy-policy · confidence 0.20
Opt-out mechanism
You may opt-out of our marketing communications as described in the Opt-out of marketing section below.
“You may opt-out of our marketing communications as described in the Opt-out of marketing section below.”
privacy policy · https://front.com/privacy-policy · confidence 0.50
AI features
present
“We may share all categories of personal data with third parties that provide services on our behalf or help us operate the Service or our business (such as hosting, information technology and software, customer support, email and telephone communications, call recording, marketing, advertising, payment processing, user authentication, market/survey research, data brokerage, generative artificial intelligence, and analytics).”
privacy policy · https://front.com/privacy-policy · confidence 0.55
Model providers named
none named
No supporting text found in the documents read.
privacy policy · https://front.com/privacy-policy · confidence 0.20
Retention
30 days
“Customers can ask Front to delete their Customer Data as described in the Data Processing Addendum and such requests generally will be processed within 30 days.”
Hosting regions
not stated
No supporting text found in the documents read.
privacy policy · https://front.com/privacy-policy · confidence 0.20
Subprocessor notice
not stated
No supporting text found in the documents read.
privacy policy · https://front.com/privacy-policy · confidence 0.20

Subprocessors (1)

NameCategoryLocationQuoted from
Amazon Web Serviceshyperscalerunstated
“Customer Personal Data is encrypted both in transit and at rest. In transit, Front uses TLS 1.2 or greater for data encryption between Front and third parties, including customers. At rest, Front leve”

Sources read

DocumentURLReadContent hashLedger
privacy_policyhttps://front.com/privacy-policy2026-10-13a0b6183f7b84446f…seq 53218
dpahttps://front.com/legal/data-processing-addendum2026-10-13f23b92a925d13329…seq 53219
Ledger proof for this record.
seq 53346 · key 2f898a895f05b7a0 · 2026-10-13T05:19:26.694Z
hash efdebf1b85141505e810648ba8e5344c687f49c8403dbab279981c75ea3197a3
prev 0df9dc1d806ed6d72ba37442c8094f5a7b33dfba7cbe1b6e7fc85e27bec12d9a
payload fb80833c8543d4d79e2da187fbaff195df0e46674c074417654aeb6e249f6acb
signature bFq5ALiB96zo67nsRj3R/WEy38ND5QUREwtBa0hrVkb1qfAWOBSBF5Z4PPqi/XoFxRv58jYs0xxFH3j/ySC/BQ==
anchored 2026-10-13 at head seq 53553 29b831e17d49be9d0c48e24c727cfa82ce9b500faacabb488dae167a42404d31
Fetch /v1/keys; for each ledger entry recompute sha256(prev_hash|kind|ref_id|payload_hash|created_at ISO) and verify the Ed25519 signature over that hash. Anchors are committed to git; compare the anchored head with the chain.