How Basecast handles your information

Last updated 3 November 2026

This policy explains what information Basecast collects when you use basecast.net, why, who it goes to, how long we keep it, and the choices and rights you have. It applies to visitors, to people with a Basecast account, and to people invited to join a podcast team. Questions about it go to privacy@basecast.net.

Who we are

Basecast (“we”, “us”) turns recorded video, such as a religious service or community event, into podcast episodes: it cuts out the parts you choose, makes the audio, and can publish it to Podbean. Basecast is run from Australia, and we are responsible for your information under the Australian Privacy Act 1988, and, where it applies to you, the EU and UK General Data Protection Regulation (GDPR).

STEVENSON, PAUL GEOFFREY, ABN 66 124 187 889

What we collect

You give us

Your account: your email address and, if you have one there, your name. If you sign in with Google, Google tells us your name, your email address and whether it’s verified. If you sign up with an email address, you also choose a password, which our sign-in provider stores. If you change it in Your account, the old and new passwords pass through our servers to the provider; we don’t keep or log them.
Podcasts and teams: each podcast’s name and plan, who is on its team and their role. When you invite someone, the email address you type in.
Your content: videos you upload, intros, outros and artwork, the parts you mark, and the episode details you enter (title, description, season and episode numbers, and so on).
Podbean access: for a podcast you host on your own Podbean account, its Podbean client ID and client secret. For a podcast Basecast hosts for you (the Publisher plan), the details you ask us to set up: its title, description, category, author, copyright line and logo.
Billing: when you pay for a plan, Stripe collects your payment details on its own page. We never see your card number. We keep the plan, the billing interval, whether the subscription is active, its renewal date, and Stripe’s customer and subscription references.
Messages: what you send us at privacy@basecast.net, support@basecast.net or sales@basecast.net.
Contact sales: when you use the Contact sales form, your email address, the message, and your name and organisation if you give them. You don’t need an account.
Support requests: when you use Contact support in Basecast, your request, with your account’s email address and ID, the podcast you had open, its plan and your role on it, so we can answer without asking.

We collect as you use Basecast

Service records: the files in each workspace (names, sizes, dates and lengths), how many clips each podcast has made this month, invitations sent, the episodes published to Podbean, which version of our Terms of Service you accepted and when, and whether you’ve unsubscribed from our welcome email.
Server logs: records of requests and errors, with your account’s random ID and podcast IDs, used to run and fix the service. We don’t record your IP address in our own logs, though our hosting and sign-in providers process it to deliver the service and keep it secure.
Analytics, only if you accept: which pages you visit and features you use, the plan and amount when you subscribe, your browser and device type, and your approximate location, through Google Analytics. When you’re signed in it’s linked to your account’s random ID, never your name or email. See Cookies.

Recordings of other people

The videos you upload usually show and record other people, and a recording of a religious service or gathering can reveal the religious beliefs of the people in it. Australian law and the GDPR treat religious belief as sensitive information. We process your recordings only to make and publish the episodes you ask for: we don’t watch, analyse, profile or share them for any other purpose.

You’re responsible for having permission to record, upload and publish the people in your videos, including any children, and for telling them how their recording will be used. Once you publish an episode, it is public on Podbean and in podcast apps.

How we use it

To run your account and sign you in.
To make your episodes: cutting the clips you mark, making the audio, adding your intro and outro, and publishing to Podbean when you ask.
To let teams work together: showing who is on a podcast’s team, and emailing invitations.
To answer Contact sales messages and support requests: we keep each one with our replies, email it to our sales or support inbox, and reply to your email address. We don’t use them for marketing.
To bill for paid plans, through Stripe, and keep billing and tax records.
To email you about your account and podcasts (see Emails).
To give support: Basecast’s support staff can open any podcast (but not your private Clip Creator) to help its team or set up a Publisher podcast.
To keep Basecast secure and working: limiting misuse such as invitation or contact-form spam, and finding and fixing faults.
If you accept analytics cookies, to understand how Basecast is used and improve it.

We don’t sell your information, use it for advertising, or make automated decisions about you.

Legal bases (GDPR)

If the GDPR applies to you, we rely on:

Contract: your account, making and publishing episodes, teams and billing.
Legitimate interests: security, logs, misuse limits, support, answering Contact sales messages and support requests, invitations sent on a team owner’s behalf, and the welcome email, which you can unsubscribe from.
Consent: analytics cookies, which you can withdraw at any time.
Legal obligation: keeping billing and tax records.
Explicit consent and your instructions: any sensitive information in recordings you choose to upload and publish.

We share information only with the services that run Basecast, each for its own part:

Amazon Web Services hosts Basecast in Sydney, Australia: sign-in, our databases, your files, the audio processing, and our emails. The website itself is delivered through Amazon’s worldwide network.
Podbean hosts the podcasts Basecast publishes to. When you publish, the episode, its details and its artwork go to Podbean, and Podbean’s privacy policy applies to them there.
Stripe takes payments and sells paid plans on our behalf, including working out tax. It receives the email address of the podcast’s owner, and keeps its own payment and invoice records under its privacy policy.
Google signs you in if you choose “Continue with Google”, and runs Google Analytics if you accept analytics cookies.
Cloudflare runs our domain’s DNS and forwards email sent to our addresses.
Your team: other members of a podcast see your name or email address, and your role. An invitation email shows the inviter’s name and email address.

We may also disclose information if the law requires it, or to protect people’s safety or Basecast’s rights.

Information sent overseas

We store your information in Australia. Google, Stripe, Podbean and Cloudflare may process it in other countries, including the United States. We use them only for the purposes above, and rely on their contractual commitments to protect it. If you are in the EU or UK, transfers out of the EU or UK are covered by those providers’ standard contractual clauses, or are needed to provide the service you asked for.

Emails

Welcome email, from welcome@basecast.net: once when you first sign in, and once when a podcast you add is first paid for. It has an Unsubscribe link; unsubscribing records the date on your account and stops it.
Account emails: sign-up and password-reset codes, from no-reply@basecast.net.
Invitations, from invitations@basecast.net, when someone invites you to a podcast team. If you weren’t expecting one, you can ignore it. Each podcast can send only a limited number a month.
Publisher plan setup: emails about setting up a podcast Basecast hosts for you, sent while we set it up.
Replies to Contact sales messages, from sales@basecast.net, and replies to support requests, from support@basecast.net, only when you’ve sent one. Replies to them reach our sales or support team.

The account, invitation and setup emails are part of the service, so they have no unsubscribe link. Replies to our other emails aren’t read: write to privacy@basecast.net instead. Our email provider stops sending to an address that bounces or reports our email as spam.

How long we keep it

Information	Kept
Uploaded videos	1 day after upload, then deleted automatically
Finished audio (mp3) files	14 days after they are made, then deleted automatically
Intros, outros and episode artwork	Until you delete them, or the podcast is deleted
Details of your files (file name, size, dates, length, and the Podbean episode each mp3 was published as)	As long as the podcast or Clip Creator exists, even after the file itself has gone
Your account, team memberships and invitations	Until you delete your account, or the invitation is accepted or withdrawn
Monthly usage counts	About 13 months, or until the podcast is deleted
Contact sales messages, support requests and our replies	2 years after the last message, then deleted automatically, even if you delete your account
Server logs	3 months (2 weeks for our test system and the sign-up step)
Database backups	Up to 35 days, so deleted records can remain in backups for that long
A Publisher podcast its owner has deactivated	Kept, including its Podbean details and files, so it can be restored, until you ask us to delete it
Billing records (Stripe customer and invoices) and Publisher requests	As long as tax and accounting law requires, even after a podcast or account is deleted

Deleting a podcast (its owner, in Account & settings) removes it from Basecast with its team, invitations, files and records. A Publisher podcast is deactivated instead, as above. Nothing already published on Podbean is changed by Basecast.

Deleting your account (in Your account) removes your login, your Clip Creator with all its files, your place on every team, invitations to your address, and your account record, including your email preference. If you own a podcast, hand it over or delete it first. Podcasts aren’t deleted with your account, and support requests are kept for the time shown above; ask us at privacy@basecast.net to delete them sooner.

Your rights

You can:

Delete your account yourself, in Your account, or ask us to.
Get a copy of your files from the Media pages while they’re kept, or ask us for a copy of the information we hold about you.
Correct information that’s wrong.
Withdraw consent to analytics cookies, and unsubscribe from the welcome email.
If the GDPR applies to you, object to or restrict how we use your information, and receive it in a portable format.

Email privacy@basecast.net from the address on your account. We’ll reply within 30 days, and may need to check it’s you. If you’re not happy with our answer, you can complain to the Office of the Australian Information Commissioner (oaic.gov.au), or, in the EU or UK, to your local data protection authority (in the UK, the ICO).

Cookies and browser storage

Needed to work: your browser keeps your sign-in, and settings such as light or dark mode, the podcast you last opened and episode details you reuse. Our sign-in page (run by Amazon Cognito) uses its own cookies to keep you signed in. Signing out removes your sign-in and the podcast information.
Analytics, optional: Google Analytics cookies (named _ga and _ga_…), which last up to two years. They’re off until you accept them in the cookie banner, and rejecting or withdrawing deletes them. We have turned off Google’s advertising features and signals.

Security

Everything travels over encrypted connections, and our files and databases are encrypted where they’re stored. Podbean client secrets are encrypted again with a dedicated key that only the parts of Basecast that use them can read. Access to a podcast is limited to its team and Basecast support. No system is perfectly secure; if a data breach is likely to cause you serious harm, we’ll tell you and the regulator as the law requires.

Children

Basecast accounts are for adults, usually acting for a religious or community group or other organisation. We don’t knowingly create accounts for children. Recordings of children are covered under Recordings of other people.

Changes to this policy

When we change this policy we’ll update the date at the top. If a change materially affects how we use your information, we’ll tell account holders by email or in Basecast before it applies.

Contact

Email privacy@basecast.net with any question or request about your information. You can also read our home page for how Basecast works.