Privacy notice

This notice describes how Transposer works today. Transposer is run by Digital Forge Development, LLC (“Digital Forge”, “we”), a Michigan limited liability company, and is in a private beta, by invitation.

What Transposer collects

• Your sign-in. WorkOS runs sign-in for Transposer. It keeps your email address, whether it’s verified, and your name if you give one. Transposer reads them from WorkOS when it needs them, such as when you sign in. If you sign in with Google, Google shares your name and email address with WorkOS.
• What you bring in and make. Your sources (captures, audio and video files, transcript files and pasted text), their transcripts, your edits, the extractions and results you make, the questions you ask and their answers, and your library: templates, presets, contexts, tags and workspaces.
• Write with AI. The descriptions you give it and the drafts it writes, including ones you don’t save.
• Recordings. A capture, or an audio or video file you bring in, is uploaded to the server to be transcribed, then deleted (see Deleting and keeping).
• Usage. How many sources you bring in each month, and how much AI writing you use: extractions, questions, corrections, trials and drafts. It’s counted even on a plan with no limit.
• Activity. A record of the changes made in your account, when, and by which app. You can see it in Settings.
• Sign-in records. Your signed-in devices and connections: when each was made and last used, and what it may do.
• Logs. Transposer’s own application logs record what the service did, such as errors, by internal ids. They’re built to leave out your content and your email address.

Where it goes

• Digital Forge’s own server, in Michigan. Transposer runs on a server Digital Forge owns and runs. Transcription and extraction happen there, on its own graphics cards.
• WorkOS runs sign-in and sends sign-in emails. It keeps your sign-in details in the United States. It never receives your content.
• Cloudflare sits in front of the server. Every request between your apps and Transposer passes through it, and Cloudflare decrypts it at its edge to deliver it and to protect the service from abuse. So Cloudflare can process your content and your IP address, possibly outside the United States, under Cloudflare’s privacy policy. It also delivers app updates and this website.
• Backblaze stores the server’s nightly backups in the United States. They’re encrypted before they leave the server.
• Anthropic receives what Claude reads while helping Digital Forge run Transposer (see Who can read your content).

Who can read your content

Your content is stored encrypted, with keys specific to your account. Transposer has to read your content to transcribe it and extract from it, so it can unlock it whenever it’s running. That means Digital Forge, which runs the server, can read your content.

Digital Forge uses Claude, an AI assistant made by Anthropic, to help build and run Transposer, with the same access to the server. Whatever Claude reads while doing that work is sent to Anthropic to process, including on its servers in the United States. Anthropic keeps it for 30 days and doesn’t use it to train its models, except content its safety systems flag, which it may keep for up to 2 years and use for training (see Anthropic’s privacy policy). Transposer’s promise not to train on your content covers Transposer, not Anthropic. This is separate from connecting Claude to your own account, which is your choice (see AI apps you connect).

Transposer’s built-in administration commands show ids and counts, not your content, and the changes they make are recorded. That doesn’t limit the wider access to the server described above.

Cloudflare can also read your content as it passes (see Where it goes).

AI apps and scripts you connect

Access for AI apps and scripts is off until you turn it on. When you connect one, such as Claude or ChatGPT, you choose what it may do before it can do anything. Today that choice covers your whole account: an app allowed to read can read all your sources, transcripts, results and library.

What it reads leaves Transposer, and that company’s own terms apply to it. Revoking its access in Settings stops what it can do next. It doesn’t bring back what it already read.

Settings shows each connection and the changes it made. It doesn’t list everything a connection reads.

Deleting, and how long things are kept

While you use Transposer

• What you save stays until you delete it. Write with AI’s descriptions and drafts are kept too, and you can’t delete them yet.
• Some things expire on their own. A trial of a template, with its result, is erased an hour after it ends. A correction’s request and report are erased after 24 hours; the corrected transcript or result stays.
• Uploaded recordings. Once a transcript is saved, the server deletes the upload within minutes. If transcription fails, it keeps the upload for up to a day so it can try again, and never more than three days after it arrived.
• Logs and records. Transposer’s application logs, your activity and usage records, and your sign-in records have no set end date today.

When you delete something

• 7 days to restore. A deleted source, extraction, result or library item waits in Recently deleted for 7 days, where you can restore it.
• Then it’s erased from the live service, with the keys that unlock it. Deleting a source deletes everything made from it.
• Copies in earlier extractions. Deleting a template or context doesn’t remove the copies kept with extractions already made from it. To remove those, delete the extractions or their sources too.
• Backups. The whole server is backed up every night, Transposer included, and backups are kept for about six months. So a copy of something you delete, or of an upload that was on the server when a backup ran, can stay in backups for about six months.
• Copies made before updates. Before each update to the service, Digital Forge saves a copy of Transposer’s database on the server. These copies have no end date yet, so they can keep deleted content for longer.
• On your computer. The Windows app keeps a capture’s audio on your computer, encrypted. It removes that audio only if it learns of the deletion within the 7 days, and later connects to Transposer after the source is erased. Deleting the source in the app on that computer tells it at once. Otherwise it learns through its checks, which need it signed in and online; opening the app isn’t enough on its own. If it misses the deletion, the audio stays on your computer.
• Copies outside Transposer. Files you export, and anything an AI app has read, are outside Transposer’s control.

Deleting your account

To have your account deleted, email contact@digitalforge.dev. Deleting a whole account isn’t built yet, so it’s done by hand: your content in the live service, Write with AI drafts included, your sign-in, and your sign-in details at WorkOS. Copies already in backups and in database copies made before updates stay until those copies are removed, as above.

What we don’t do

We don’t sell your information or share it for advertising, and Transposer shows no ads. Transposer never uses your content to train AI models.

This website sets no cookies and runs no analytics. Its fonts and images come from the site itself.

Your choices

• Delete sources, results and library items in the app at any time.
• Export transcripts and results as Markdown files.
• Revoke an AI app’s or a script’s access in Settings.
• Ask what we hold about you, or have your account deleted, by email.

Details

• Your email address. Transposer doesn’t store it. It keeps the id of your WorkOS account and a hash of your address, which it uses to match an invitation to you.
• Signing in. Signing in through the app sets one cookie on api.transposer.io, for up to ten minutes, only to finish that sign-in. The sign-in page itself is WorkOS’s. The Windows app keeps its sign-in in Windows’ credential store on your computer. Transposer’s database keeps the app’s sign-ins, and the access tokens you create, only as hashes.
• What isn’t encrypted. Some details are stored without encryption so the service can work: ids, dates and times, lengths and sizes, word counts, statuses and usage amounts.
• Amazon Web Services holds one key that lets Transposer’s key service start after a restart. None of your content, and none of your account’s keys, go to it.

Children

Transposer isn’t meant for children under 13, and we don’t knowingly collect their information.

Changes

When the way Transposer handles your information changes, we’ll update this notice and its date, and email the people in the beta about any change that matters.

Contact

Questions about this notice or your information: contact@digitalforge.dev.