Consent Records

Live transparency report — updated in real time from our consent database

Every consent event (Terms of Service acceptance, email verification, eBay account linking, onboarding completion) is recorded with a tamper-evident SHA-256 hash. Weekly batch hashes are submitted to the Bitcoin blockchain via OpenTimestamps, creating an independent timestamp that cannot be forged or backdated.

Bitcoin Blockchain Anchors

Each week, all unanchored consent hashes are combined into a single batch hash and submitted to OpenTimestamps. Once confirmed on the Bitcoin blockchain, the timestamp is mathematically unforgeable.

# Status Events Anchored
#26 Anchored 6 events 2026-06-02 18:51:52 UTC
BATCH 69dc67234342dbdfa9368d1c3bdb664089053161b27d15c6aa11f46884151b76
OTS    f008a757e6eb0b9e0ea708f01000e597954eccbfe9e86803e55b12ba9108f1203179562bc0981f82…
#25 Anchored 2 events 2026-06-01 22:16:00 UTC
BATCH 4ad482d826c96df47db0aa9683bbf801edf9c77fd595ed5ae29145d9b2baa68f
OTS    f008c4e56313857a637408f0108189cca390b6e9090a93945cde4b49d008f12099e46bee3a0ca9df…
#24 Anchored 2 events 2026-05-28 20:40:10 UTC
BATCH 0ca6578a52b0baa990d22798e606d899744508932b1cdcba7e0cb61982b462e7
OTS    f0080ed48034900f2a6008f01030760eedefd2232364ef2ab8216428d208f020fb1424b304a22785…
#23 Anchored 1 events 2026-05-24 17:30:56 UTC
BATCH b0daf0d6cae5f7fa8303711b9356d798965a181a3345cc73ebd6931be380156f
OTS    f008fa7aa09d886959f208f01012b17ec293d4140a2ff7f89b19e8b5cc08f12037cd0ed53f43558b…
#22 Anchored 1 events 2026-05-22 01:09:30 UTC
BATCH accdbf714dd2df819359192075c84b5d50e0bc266ee22f5054b6503bead758e1
OTS    f0082d9003ee6f46d3ec08f0107c7d511b6c703c7909e1f1f147d0c9a008f0201c23c84a0e68fd48…
#21 Anchored 6 events 2026-05-21 03:46:44 UTC
BATCH b251c7fca4ff448e0a388a647233d21b447cc3eb3be30b2bc7f2c09f346b5e29
OTS    f008129fc834aa9fcb0408f120b4bbfde2e9bbb88b85b8d06ee437cd941659ba4a99077196dd7110…
#20 Anchored 1 events 2026-05-18 21:14:52 UTC
BATCH a0aff521ec8b3f02263bae05dc65963d929a012ad739f92968729cc1e2acd4b4
OTS    f008a27aadd88910860f08f010e6efd9d12307e99965380cba9dfc233e08f120963da027b0716b38…
#19 Anchored 1 events 2026-05-18 19:33:40 UTC
BATCH 38dd48d0db2fea3251df0ec76d9ad2ea5f02f3bc578e76e6544467eafede1a93
OTS    f0081a29977d483daf1808f120ac89e8530d95a4078dca6e634ec225649f66fb0c911bd87bef740b…
#18 Anchored 1 events 2026-05-17 16:41:50 UTC
BATCH f3fd776312473bb5183e7c9db57626df8a7d835df48fb30b4aa9e5d854ab4790
OTS    f008fca75a509501914108f1209081e362c38644c9d492efd1a60137ba41df8765ed3e4d91e22422…
#17 Anchored 1 events 2026-05-08 22:11:33 UTC
BATCH 593df097819ae79f5a12cb80e0683d8499d890ead47da78ebb24eb80921a6852
OTS    f008e64c82af7e6b3b1808f1208d871c3f5731662901c2e48e36b7e00479564c39bf3e2c2cbc4056…
#16 Anchored 2 events 2026-05-04 02:08:10 UTC
BATCH ecdd3f2711fc5296b84c33de5f7c3aa84eaa6e0226f3994ae3bf2d0bac7eca83
OTS    f0080a94d5a4505a0c2808f0109f409c0d1ba1ca2b5884997f9eaa764308f120f7776acb400cf73a…
#15 Anchored 2 events 2026-05-03 00:16:41 UTC
BATCH 085dcbc65752e703f4c6436acced9ba85e88714c34c3a98b74bcdf7c584f16f8
OTS    f008b0fb7782dad3d06208f010f308de1e14eb9b26b7cdf2299b7b86e208f1200966ec2e3ae82df4…
#14 Anchored 1 events 2026-05-01 05:12:56 UTC
BATCH f34e693ea1bf796ec08974ef50478381b92c5560ed0208ec130c2b07a40af8a7
OTS    f008f5b4057f215e7b1608f01031a0b247f22564b050f1fbc68142784708f02099e944e0c385883d…
#13 Anchored 1 events 2026-04-30 21:55:19 UTC
BATCH 2b78f447f885d565fa25123fa3468064255e31fc0bafb6c0a5623c302a7ab092
OTS    f008667b3eae5022bfad08f010bb8026c9f9e99938ae416538445e09cc08f02047674aea5b396297…
#12 Anchored 8 events 2026-04-22 23:31:56 UTC
BATCH bb4968f6b2e90069ef34c1eb6f61441473fff8aba678c2e6dbf18b3678cba697
OTS    f0083821f96f82f45fb908f010a14f569ce339c8918b8f8bc8ee6f0e7808f02033392dbee72ca6d7…
#11 Anchored 2 events 2026-04-22 01:10:25 UTC
BATCH 954729d84e5e27c294f92e1721bbc6bd80bcb633aa8041c4f1317b5b1b089ce3
OTS    f0087142e82b4600271c08f01028200148064d9630e6dd36a124b321e508f02066b5982117e49872…
#10 Anchored 2 events 2026-04-21 18:06:47 UTC
BATCH b059af2991865960364a966660686009acab5566d00a8bafb176c3d056dc51e3
OTS    f008ab61ad53dfe734af08f120631536993931870130118f7f0735d578fda2ba4b9b3bf15ce715c0…
#9 Anchored 12 events 2026-04-21 03:46:49 UTC
BATCH 3b3c035251877339d2c3780940ba6211afb4e816b7422ed1c6a004c7953c6677
OTS    f0088dbbf8f8722d44d408f020988445e60b8bb4750ef05f26f519678f11f9cba64a12b35d686c1b…
#8 Anchored 1 events 2026-04-20 17:40:32 UTC
BATCH f1884b00021169a53e207a5ddc633463c16a881819de3ac2acd6ec588276c7ea
OTS    f00853b4f73a428f6dbf08f12064dd5d025f4c201b10203bb0f06c57b811f5671392b89075322db1…
#7 Anchored 1 events 2026-04-08 22:57:30 UTC
BATCH f26bdd05292932d60594279ac12125869ee40fa9f6400836c85d316d4b7ef4fc
OTS    f008d7c0bee23c7fcfef08f010eb025bc488535ad7b7fda1ffb08c31c408f12056b1e2d2a2d88a1c…

Document Version Registry

Every version of our Terms of Service and Privacy Policy is registered with a SHA-256 content hash. This ensures that the exact document a user agreed to at any point in time can be verified cryptographically.

Document Version Content Hash (SHA-256) Effective Date
tos v1.17-20260528 1e693db24a5b… 2026-05-28 20:30:20 UTC
privacy v2.2-20260520 df9b092cdd3b… 2026-05-21 03:36:51 UTC
privacy v2.1-20260520 d8e92ca081b2… 2026-05-20 03:02:48 UTC
tos v1.16-20260520 fc4b98e86ed2… 2026-05-20 03:02:47 UTC
tos v1.14-20260515 0cd7274fd320… 2026-05-17 16:31:56 UTC
tos v1.13-20260502 ee9cbaebbcae… 2026-05-02 20:24:26 UTC
privacy v1.6-20260502 e3086440cad0… 2026-05-02 20:24:26 UTC
tos v1.12-20260430 be51df5cfb79… 2026-04-30 21:45:54 UTC
privacy v1.5-20260426 a271b0c5122d… 2026-04-26 18:43:31 UTC
privacy v1.4-20260414 e30c6a380ef8… 2026-04-17 06:02:13 UTC
tos v1.11-20260408 c69eb2cdc0e8… 2026-04-08 14:56:30 UTC
tos v1.10-20260407 5e19a2071da9… 2026-04-07 07:36:45 UTC
tos v1.9-20260407 7277e7f8bfa6… 2026-04-07 04:59:31 UTC
privacy v1.3-20260403 6a75f8ab115d… 2026-04-05 18:16:07 UTC
tos v1.8-20260403 aade42471566… 2026-04-05 18:16:07 UTC

How to Verify

To verify that a consent record has not been tampered with:

  1. Contact us at [email protected] — click the link and your email client will open with the request pre-filled
  2. We will provide the raw event data and its SHA-256 hash
  3. Independently recompute the hash from the event fields to verify it matches our record
  4. Use the batch anchor's OTS file to prove the hash existed before the Bitcoin block timestamp