Privacy Policy

1. Who we are

Streamboth is a product of Elannfarm Ventures, a business registered in Ghana ("we", "us"), which runs streamboth.com and is responsible for the personal information described here. This policy covers the Streamboth website and studio.

2. What we collect

• Account details. When you create an account (you need one to host a studio), we receive your email address and an account ID. If you sign in through another service, such as Google, we may also receive your name and profile picture from it. Our sign-in provider, Clerk, handles your login.
• Plan and billing. Your plan, your subscription status, and the customer and subscription references our payment provider, Stripe, gives us. Stripe handles your card details; we never see or store them.
• Broadcast records. When each live broadcast starts and ends, how many destinations it went to, and which platforms by name (such as YouTube or Kick — not your stream addresses or keys). If something goes wrong during a broadcast, such as a platform dropping the connection, we record what happened and the error message, so we can help when you ask. We use these to apply your plan's limits, such as monthly stream minutes, to show your usage, and to fix problems.
• Support notes. Our team may keep short notes on your account to help with support, such as what we did about a request.
• When and how you use Streamboth. The days you use Streamboth while signed in, and when you last did. While you're signed in, we also keep a record of what you do in your account, with the time: the pages of Streamboth you open, opening the studio and its room code, and actions such as saving scenes or songs, changing your room code, scheduling a show, connecting or disconnecting YouTube or Facebook, starting, renaming or deleting a cloud recording, adding a Bible, and opening checkout or billing. It holds only what was done and short names (such as a plan, a room code or a show's title) — never your stream keys, the words of your songs or messages, or what's in your shows. Our team uses it to help you when you ask for support and to understand how Streamboth is used. We keep each entry for 400 days, and delete it with your account.
• Your country and city. While you're signed in, we work out roughly where you are — your country, region and city — from your internet (IP) address, using a location database kept on our own server (IP Geolocation by DB-IP), so your address isn't sent to anyone else for this. We keep only the place, not the address, and note in the record above when it changes. It's approximate (often the city your internet provider is in). Our team uses it to understand where Streamboth is used and to help with support, such as connection problems in your region.
• Messages from us. Which of our messages and policy-change notices you've seen and pressed OK on in the app, so each one is shown to you only until you do; which ones we've emailed you, so nobody gets one twice; and whether you've unsubscribed from our emails.
• Saved scenes and songs. The scenes you save in the studio (their names, layouts and colors) and the songs you save for Lyrics (their titles, words and credit lines) are stored with your account, so they're there on any computer you sign in on.
• Your connected YouTube channel. If you connect your YouTube channel in the studio (Room → Comments, on the Pro plan and up), Google gives us permission to use it on your behalf. We keep your channel's name and picture, and an access token from Google, stored encrypted. We use it only to read your stream's live chat while you're live through Streamboth and to post the replies you write in the studio. We don't use it to change or delete anything on your channel, or for anything else. Connecting a channel uses YouTube API Services, so Google's own handling of that information follows the Google Privacy Policy.
• Your connected Facebook Pages. If you connect Facebook in the studio (Room → Comments, on the Pro plan and up), Meta gives us permission to use the Pages you manage on your behalf. We keep their names and pictures, which Page you picked, and access tokens from Meta, stored encrypted. We use them only to find your Page's live video while you're live through Streamboth, read its comments, and post the replies you write in the studio, as your Page. We don't post anything you didn't write, and don't use them for anything else.
• Messages you send us. When you use our Contact page, we receive your name, email address, the topic and your message, and which account sent it if you're signed in. If we reply from Streamboth, we keep our reply with your message. If you message us on WhatsApp instead, the chat goes through WhatsApp (part of Meta) under its own privacy policy, and we see your number and messages there. We keep a message until we've dealt with it and deleted it.
• Visits to our website. When a page of our website opens, we count the visit: which page it was, the day, and where you came from (for example a Google search, a Facebook or WhatsApp link, or typing our address). To count each visitor once a day, we make a code from your IP address and browser details with a secret that changes every day and is never stored. We keep only that code, not your IP address, and it can't be linked to you or to your visits on other days. This uses no cookies, and we don't learn your name, email or phone number from it.
• Cloud recordings (Business and Apex). If you're on Business or Apex and tick ☁ Cloud next to Record, the recording is uploaded from your browser to storage we rent from Cloudflare (R2), with its name, size, length and date. Only you can see, download or delete it, from My recordings on the Studio page. We keep it until you delete it. If your account stops being on Business or Apex, we keep your recordings for 30 days so you can download them, then delete them; if you ask us to delete your account, we delete them too.
• Verses you share with phones (Scripture → Audience). If you switch on Audience in the website's Scripture, or in the studio's Brand → Script → Audience (the same page and link), the verse on your screen and the day's earlier ones (the Bible text, in the versions you pick, and a name you can give the page) are kept with a link we make for your account, so anyone with the link or its QR code can read them. Nothing about you or the people reading is shown on that page. When you switch it off, we clear the verses and the link stops showing them.
• Live captions on the Audience page. If you switch on Live captions in Scripture → Audience (or the studio's Script → Audience, which hears what's on air), the last few lines heard by your computer's speech recognition (or AnnanAI, if you picked it) (and their translations, made on your computer) are sent to our server and shown on your Audience page to anyone with its link, as they're said. Only the latest 30 lines are kept; they're cleared when you stop sharing.
• Scripture's streaming software link. If you use the link for OBS, vMix or other streaming software, what's on your Scripture output (the verse or slide, its look, and your logo) passes through our server to the pages open on that link, as you present it. We keep only the link itself and, in memory, the last thing sent, so a page that reloads shows it again. "Make a new link" stops the old one.
• Prayer requests. If you let people send prayer requests from your Audience page, what they write (and a name, if they give one) is kept with your account so only you see it, in Scripture or the studio's Script → Audience. You can mark them prayed for or delete them; we delete each one after 30 days. To stop one address sending too many, we count requests from it for a few minutes, in memory only.
• Teleprompter notes you share for editing. If you share a note from the website's Teleprompter (🔗 Share for editing), its name and words are kept on our server, with a link we make, so the people you send the link to can edit it with you live. Anyone with the link can read and change it. When you stop sharing, we delete them from our server; your own copy stays in your browser.
• Technical information. Like any website, our servers and providers receive your IP address and basic browser details when you connect. We keep short-lived server logs to run Streamboth and keep it secure.

If you join a studio as a guest, without an account, all you give us is the display name you type in, which the other people in the studio see.

3. What stays on your device

• Recordings are made in your browser and saved straight to your computer. They're never uploaded to us — unless you're on the Business or Apex plan and tick ☁ Cloud next to Record (see "Cloud recordings" in section 2).
• Images and videos you add in the Media tab are kept in your browser's storage only while you're in the studio, so a refresh brings them back, and they're cleared when you leave. Any picture or video you choose as a lyrics background stays in your browser's storage so it's there next time. None of these are uploaded to us. Captions you make for a video (CC) are made in your browser too, and kept with the video for the visit.
• Background music you add in Media → Music is kept in your browser's storage until you delete it, and played from there. The files are never uploaded to us; only their sound goes out as part of your stream when you're live.
• Sound board sounds you add are kept in your browser's storage the same way, and PDF slides like the rest of your media; neither is uploaded to us — only what's on screen and heard goes out in your stream.
• Stream keys and RTMP addresses are saved in your browser. They're sent to our server only when you go live, used to connect to the platforms you chose, and not stored afterwards.
• The website Teleprompter's camera, coach and rehearsals. The camera picture behind the words is shown only in your browser. A rehearsal's recording is kept in your browser for that visit, to play back, and never uploaded. Follow my voice, the coach and rehearsals use your browser's built-in speech recognition, as live captions do (see section 4): in Chrome and Edge, the browser may send your microphone's sound to Google or Microsoft to turn it into text. The script helper's ✨ choices and the translation under each line use Chrome's own built-in AI and translator on your computer; your words aren't sent to us for them. Voice commands use the same speech recognition. Word, PDF and text files you import are read in your browser and never uploaded; a Google Doc you import is fetched from Google by our server, using only the link you paste, and passed straight to your browser — we don't keep it.
• The Teleprompter's captions, versions and producer cues. When you turn on Captions for your stream, the line you're reading goes through our server to the captions link (for OBS and the like) as you read; it isn't kept. Earlier versions of your notes are kept in your browser only. Cues a producer sends from the phone remote go through our server to your page and aren't kept.
• Scripture's confidence monitor and offline copy. The confidence monitor gets what's on screen, the next verse, your notes for the preacher and the service clock through our server on your output link; only the last of each is kept, in memory. Get ready for offline keeps a copy of the console's own files, the Bibles you use and your songs list in your browser on that computer, so it keeps working if the internet drops.
• The website Scripture's logo, songs and "My verses". A logo you add for the lower third is kept in your browser. Songs you save in Scripture are kept with your account, as the studio's Lyrics are (see section 2). On the Audience page, verses people save with ♡ stay on their own phone, and "Email them to me" opens their own email app — we don't send or see it.
• Studio settings, such as layouts, colors, filters, overlays and lyrics looks, are saved in your browser.
• Web pages you open in Brand → Browser load in your browser, straight from their sites, like any page you visit. To tell you whether a site allows being shown inside the studio, our server first asks that site for its headers, with only the address you typed (and, for a YouTube @name link, asks YouTube which channel it is); the address isn't kept. Your recent addresses are saved in your browser. The page opens in a window of its own; when you show it on your stream, Chrome shares that window (you pick it), with its sound, and it goes out like the rest of your stream.

4. Video, sound and chat in the studio

• Camera, microphone and screen-share video and sound travel directly between the browsers of the people in a studio, encrypted. When a direct connection isn't possible, they may pass through an encrypted relay service, which doesn't keep them.
• When you go live, your studio's output passes through our servers, which convert it and send it to the platforms you've chosen. We don't keep a copy. Those platforms receive your broadcast because you send it to them, and their own privacy policies apply.
• Chat messages and caption text are passed through our server to the other people in your studio. We don't store them.
• While you're live with a YouTube channel or Facebook Page connected, your stream's live comments (each viewer's display name, picture and message) are passed through our server to you and your co-hosts in the studio, and your replies go back to YouTube or Facebook. We keep the latest comments only in memory while the broadcast lasts, so they're there if you reload the page, and never store them.
• Live captions, which are off unless you turn them on, use your browser's built-in speech recognition. In Chrome and Edge, the browser may send your microphone's sound to Google or Microsoft to turn it into text, under their privacy policies. On Apex and the Service plans the host can pick AnnanAI to write the captions instead (Captions → Captions with): then the sound that's on air is sent from the host's browser to AssemblyAI (see section 6), and our server counts how long AnnanAI captions run each month (minutes only — not the sound or the words) to work out the included hours and any charge.
• Translated captions, off unless you pick a language, use Chrome's built-in translator, which works on your computer: Chrome downloads the language once, and the caption text isn't sent to us or anyone else to be translated.
• "Keep a transcript for the recap", off unless the host turns it on, writes down what's said while live the same way as live captions (your browser's speech recognition), without showing it on screen. It stays in the host's browser for the show's recap — we don't store it.
• The AnnanAI show summary, only when the host asks for it in the recap: the transcript (what was said, with names and times) and the show's scenes and moments are sent through our server to Anthropic, whose Claude model writes the summary, title ideas, chapters and notes. We don't keep it; Anthropic handles it under its commercial terms and doesn't train on it. If this isn't switched on, the summary is written by Chrome's built-in writer on the host's computer instead.
• Sermon Notes in the website's Scripture, only when you press ✨ Summarize: the whole transcript (what was heard since it was last cleared) and the references of the verses shown are sent through our server to Anthropic, whose Claude model writes the AnnanAI summary, the statements and the outline. We don't keep them — they're kept in your browser; Anthropic handles them under its commercial terms and doesn't train on them. If this isn't switched on, Chrome writes the summary on your computer instead and nothing is sent.
• Past sermons you import in the website's Scripture (Sermon Notes → Transcripts and book → Import a past sermon): the audio or video file is uploaded from your browser to storage we rent from Cloudflare (R2), AssemblyAI (which runs AnnanAI's listening) transcribes it from there, and the file is deleted from our storage once it's transcribed; if you paste a link instead, AssemblyAI fetches the file from that link. The transcript is then kept with your account like any saved sermon, with the title, date and series you give it, and we keep a record of each import (its title, status and length) to count the month's import hours.
• Live notes in Sermon Notes, only while you have them switched on and Listening is on: every few minutes the whole transcript and the verses shown are sent through our server to Anthropic, the same as pressing ✨ Summarize.
• A book's introduction, only when you make a book with "AnnanAI writes the introduction" ticked: each chapter's title, subtitle, headings and opening lines, and the book's title and author, are sent through our server to Anthropic, whose Claude model writes it. The cover picture, dedication and foreword you add are kept only in your browser and go into the file made on your computer. Quote cards are made on your computer too; nothing is uploaded.
• Ask AnnanAI in Sermon Notes, only when you ask a question: your question, the conversation so far and that sermon's transcript (today's, or one you saved) with the verses shown are sent through our server to Anthropic, whose Claude model answers. We don't keep the questions or answers — they stay on the page until you close it or start again; Anthropic handles them under its commercial terms and doesn't train on them.
• Sermon transcripts you save in the website's Scripture (Sermon Notes → Transcripts and book): the whole transcript, the title and date you give it and the verses shown, kept with your account until you delete it. When you download a sermon or a book, the transcript goes through our server to Anthropic, whose Claude model (AnnanAI) writes it as a readable chapter; we keep the chapter with the transcript. The Word and PDF files are made in your browser.
• Your public sermon library (Scripture → Sermon Notes → 🌐 Sermon library), only for the sermons you tick 🌐: its name, web address and "About" line, and for each sermon its title, date, series, the verses shown, the whole transcript and the summary, key points and outline that AnnanAI writes from it (sent through our server to Anthropic once, when you first tick it). Anyone with the link can read them; untick a sermon to take it off.

Chronicles (a church's records)

Chronicles (streamboth.com/chronicles, under Standalone Apps) is where a church keeps its own records: the people of the church and their households (names, phone numbers, email and home addresses, birthdays, gender, membership dates, notes and tags), children's details for check-in (age, room, allergies or medical notes the church adds, and the codes printed on their labels), attendance, groups and volunteer rotas, events and who registered, the gifts the church records (who gave, how much, to which fund and how), pledges, prayer requests and other pastoral care notes, weddings (the couple's names and contact details, the day and venue, counselling sessions, the checklist, and guests' names, phone numbers and whether they're coming), certificates, and a record of the messages sent. Wedding fliers, invitation cards and gift cards — and birthday and anniversary cards — are drawn in your browser; a photo you add to one stays on your computer and isn't uploaded to Streamboth. A birthday or anniversary card's link keeps the name(s), the years, the design and the words chosen, so the person can open, save and share their card; anyone with the link can see it. A person's wedding date, if the church adds it, is used for their anniversary card. Group leaders can take their group's attendance and send a prayer request or note about a member from their own private page; these go into the church's records like any other. The church that sets it up decides what goes in and who on its team can see it (each team member has a role; giving and care notes are only seen by the roles that need them), and it is responsible for having the right to keep this information about its members, including permission from parents for children's details.

We keep it on the church's behalf and use it only to run Chronicles for that church — we never sell it, show it to other churches, or use it for advertising. It is stored with Streamboth's database. When the church sends an email from Chronicles, the recipients' email addresses and the message go to Resend, our email provider; WhatsApp and text messages are opened on the sender's own device, so Streamboth doesn't send them. Gifts a church records by hand stay in its records; gifts given online are described below. Everything stays until the church deletes it (a person, a gift, a whole list) or asks us to delete the church; anyone whose details a church keeps can ask that church to correct or delete them, or contact us and we'll pass it on.

A church's public page, member links and check-in. A church can give each member a private link to their own page (streamboth.com/c/…) — no password; anyone holding the link can see and change that member's own details, their family's children, their giving for the year and their serving and event places, so the church can turn a link off or make a new one at any time. The member's phone remembers the link so checking in next time is one tap. A service's QR code lets people check themselves in with their phone number; only their first name is shown back, and children's check-in codes are only shown through a member's private link. The connect card lets a visitor give their name, phone, email, how they heard of the church and a prayer request; these go into that church's records only. Children's check-in labels, their pickup codes, and the people a church says may collect a child (with photos the church adds) are kept for the church's kids team.

Online giving. For now, online payments in Chronicles, Gatherings and Lyceum are by card through Stripe; Paystack (mobile money, and Streamboth collecting) is switched off and described below for when it returns. A church can open a giving page (streamboth.com/give/…) in one of two ways. With its own account, the church connects its own Paystack and/or Stripe account: the gift is paid to the church through that company, and we keep the church's secret key locked (encrypted) only to start payments and check them. With Streamboth collects and pays out, the gift is paid through Streamboth's own Paystack account, and Paystack pays it on to the bank or mobile money account the church gives us (we keep its bank or network, the last four digits of the account and the name on it; Paystack keeps the full number). Either way, the giver's card or mobile money details are entered with Paystack or Stripe and never reach the church or us. We keep, with the church's records: the giver's name, email and phone (as they type them), the amount, the fund, whether it's monthly, how it was paid (mobile money, card or bank), the payment's reference and status, and the gift itself. If the giver isn't in the church's records yet (matched by email or phone), they're added as a person. For a monthly gift by card through Paystack we keep Paystack's reusable reference for the card (encrypted, never the card number) so Chronicles can take each month's gift; with Stripe, Stripe keeps the subscription and tells us each month. The giver's receipt is emailed through Resend and kept at a private link; a church can also email every giver their year's statement through Resend. When Streamboth collects, Streamboth's administrators can see those gifts (the giver's name and email, the amount, fund and reference) and the church's payout account, to check payouts and deal with refunds and disputes; gifts taken through a church's own account are not shown to them. Paystack and Stripe handle the payment under their own privacy policies.

Photos, the members map, automations and the activity log. A church can add photos of its people and of those allowed to collect children; they are stored as small pictures with its records. To put members on its map, Chronicles sends each home address (and the church's city) to OpenStreetMap's address finder, Nominatim, run by the OpenStreetMap Foundation — only the address, not the person's name — and keeps the map position it gives back. A church's automations work only inside its own records (for example adding follow-up tasks for a new visitor, or preparing a birthday message). Chronicles keeps an activity log of who added, changed, removed or checked in what, so a church's admins can see it. A church can require everyone on its team to use two-step sign-in; we only check whether it is turned on in their Streamboth account and never see their codes.

Gatherings (events and tickets)

Gatherings (streamboth.com/gatherings, under Standalone Apps) lets an organiser — a church, school, business or person — make event pages and sell tickets or take free registrations. We keep, for the organiser: its name, city, currency and logo, its team's email addresses and roles, its events (name, dates, venue, description, cover picture, livestream link), ticket types and promo codes; and for each order the buyer's name, email and phone (as they type them), what they chose, the amount, how it was paid, its reference and status, and one ticket per person with its own code and whether and when it was scanned at the door (and by which team member and door). The event page is public; a buyer's tickets are at a private link sent to them. Payments work the same two ways as Chronicles online giving — through the organiser's own Paystack or Stripe account, or collected by Streamboth's Paystack account and paid on to the organiser — and the buyer's card or mobile money details go only to Paystack or Stripe. A door scanner keeps the event's ticket list in that browser so scanning works offline. Tickets and messages to attendees are emailed through Resend. An organiser can send an event's attendees into its own Chronicles church. We keep it until the organiser deletes it or asks us to; we never sell it or use it for advertising.

Lyceum (a school's records)

Lyceum (streamboth.com/lyceum, under Standalone Apps) is where a school keeps its own records: its staff's email addresses and roles; its classes, terms and subjects; its students (name, class, gender, birthday, admission number, photo, and allergies or medical notes the school adds) and their families (the parents' names, phone numbers, email and address); the daily register (here, late or absent, with notes); fees, payments and receipt numbers; class and exam scores, grades, positions and teachers' remarks; and the notices it sends. Each family has its own page (streamboth.com/l/…) showing its children, their attendance, fees and report cards; it opens only for a parent signed in to Streamboth with an email the school has for that family (we check the signed-in email against the family's), and the school can make a new link at any time. When a child is marked absent the school can have their parent emailed, and fee reminders, receipts and notices are emailed through Resend; WhatsApp messages are opened on the staff member's own phone. Fees paid online work the same two ways as Chronicles giving (the school's own Paystack or Stripe, or Streamboth's Paystack paying the school), and the parent's card or mobile money details go only to Paystack or Stripe. We keep the records on the school's behalf and use them only to run Lyceum for that school — never sold, never shown to other schools, never used for advertising; they stay until the school deletes them or asks us to. A parent who wants their family's details corrected or removed can ask the school, or contact us and we'll pass it on.

Who pays for these apps. Chronicles, Gatherings and Lyceum are subscriptions paid by the owner of the church, organiser or school (through Stripe, as for any plan). If it ends, the people on its team are shown the owner's email address, so they can ask them to renew it.

5. How we use information

We use the information above to provide Streamboth, which means:

• signing you in;
• running your studio and broadcasts;
• billing you and applying your plan's limits;
• answering your messages;
• telling you about your account, billing and important changes, in the app and by email;
• sending you occasional news about Streamboth by email, which you can stop any time with the Unsubscribe link at the bottom of each one (you'll still get emails about your account, such as changes to these policies);
• keeping Streamboth secure and working well;
• meeting our legal obligations.

We don't sell your personal information or build advertising profiles ourselves. On the pages of our website (not the studio) we use the Meta Pixel and the Google tag to measure our own advertising — see section 7. Where privacy law requires a legal basis for this, we rely on providing the service you asked for, our legitimate interest in running and protecting it, and our legal obligations.

6. Who we share it with

We share information only with the companies that help us run Streamboth, and only for that purpose:

• Clerk, for sign-in and accounts;
• Stripe, for payments — and, for a church that connects its own Stripe account to Chronicles online giving, its givers' payments;
• Paystack, for Chronicles online giving: a gift given to a church through its own Paystack account or through Streamboth's (with the giver's email, the amount and the payment reference), and, when Streamboth collects, the account the church is paid into;
• Resend, which sends our emails to you, so it receives your email address and the email;
• Railway, which hosts our servers and database in the United States;
• Google, which provides our email, for messages you send us by email — and YouTube, which is Google's, when you connect your channel: we read your live chat from it and send your replies to it;
• AssemblyAI, which runs our AnnanAI listening — only if you choose AnnanAI under Scripture → Settings → Listen with, the studio's Brand → Script → Listen → Listen with, or the studio's Captions → Captions with: while it's listening, your microphone's sound — or, in the studio, the sound that's on air — is sent from your browser to AssemblyAI to be turned into words, under AssemblyAI's privacy policy. We give your browser a short-lived pass for each session; we don't receive or keep the sound. It also transcribes the past sermons you import (see above);
• Meta, when you connect Facebook: we read your Page's live comments from it and send your replies to it — and for the Meta Pixel on our website (see section 7);
• Google, for the Google tag on our website (Google Analytics and Google Ads; see section 7);
• Cloudflare, for the relay that connects studio participants when a direct connection isn't possible, and to store cloud recordings and, until they're transcribed, imported sermons (R2);
• jsDelivr, which delivers the code for virtual backgrounds, video captions, PDF slides, QR codes and the Word files of sermons. All of them run on your computer;
• Anthropic, whose Claude model writes a show's AnnanAI summary when the host asks for one, and Scripture's AnnanAI summary, sermon notes, answers to Ask AnnanAI, book chapters and book introductions when you ask for them, and Live notes while they're on (see above);
• LRCLIB, when you search for a song in Lyrics → Online: our server sends it the words you typed in the search, never who you are;
• Hugging Face, which delivers the speech-recognition model used for video captions. Your browser downloads it the first time you make captions; the video's sound itself is processed on your computer and never sent to anyone.

We may also share information if the law requires it, to protect people's safety or our rights, or as part of a merger or sale of the business, in which case this policy would continue to apply to it.

7. Cookies and browser storage

Streamboth itself needs only cookies from Clerk that keep you signed in, and your browser's storage for your settings, the media you add and a backup of your scenes and songs; the visit counts described in section 2 work without any cookie.

Advertising and analytics. On the pages of our website and your dashboard (/app) — never in the studio, on guests' pages or on the audience page — we use the Meta Pixel (Facebook and Instagram) and the Google tag (Google Analytics and Google Ads). They set their own cookies and send Meta and Google the pages you visit and a few things you do: buying a plan or a website tool (which one and its price), starting a free trial, and sending us a message through Contact Us — never what you type, your stream keys or anything from the studio. We use this to see which of our ads work and to show our ads to people who may want Streamboth; Meta and Google use it under their own privacy policies (Meta, Google). You can choose what ads you see in Meta's ad preferences and Google's My Ad Center, block these cookies in your browser's settings, or turn off Google Analytics with its browser add-on.

8. How long we keep information

We keep a connected YouTube channel's or Facebook Page's access tokens until you disconnect it (Room → Comments → Disconnect) or delete your account; we then delete them and ask Google or Meta to cancel the access. You can also remove Streamboth's access at any time on your Google account's third-party access page, or in Facebook under Settings → Business integrations. We keep your account details, scenes, songs and broadcast records for as long as your account is open. When you ask us to delete your account, we delete them within 30 days. The exception is billing records, which we keep for as long as tax and accounting laws require. Server logs are kept only for a short time.

9. Your choices and rights

You can ask us for a copy of your personal information, ask us to correct or delete it, or ask us to close your account by contacting us at the address below. Depending on where you live, for example in the EU, the UK or California, you may have further rights, such as to object to or restrict how we use your information, or to move it elsewhere. We'll respond within 30 days. If you're unhappy with how we've handled your information, you can also complain to your local data protection authority.

Streamboth's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Deleting your data

To delete what Streamboth keeps about a connected YouTube channel or Facebook Page, open any studio, go to Room → Comments and click Disconnect next to it: we delete it straight away and ask Google or Meta to cancel our access. If you removed Streamboth from your Google or Facebook account instead, we can no longer use what we kept, and it's deleted when you ask us or when your account is deleted. To delete your whole Streamboth account and everything kept with it, write to us at the address in Contact us from the email address on your account, and we'll delete it within 30 days.

10. Security

Everything between your browser and Streamboth is encrypted, and access to our systems is limited to the people who run them. No service can promise perfect security, but we work to protect your information and will tell you if a breach affects you, as the law requires.

11. International transfers

We're based in Ghana. Our servers are in the United States, and our providers may process information in other countries. When information moves across borders, we rely on our providers' legal safeguards, such as standard contractual clauses.

12. Children

Streamboth isn't meant for children under 13, or under the minimum age in their country. If you believe a child has given us personal information, contact us and we'll delete it. Children's details kept by a church in Chronicles for check-in are added by that church, not by the children (see Chronicles).

13. Changes to this policy

We'll post any changes here and update the date at the top. If a change is significant, we'll tell you by email or with a notice in the app before it takes effect.

14. Contact us

Questions or requests about your privacy: email streambothlive@gmail.com, or use our Contact page.
Streamboth, a product of Elannfarm Ventures (Ghana)