Privacy
Policy

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 details needed to run your subscription. 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.

Account and billing

To run a $15 per month subscription we hold what a subscription requires: your account email address and the status of that subscription.

Payment is processed by Stripe under its own privacy policy. Your card details are handled by that processor and are not stored by us.

What is retained

While your account is active, we retain:

• your account record — the email address you signed up with and your subscription status;
• the API keys you have supplied, until you remove them;
• the access tokens for accounts you have connected, until you disconnect them;
• [LIST ANYTHING ELSE RETAINED — E.G. JOB RECORDS, ERROR LOGS, PUBLISHED-POST IDS — AND FOR HOW LONG]

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.
• Delete everything. Message @kookventures on X and ask. We delete your account record, any stored API keys and any remaining access tokens within 30 days.

The one exception is records we are legally required to keep, such as billing records retained for tax purposes. Those are kept for as long as the law requires and are not used for anything else.

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: the API providers whose keys you supplied receive the requests Hearsay makes on your behalf, the platforms you connected receive the videos and captions you approved, and Stripe handles your subscription payment. 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.

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.