Privacy notice

Last updated 2026-09-29

The short version: OwnLikeness, EvidenceSlip and the Rights Vault pilot are one family of tools from Honeycutt Ai Labs for detecting and documenting synthetic voice, image and video. A file you submit is analyzed on the Honeycutt Ai Labs server, not sent to a third-party AI API. A score-only check is not stored. A submitted receipt, an EvidenceSlip case, a registry enrollment and a Rights Vault record are kept in an append-only log on that server so you can retrieve them later; the underlying audio, image or video file itself is not kept in a separate archive after scoring. The registry additionally keeps a voice fingerprint tied to the claimant's name for the license term chosen, and erases it when that term ends or when deletion is requested. No tracking cookie, analytics script or third-party script loads on any page in this family.

What each part of the family does

OwnLikeness (voice and video) scores a file you upload for signs of synthetic generation and, if you choose to submit rather than just check, writes a receipt you can retrieve later. EvidenceSlip does the same for an image, by forwarding the image bytes internally to the same operator's image-analysis service on the same server; that internal call is not a third-party disclosure. The Rights Vault pilot is a login-gated internal tool where an authorized performer, agent or reviewer records agreements, authorizations and incidents. The registry lets a performer or their representative enroll a reference voice, image or video so platforms can later check new content against it.

What is submitted

Voice or video check (score only): the audio or video file you upload, used only for the duration of that request.
Voice or video receipt (submit): the same file, plus the performer name you enter, an optional source URL, and an optional claim describing what you are documenting.
EvidenceSlip: the image you upload, plus an optional performer name and claim.
Registry enrollment: a reference voice, image or video file, the claimant's name, a reachable contact (email or phone), the modality, a license term in years (10 by default), the claimant's consent to enrollment, and optional notes.
Rights Vault: a username and password to sign in, and whatever agreement, authorization or incident material an authorized user enters or uploads, including incident evidence files.
Early access: the form on the OwnLikeness home page sends nothing; it asks you to email hello@honeycuttailabs.com, and that email is handled as ordinary correspondence.

What is kept, and for how long

A score-only check (voice or video) is processed in memory for that request and is not written to any store.

A submitted voice or video receipt, an EvidenceSlip case, and a takedown-notice draft are written to an append-only, hash-linked record on the server: the performer or claimant name, contact where given, a SHA-256 fingerprint of the file, the timestamp, and the full scoring result. The underlying audio, image or video bytes are not written to a separate media archive after that request completes. These records are kept until you ask for one to be deleted; a deletion request is handled by hand within 30 days (see Contact below).

A registry enrollment stores the claimant name, contact, a SHA-256 fingerprint of the reference file, a derived digital fingerprint (see "Voice recordings and voice fingerprints" below for the voice case), and the record of the claimant's consent. The reference file itself is not stored as a separate media archive; the video-fingerprint step for a video enrollment does briefly write the uploaded video to a temporary file on the server to sample three frames, and deletes that temporary file immediately afterward. A registration is kept for its chosen license term (10 years by default; the enrollment form offers 1 to 70) and carries a stated expiration date. When an expiry purge runs, it clears an expired registration's fingerprint, reference-file hash, file name, claimant name, contact and notes. The service invokes this purge at startup and when processing registry requests; erasure is not promised at the instant the term ends. The registration ID, registration and expiration dates, reference-file size, modality, license term, consent flag and timestamp, chain-verification hashes and erasure metadata remain as an audit record.

Rights Vault incident evidence you upload is written to a file on the server and kept with its incident record until an authorized user, or the person it concerns, asks for it to be deleted; a deletion request is handled by hand within 30 days.

Voice recordings and voice fingerprints

A voice recording can identify the person who spoke it, so OwnLikeness treats voice with extra care and handles it in two different ways depending on which feature you use.

A voice check or voice receipt uses the recording only to compute a same-request score (metadata, a fingerprint-style signal, a transcription pass, and a synthetic-voice classifier). The recording itself is not kept in a separate archive after that request; a submitted receipt keeps the scoring result and a SHA-256 hash of the file, not the audio.
Registry enrollment is different: it deliberately computes and keeps a derived voice fingerprint (an MFCC-hash together with duration, sample rate, channel count and frame count) tied to the claimant's name and contact, specifically so that other content can later be checked against it. Honeycutt Ai Labs treats this fingerprint as a voiceprint, a biometric identifier in the sense of Texas's Capture or Use of Biometric Identifier law (Tex. Bus. & Com. Code sec. 503.001), and enrollment requires the claimant's consent before it is captured.

Why it is kept: so a platform or investigator can later query the registry to check whether a new piece of media matches a claim a performer already registered. How long: for the license term chosen at enrollment (10 years by default), after which the fields named above are cleared when an expiry purge runs. How to ask for deletion: contact hello@honeycuttailabs.com with the registration you want removed. There is no self-service deletion in this release; removal is done by hand on the server within 30 days of the request and erases the same fields as expiry does.

Server logs

The web server's access log is turned off for the upload and analysis routes, and the OwnLikeness services write no request log of their own. Standard web server and hosting infrastructure logs (connection metadata, request paths, response codes and error records) are separate from this application and are not covered by the "not retained" statements above. The web server's own logs rotate daily and are deleted after 14 rotations, so no entry in them is kept longer than about 15 days.

Your browser

No tracking cookie, analytics script or third-party script loads on any page in this family. Two kinds of storage are used, both first-party and functional:

The shared top bar on the OwnLikeness, registry, takedown and EvidenceSlip pages uses a single session-storage key (likeness-performer), cleared when you close the tab, to remember which performer you have selected in a dropdown so you do not have to re-select it on every page.
The Rights Vault sets one sign-in cookie, named pilot_session, only after you sign in; no cookie is set by simply visiting any page. It is marked HttpOnly, Secure and SameSite=Strict, contains an internal account identifier, an anti-forgery value, an expiry time and a signature, but no password, expires after 8 hours, and is deleted when you sign out. The Rights Vault also caches its own app shell files (stylesheet and script, nothing you enter) for offline use through your browser's service-worker mechanism; that cache never leaves your device.

Purpose and sharing

Information submitted is used only to produce the requested analysis or record and to protect the service from abuse. Honeycutt AI Labs LLC does not sell submitted media, receipts or registry data, and does not use them to train a model through this service.

Your choices

Do not submit a file, name or contact you are not authorized to submit. Registry enrollment is a deliberate, named record tied to the claimant's identity; only enroll a reference file for a performer who has agreed to that. A voice or video check that does not submit a receipt is the lower-footprint option if you only want a same-request score.

Contact

For a privacy request, including a deletion request for a receipt, a record or a registration, contact hello@honeycuttailabs.com.

Changes

Material changes to this notice will be posted on this page with a new date.

Terms