The short version
- Hearsay is not open yet. Right now this site holds one thing: the email address you put on the waitlist.
- Your API keys are stored so Hearsay can call those services on your behalf. Nothing else.
- Your social account tokens are stored so Hearsay can publish what you approved. Nothing else.
- Hearsay posts. It does not read. No timelines, no followers, no messages, no engagement data.
- We do not collect or resell anything about your audience, or about anybody else's.
- Transcripts come from podcasts that were published publicly.
What this covers
Hearsay is a desktop application that reads published podcast transcripts, writes and voices commentary about a moment you choose, renders it as a short vertical video, and — once you have approved that video — publishes it to social accounts you have connected.
This policy covers the information Hearsay handles in order to do that: the API keys you supply, the tokens for the accounts you connect, and the email address you give us if you join the waitlist. It applies to the Hearsay application, this website, and the service behind them.
Your API keys
Hearsay runs on your own API keys — Google Gemini for the writing and the artwork, ElevenLabs for the voice.
Those keys are stored so that Hearsay can call those services on your behalf when you ask it to generate something. That is the only reason they are stored and the only thing they are used for. They are not shared with anyone. They are not used for our own purposes, for other users, for testing, or for anything you did not initiate.
You can remove a key at any time. Removing it deletes it from storage, and Hearsay stops being able to generate with it. Your use of Google Gemini and ElevenLabs is also covered by their own privacy policies, since your requests go to them.
Connected accounts and tokens
When you connect a YouTube, Instagram, Facebook, TikTok or X account, that platform issues an access token. We store that token for exactly one purpose: publishing content you have approved to the account you connected it for.
It is not used for anything else, and it is not shared with anyone. Where a platform's API grants access broader than posting requires, we do not use it.
Disconnecting an account in Hearsay deletes its stored token. You can also revoke Hearsay's access from the platform's own settings, and doing both is the surest way to end the connection.
What we do not read
Hearsay posts. It does not read.
It does not read your timeline, or anyone else's. It does not read your followers or the accounts you follow. It does not read direct messages. It does not read likes, views, comments, watch time, or any other engagement data.
It does not build a profile of your audience. We do not collect, aggregate, analyse or sell information about the people who follow you or watch your videos — not to advertisers, not to data brokers, not to anyone. There is no audience data product here, because there is no audience data.
The only thing Hearsay does with a connected account is publish to it, after you have approved what is being published.
Podcast transcripts
The transcripts Hearsay works from are obtained from publicly published sources — podcasts that have already been released to the public.
It works from what is public. It does not use anyone else's credentials to reach material that is not.
The waitlist
Hearsay is not open yet, so there are no accounts and nothing is sold. The only thing this site collects is the email address you type into the waitlist form, and the date you submitted it. Nothing else is asked for and nothing else is inferred.
That form is handled by Web3Forms, which receives the address on our behalf and passes it to us under its own privacy policy. It is used to tell you once that Hearsay has opened. It is not added to a newsletter, not sold, and not shared with anyone else.
Because nothing is being sold, no payment processor is involved and we hold no card details, no billing address, and no payment records of any kind.
What is retained
Hearsay is not open yet, so the list below is short — and it is complete. There is no application in anyone's hands, which means there are no keys, no tokens, no job records and no published-post history to retain. Today we hold exactly one thing:
- the email address you submitted to the waitlist, and the date you submitted it — kept until Hearsay opens, or until you ask us to delete it, whichever comes first.
When the application does ship, this section gets rewritten before it does, and it will name the keys, tokens and records it then holds and how long each is kept.
Hearsay is a desktop application. The files it produces on your computer — the transcripts it has read, drafts, and the rendered videos themselves — sit on your computer. They are yours, and deleting your account does not reach them; delete them yourself if you want them gone.
Deleting your data and disconnecting accounts
- Disconnect a social account. Disconnect it in Hearsay, which deletes the stored token. Then revoke Hearsay's access in that platform's own settings.
- Remove an API key. Delete it in Hearsay. It is removed from storage.
- Come off the waitlist. Message @kookventures on X and ask. Your email address is deleted within 30 days, and there is no exception to this and nothing we keep back — no billing records exist, because nothing has been sold.
- Delete everything. Same request, same route. Once the application ships this will also cover your account record, any stored API keys and any remaining access tokens, within the same 30 days.
Who else sees anything
We do not sell personal information, and we do not share it with advertisers or data brokers.
Information reaches a third party only where you have asked for something that requires it: Web3Forms receives the email address you type into the waitlist form, the API providers whose keys you supplied receive the requests Hearsay makes on your behalf, and the platforms you connected receive the videos and captions you approved. We may also disclose information where the law requires it.
This website
This site is a set of static pages. It sets no cookies, runs no analytics, and has no tracking on it. There is nothing to opt out of.
The waitlist form is a plain HTML form. It loads no script, and this site sets no cookie for it; it simply posts what you typed when you press the button. The only information this site can send anywhere is the email address you choose to put in that box, and it goes nowhere until you submit it.
Pressing that button does send what you typed through Web3Forms, whose servers see the address before we do and who may set a cookie of their own on their domain, under their own policy. We do not control that and cannot switch it off. It is worth saying plainly rather than hiding behind the sentence above: reading this site is untracked, and submitting the form involves one other company.
Changes to this policy
If this policy changes, the updated version is posted on this page with a new date at the top. If a change is material — particularly to anything above about what is stored or what is read — we will say so rather than quietly editing the page.
Contact
Questions about privacy, requests to delete data, or anything you think this page gets wrong: @kookventures on X.