Openwake · evidence pack

Lovable

https://lovable.dev · record 583 · read 2026-10-13 · rules/v1 · generated 2026-10-23 04:08 UTC

Facts

Trains on customer data
opt_out
“* Train and develop our AI models — train, develop, and improve our AI models, as described in Section 5 (with an opt-out);”
privacy policy · https://lovable.dev/privacy · confidence 0.60
Opt-out mechanism
* Train and develop our AI models — train, develop, and improve our AI models, as described in Section 5 (with an opt-out);
“* Train and develop our AI models — train, develop, and improve our AI models, as described in Section 5 (with an opt-out);”
privacy policy · https://lovable.dev/privacy · confidence 0.50
AI features
present
“We use Customer Content and Usage Data — which may include Personal Data — to train, develop, fine-tune, and improve our AI models and AI-powered features, including models we operate within the Services and models we may make available to customers through Lovable products such as the AI Gateway.”
privacy policy · https://lovable.dev/privacy · confidence 0.55
Model providers named
none named
No supporting text found in the documents read.
privacy policy · https://lovable.dev/privacy · confidence 0.20
Retention
not stated
No supporting text found in the documents read.
privacy policy · https://lovable.dev/privacy · confidence 0.20
Hosting regions
not stated
No supporting text found in the documents read.
privacy policy · https://lovable.dev/privacy · confidence 0.20
Subprocessor notice
20 days
“In the event that the Customer does not wish to consent to the use of a new Sub-processor, the Customer may notify Lovable within twenty (20) business days of Lovable notifying the Customer, that the Customer does not consent on reasonable grounds relating to the protection of Personal Data by contacting privacy@lovable.dev.”
dpa · https://lovable.dev/data-processing-agreement · confidence 0.55

Subprocessors (0)

NameCategoryLocationQuoted from
None listed.

Sources read

DocumentURLReadContent hashLedger
dpahttps://lovable.dev/data-processing-agreement2026-10-09ddc8507f1259b25e…seq 47766
privacy_policyhttps://lovable.dev/privacy2026-10-13c4ae083f849c0ede…seq 53310
termshttps://lovable.dev/terms2026-10-13e62f53fa5578509d…seq 53311
Ledger proof for this record.
seq 53362 · key 2f898a895f05b7a0 · 2026-10-13T05:19:27.800Z
hash cf449683f9a47492b74b32a04c19a85bc702d3ac2e97da62db12d0f079cd9477
prev cf2cb9f0855ca364be50fc3a4295c28947a7e080879999a98eca88a37282ece2
payload be44dfc7564b887100b9d867f37e24a60b1a95e13eb6e11dfc69abdee0837a2f
signature fW7yL46d8mXupYPH8xxXB8/fXwojmx6yt6Kyf1mWtrxrfkL7tBMvvlzet/qW7uxVjPs+DjTIq0aFOZB4A94UDw==
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.