Legal
Privacy Policy
The short version. We hold an email address, a password hash, your plan, and basic technical logs. Your camera and microphone content is processed on your own device and is never sent to us. Payments are handled by Creem. You can ask us for a copy of your data or ask us to delete it at any time by writing to support@mintcast.io.
Contents
- Who we are
- What this policy covers
- What we collect
- Camera, microphone and face data
- Casting and your local network
- Payments
- Cookies on this website
- Why we are allowed to process it
- Who else sees it
- Where it is stored
- How long we keep it
- Your rights
- Deleting your account
- Security
- Children
- Changes to this policy
- Contact and complaints
1. Who we are
Mintcast is a live streaming application for phones and Windows computers. It is operated by Mintcast Studio Limited, located in Hong Kong SAR, China. In this policy, "we", "us" and "our" mean Mintcast Studio Limited, and "you" means the person using the website or the apps.
For anything in this policy, including requests about your own data, the contact address is support@mintcast.io.
2. What this policy covers
This policy applies to the website at mintcast.io, the Mintcast mobile apps for Android and iOS, the Mintcast desktop app for Windows, and any support conversation you have with us. It does not apply to the streaming platforms you send your video to — TikTok, YouTube, Twitch and the others listed on our home page each have their own privacy policy, and their handling of your stream is outside our control.
3. What we collect
3.1 Information you give us
- Account details. An email address and a password. Passwords are stored only as a salted hash; we cannot read them. A display name and an avatar are optional, and the app works without them.
- Support messages. Whatever you write to us, including any screenshots or log files you choose to attach.
- Order details. The plan you bought, the amount, the currency, the date, and the order identifier issued by Creem. We do not receive your card number.
3.2 Information created when you use the app
- Device and app data. Device model, operating system version, app version, language, time zone, and a randomly generated installation identifier.
- Technical logs. IP address, connection timestamps, crash reports, and error codes. These are used to keep the service running and to diagnose faults.
- Usage counters. Which features are opened, how often a stream is started, and which plan limits are reached. These are aggregated counts, not a record of what you streamed.
- Licence state. Which plan is active on which device, so that the paid features can be unlocked offline.
3.3 What we do not collect
We do not collect your camera feed, your microphone audio, the content of your streams, your contact list, your photo library, your precise location, or your advertising identifier. We do not buy data about you from brokers, and we do not sell or rent personal data to anyone.
4. Camera, microphone and face data
The app needs access to your camera and microphone to do its job. Both are used only while you are actively casting or streaming, and both are processed on your device.
- The background replacement model runs locally on the phone. Frames are analysed to separate a person from the background and are then discarded. They are not transmitted to us or to any third party.
- We do not create, store or transmit a face template, a faceprint, or any biometric identifier. The model does not attempt to recognise who you are.
- Video and audio leave your device only in the direction you choose: to your own PC on your local network, or to a streaming destination whose address you entered.
- If you save a recording to your phone's storage, that file is under your control and is not visible to us.
- Permissions can be revoked at any time in your phone's settings. Revoking the camera permission stops casting but does not delete your account.
5. Casting and your local network
When you cast from the phone to the desktop app, the two devices find each other on your own Wi-Fi network or over a USB cable, and the video travels directly between them. It is not relayed through our servers. The app asks for local network permission on iOS for this reason. Pairing uses a short code shown by the desktop app so that a device on the same network cannot join without your confirmation.
6. Payments
Paid plans are sold through Creem, which acts as the merchant of record. Creem processes the payment, calculates and remits applicable sales tax or VAT, issues the invoice, and appears as the seller on your card statement. Creem collects your name, billing address, card details and tax identifier directly; those details never reach our servers.
We receive a limited confirmation: the plan purchased, the amount, the currency, the order identifier, your email address, and your billing country. We use it to activate the licence, answer billing questions, and meet our accounting obligations. Creem's own privacy notice applies to the information it collects.
7. Cookies on this website
This website is a set of static pages. It does not set advertising cookies and does not contain third-party tracking pixels.
- Strictly necessary. A security cookie may be set by our hosting provider to distinguish real visitors from automated traffic. It contains no personal data beyond a temporary token and expires within 24 hours.
- Analytics. We count page views in aggregate, without cookies and without building a profile of individual visitors. If we ever add a cookie-based analytics tool, this section will name it and offer an opt-out before it is switched on.
You can block or delete cookies in your browser settings. Because the necessary cookie is only used for abuse prevention, blocking it does not stop you reading any page on this site.
8. Why we are allowed to process it
Where the GDPR or UK data protection law applies, we rely on these legal bases:
| Performance of a contract | Creating your account, activating a paid plan, providing support, and delivering the app you asked for. |
|---|---|
| Legitimate interests | Keeping the service secure, preventing abuse and fraud, diagnosing crashes, and improving features using aggregated counts. We balance these against your rights and keep the data minimal. |
| Legal obligation | Retaining invoices and transaction records for tax and accounting purposes, and responding to lawful requests. |
| Consent | Any optional communication, such as product news. You can withdraw consent at any time and it does not affect anything you have already received. |
9. Who else sees it
We do not sell personal data. We share it only with the service providers that make the product work, and only as much as each one needs:
- Creem — payment processing, tax, invoicing, subscription management.
- Cloud hosting and database providers — storing account records and licence state.
- Email delivery providers — sending sign-in codes, receipts and replies to support mail.
- Crash and error reporting — receiving anonymised stack traces and device model, without account identifiers where technically possible.
We may also disclose data if we are legally required to, if it is necessary to investigate fraud or abuse, or if the business is sold or reorganised — in which case the receiving entity is bound by this policy and we will tell you before your data moves. We never disclose your camera feed, because we never have it.
10. Where it is stored
Account records are held on servers in the European Union and in the Asia-Pacific region, and support mail may be processed in either. Where personal data leaves the EEA or the UK, we rely on the European Commission's Standard Contractual Clauses together with the additional safeguards required by local law. A copy of the clauses we use can be requested at support@mintcast.io.
11. How long we keep it
| Account and profile | While the account is open, then 30 days after a deletion request, then permanently deleted. |
|---|---|
| Licence and subscription state | While the plan is active, plus 12 months for reactivation and dispute handling. |
| Invoices and transaction records | As long as tax and accounting law requires, typically 7 years. Held separately from the account and not used for marketing. |
| Support conversations | 24 months from the last message, then deleted. |
| Crash and error reports | 90 days, then deleted. |
| Aggregated usage counts | Retained in a form that cannot be linked back to a person. |
| Server access logs | 30 days. |
12. Your rights
Depending on where you live, you may have the right to:
- ask for a copy of the personal data we hold about you;
- correct data that is wrong or incomplete;
- ask us to delete your data (see section 13);
- receive your data in a portable, machine-readable format;
- object to processing based on our legitimate interests, or ask us to restrict it;
- withdraw consent where consent is the basis;
- not be discriminated against for exercising these rights — we do not offer different prices or service levels to people who make requests.
Write to support@mintcast.io and describe what you need. We may ask one question to confirm you control the account, usually by replying from the registered address. We answer within 30 days, and within 45 days for requests covered by the CCPA. There is no charge unless a request is clearly unfounded or repetitive.
If you are in the EEA or the UK you also have the right to complain to your national data protection authority. We would rather you came to us first, but the choice is yours.
13. Deleting your account
Email support@mintcast.io from the address on the account, with the subject "delete my account". We confirm receipt within one business day and put the account into an inactive state for 30 days, during which you can ask us to restore it. After those 30 days the account and its data are deleted from the live systems, and the deletion propagates to backups within a further 30 days.
Two things survive deletion because they are not ours to erase: the invoice records that tax law obliges us to keep, and copies that a streaming platform or app store holds under its own policy.
14. Security
Traffic between the apps and our servers uses TLS. Access to production data is limited to the engineers who need it, is logged, and requires multi-factor authentication. Passwords are hashed, not encrypted. Licences are signed so that a modified client cannot issue itself a paid plan.
No system is perfect. If a breach affects your personal data, we will notify you and the relevant authority without undue delay, and within 72 hours of becoming aware where the GDPR requires it, describing what was affected and what we have done about it.
15. Children
Mintcast is not intended for children. You must be at least 16 years old in the EEA and the UK, at least 14 in South Korea, and at least 13 elsewhere, and old enough to enter into a paid agreement in your country. If we learn that an account belongs to a child below the applicable age, we will close it and delete the data. A parent or guardian who believes their child has created an account can write to us and we will act on it.
16. Changes to this policy
We update this policy when the product or the law changes. The effective date at the top of the page always reflects the current version, and the previous version stays available on request. If a change materially affects your rights, we will email account holders at least 30 days before it takes effect.
17. Contact and complaints
Questions about this policy, requests about your data, or a complaint about how we handled it:
Mintcast Studio Limited
Hong Kong SAR, China
support@mintcast.io
We reply to every message. If you are not satisfied with our answer, you may escalate to the data protection authority in your country of residence.