Last updated 3 September 2026

Privacy Policy — Narrator Hub

The short version

Narrator Hub is a work-tracking tool for audiobook narrators. We collect what we need to run it and nothing else.

We do not sell your data. There is no version of this product where we sell your data.
We do not show advertising and we do not share your information with advertisers.
Narrator Hub does not currently take payment, so we hold no billing information at all.
Your projects, your contacts and your rates are visible to you and to people you deliberately invite into your workspace. They are not visible to other customers.
If you ask us for a copy of everything we hold about you, we will give you one.

The rest of this page is the same thing in detail.

Who we are

Narrator Hub is operated by Dean Miller Narration LLC, 2415 S Heather St, Cornelius, OR 97113.

For anything in this policy, including requests about your data, write to Dev@DMNarration.com. A real person reads that address.

What this policy covers

The Narrator Hub web application at app.mynarratorhub.com, the marketing site at mynarratorhub.com, and the emails we send you about your account.

What we collect

Information you give us when you sign up

Your email address. Required — it is how you sign in and how we reach you about your account.
Your name, or whatever display name you choose. Optional.
A contact email, if you want one different from your sign-in address. Optional.
How you heard about us, and any detail you add to that. Optional. We ask once, at signup. It tells us which of the places we talk about Narrator Hub are worth continuing, and it is not used for anything else.
Where you arrived from. If the link you followed carried campaign parameters (utm_source and its relatives), we store them. We also store the referring page address your browser reports — the page you were on immediately before you landed on ours. We are naming that separately because it is more revealing than a campaign tag: a referrer can identify the specific forum, group or private community you came from. We use it only to understand where customers find us, and we do not attempt to identify those communities or anyone in them.

Sign-in today is email and password. We do not currently offer signing in with Google or any other outside account; if we add it, this section will say so before it goes live.

Information you put into the product

This is the bulk of it, and it is yours:

Projects — book titles, authors, word counts, page counts, progress, deadlines, narration format, your estimated finished hours, your portion of a shared book, whether you are producing it yourself, your rate or fee, amounts received, payment status, and any notes you write.
Contacts — names, email addresses, phone numbers, companies, links and notes for the people you work with.
Who worked on what — the roles connecting your contacts to your projects.
Your workspace settings, including your words-per-finished-hour figure.

Information about people who are not you

This one deserves its own heading, because it is the part most tools skip.

When you add a client, an author, a co-narrator, a producer or an editor to your contacts, you are giving us information about someone who has not signed up for Narrator Hub and has not agreed to anything.

Here is how we treat it:

We store it because you asked us to and use it only to show it back to you and the people in your workspace.
We do not email those people. We do not market to them. We do not add them to any list. Adding someone as a contact does not create an account for them and does not tell them anything.
We do not combine it with anything else, sell it, or share it.
If one of them contacts us and asks what we hold about them, we will tell them and, where the law requires it, we will act on their request — which may mean asking you to remove or correct the entry, since it is your record.

And here is your part. Under privacy law in a number of places — the UK and EU in particular — you are responsible for the personal information you enter about other people. Enter what you need for your working relationship, keep it accurate, and take it out when it is no longer useful to you. If a client asks you to remove their details, remove them.

Information we collect automatically

A session cookie, so you stay signed in.
A workspace cookie, remembering which workspace you were last looking at if you belong to more than one.

Both are required for the product to work, are readable only by our server, and are not used for advertising or for tracking you across other sites. We set no other cookies.

Standard server logs — IP address, browser type, and which pages were requested — kept briefly for security and for diagnosing faults.
We do not use third-party analytics or tracking. There is no analytics package in the application and no tracking script on any page.

Information you send us on purpose

When you use the Help button to send feedback or report a problem, we receive your message along with the page you were on, your browser's user-agent string and the version of the app you were running. Those three make a bug report actionable. Please do not put anything sensitive in the message body.

Activity within your workspace

We keep a record of significant workspace events — at present, the completion of signup. As the product grows this will expand to cover what changed, when, and who did it, so that a workspace shared with an editor or an assistant has an honest history. Any such record is visible to your workspace and not to other customers, and we will update this section as it grows rather than after.

Payment information

Narrator Hub does not currently charge for anything, and we hold no payment information whatsoever. No card numbers, no billing addresses, no payment history.

When we do introduce paid subscriptions, payment will be handled by Stripe, a PCI-compliant payment processor: your card details will go to Stripe and be stored by Stripe, and we will never see your card number. This page will be updated before that happens, not after.

Why we hold what we hold

What	Why
Email address	To sign you in and to contact you about your account
Name and display name	To show who did what in a shared workspace
Projects, contacts, roles, settings	To provide the product — this is the product
How you heard about us, and where you arrived from	To decide where to keep talking about Narrator Hub
Feedback messages	To fix what you tell us is broken
Session and workspace cookies	To keep you signed in and on the right workspace
Server logs	Security and diagnosing faults

If you are in the UK or EU, the legal bases are: performing our contract with you (providing and billing for the product), our legitimate interests (keeping the service secure, fixing faults, understanding where customers come from), and your consent where we have asked for it.

Who we share it with

We share your information with a small number of service providers who help run Narrator Hub. Each one gets only what it needs, and none of them may use it for their own purposes.

Supabase — the database and the sign-in system. Your account and everything in your workspace lives here.
Vercel — hosting and delivery of the application.
Resend — sending mail generated by the product, such as notifying us when you send feedback. Account email, including signup confirmation, is sent by Supabase.

We do not currently share your information with a payment processor, because we do not currently take payment.

We will also disclose information if the law requires it, or where it is necessary to protect the rights or safety of our customers or of Narrator Hub. If we are ever compelled to hand over your data, we will tell you unless we are legally prohibited from doing so.

If Narrator Hub is ever sold or merged, your information may transfer to the new owner as part of it. You will be told before that happens, and the new owner will be bound by this policy until they give you a new one and a chance to leave.

We do not sell personal information, and we do not share it for cross-context behavioural advertising, as those terms are defined under California law.

Where your data is held

Your workspace and account data are stored in the United States — in Amazon Web Services' Oregon region (us-west-2), through our database provider Supabase. The application itself is served from data centres in the United States by our hosting provider, Vercel.

If you are outside that region — including in the UK or EU — your information will be transferred there. Where that transfer requires a legal mechanism, our providers rely on the European Commission's Standard Contractual Clauses.

How long we keep it

While your account is open, we keep what you have put in, because taking it away would break the product.
After you close your account, we keep your workspace for 30 days, so you can come back or take a copy. After that we delete it.
If you ask us to delete your account outright, we do it, and we do not wait out the period above.
Backups roll off on their own schedule, so deleted data can persist in a backup for a short period after it is gone from the live system. It is not restored to the product and is not used for anything.

Your rights

Whoever and wherever you are, you can:

See what we hold. Ask, and we will tell you.
Take a copy with you. Ask us and we will send you your projects and contacts as CSV, which another tool can read. We do not charge for it and we do not make you explain why.
Correct it. Most of it you can edit yourself. For the rest, ask.
Delete it. You can delete projects and contacts yourself, and you can ask us to delete your account entirely.
Object to what we do with it, or ask us to restrict it.
Complain. If you are in the UK or EU you may complain to your data protection authority. We would rather you told us first, but it is your right either way.

We will not charge you for any of this, and we will not make the product worse for you because you asked.

To exercise any of these, write to Dev@DMNarration.com. We respond within 30 days, and usually a great deal faster, because there is not a queue.

Security

Everything travels over HTTPS.
Every table in our database enforces workspace isolation at the database level, not only in the application. That means the separation between your data and another customer's is checked by the database on every single query, rather than depending on the application asking the right question. There is an automated test in our build that attempts to read across that boundary and fails the release if it ever succeeds.
Passwords are handled by our sign-in provider, Supabase, and are never stored by us in a readable form. Nobody at Narrator Hub can see your password.
Access to production data is limited to those who need it to operate the service.

No system is perfectly secure, and anyone who tells you otherwise is selling something. If we discover a breach affecting your personal information, we will tell you and the relevant authorities as quickly as we can, and we will tell you what actually happened.

Children

Narrator Hub is a tool for working professionals. It is not directed at children and we do not knowingly collect information from anyone under 16. If you believe a child has given us information, write to us and we will remove it.

Changes to this policy

We will update this page when the product changes. The date at the top always reflects the current version.

If a change materially affects your rights — a new category of data, a new reason for using it, a new party we share it with — we will email you before it takes effect, rather than quietly changing the page and dating it.

Contact

Dean Miller Narration LLC
2415 S Heather St, Cornelius, OR 97113
Dev@DMNarration.com