Privacy Policy

Effective date: 10 November 2026

This Privacy Policy (the Policy) explains how SWEET BIZ PTE. LTD. (Sweet Biz, we, us or our) collects, uses, shares and keeps personal data for the Sweet Audio website, communications, purchases, support and audio plugins (the Services).

1. Who we are

1.1 Sweet Biz is the controller when we decide why and how to handle personal data under this Policy. Our registered details are below.

SWEET BIZ PTE. LTD.
UEN 202404288G
1 North Bridge Road
#B1-35 High Street Centre
Singapore 179094

1.2 Our Data Protection Officer under Singapore’s Personal Data Protection Act 2012 (PDPA) is also our privacy contact. You can email them at dpo@sweet-biz.com.

2. Scope and the role of Moonbase

2.1 This Policy applies when you visit sweet-audio.net, ask to hear from us, buy or use Sweet Audio products, use their licensing or update-check features, or contact Sweet Biz.

2.2 Moonbase handles checkout, delivery, licensing and update checks for Sweet Audio. Sweet Biz is the controller for customer accounts, licences, activations, trials, downloads, update checks and communications. Moonbase handles that data for us as our processor. This Policy also covers how we use purchase information we get from Moonbase.

2.3 The Moonbase business named as the seller at checkout is a separate controller for purchase, payment, tax and consumer-law records. Moonbase also acts as a separate controller when it does limited work with data to protect its own security, prevent fraud or calculate its fees. Moonbase explains how it handles data in these roles in its Privacy Policy for Buyers.

3. Personal data we collect and where it comes from

3.1 We collect personal data directly from you, automatically from your device, and from third parties. The kinds of data we use depend on which Services you use and how you deal with us. They may include the kinds listed in clauses 3.2 to 3.6.

3.2 Identity and contact data: your name, postal or billing address, email address, and any account or customer identifiers we receive. This data can come from you, Moonbase, or an organisation that buys or manages a licence for you.

3.3 Transaction and licence data: records we receive about products, orders, refunds, downloads, rights to use products, licences, trials, activations, licence checks and expiry. These can come from you, Moonbase, the plugin or a business customer.

3.4 Device and request data: IP addresses, browser or operating-system information, device names, persistent device or licence identifiers, activation tokens, and request or security logs. This data can come from your browser, device, plugin, network connection, hosting provider or Moonbase.

3.5 Communications and support data: messages, requests and anything you choose to send for support. These can come from you or someone authorised to act for you.

3.6 Communication preference and delivery data: email addresses, the alerts you ask for, and records of your consent or confirmation. We also record whether you unsubscribed or objected, whether further messages are blocked, and whether an email was delivered or bounced. This data can come from you, Moonbase or communications providers.

3.7 If a product uses Moonbase licensing, the plugin may get or create a device identifier and device name and contact Moonbase. This can happen when you’re loading or running the product, or when you ask for a trial, activation or licence check. The request can include device and licence identifiers, product and licence details, and ordinary connection details such as an IP address.

3.8 The plugin may keep licensing information and a diagnostic log on your device. It does not send that log to Sweet Biz automatically.

3.9 Update checks without activation. Plugins that do not require licence activation may still connect automatically to Moonbase’s public product-information service to check for updates. These checks work without a Moonbase account. The request identifies Sweet Audio and the product. Moonbase and its hosting providers receive your IP address and ordinary connection details, such as the time and requested address. The check sends no account details, licence tokens, device name, persistent device identifier, audio, presets or project content. The plugin compares versions on your device and does not send its installed version to Moonbase.

3.10 For these update checks, the plugin may keep the latest version returned by Moonbase and the next permitted check time on your device to limit how often it contacts Moonbase. Failed checks may be retried later. These checks notify you of an available update; they do not download or install it or prevent you from using the plugin offline. You can also get updates from the product page on our website.

4. How and why we use personal data

4.1 Clauses 4.2 to 4.8 explain why we use personal data. They also give the legal basis for each use if the EU GDPR or UK GDPR applies.

4.2 Website, supply, updates and support. We use data to run the website, answer requests, and provide the product, licence, delivery, updates and support you ask for. Our legal basis is carrying out a contract or taking steps you ask us to take before entering into one. If no contract applies, we rely on our legitimate interests in providing the Services and answering you.

4.3 Reseller and licence administration. We use data to send you to Moonbase and manage the business and licensing relationship. We rely on our legitimate interests in distributing and licensing Sweet Audio products through an authorised reseller. If we need the data to carry out the Sweet Biz licence, carrying out that licence is our legal basis.

4.4 Operation and security. We use data to run, maintain and protect the Services, find faults, and prevent fraud, abuse and unauthorised licence use. We rely on our legitimate interests in keeping the Services reliable and secure and protecting users and our rights.

4.5 Operational notices. We send notices about how the Services operate, licences and product security when the Services need them or the law requires them. Depending on the use, we rely on carrying out a contract, meeting a legal duty that applies to us, or otherwise our legitimate interests in keeping the Services secure and protecting users.

4.6 Records and legal requirements. We use data to keep records, answer lawful requests and provide remedies the law requires. We rely on meeting EU or UK legal duties that apply to us. Otherwise, we rely on our legitimate interests in keeping records and establishing or defending legal claims.

4.7 Requested launch alerts. We use your data to send launch alerts you ask for. We rely on your consent.

4.8 Communication choices and evidence. We use data to record and honour your communication choices, stop sending you marketing when you withdraw consent, and show we have followed the rules. We rely on meeting legal duties that apply to us. Otherwise, we rely on our legitimate interests in respecting your choices and in showing or defending our compliance.

4.9 Under Singapore’s PDPA, we collect, use and share personal data with consent, when the law treats you as having consented (deemed consent), or as the law otherwise allows. We may use the legitimate-interests exception only if we meet its conditions. Any use under that exception to enforce device limits, prevent repeat trials, protect security or prevent fraud or misuse must be proportionate.

5. Data you must provide

5.1 The law does not require you to give us personal data unless we tell you it does. We need to collect personal information to provide certain services. If you do not provide the information we identify as required or mandatory, we may not be able to provide those services. For an order, a licence or an activation you ask for, you must give us the information needed to set it up or carry it out.

5.2 You can choose whether to get marketing, load embedded YouTube videos or send optional material for support.

6. Cookies and similar technologies

6.1 We use necessary cookies from our own site to remember and record your privacy choice. We run Matomo on our own server in the EU and use it for website analytics only with your consent. It counts page views and some actions you take on the site, and connects visits from campaign links to paid orders.

6.2 Analytics data includes a random visitor reference, masked IP information, browser details, page paths, selected events and campaign labels. We use pseudonymous data, which means we use references in place of direct identifiers. The records may still be linked to someone. We don’t send names, email addresses, payment details, licence tokens or receipt URLs to Matomo.

6.3 Analytics stays off until you accept it. You can still use checkout if you decline. You can change or withdraw your choice in Privacy settings. We record what you chose, when you chose it, and the language and version of the wording. This lets us respect your choice and show which choice you made.

6.4 Here’s how long we keep our Matomo analytics and consent records.

• Links between campaigns and orders, and raw analytics records, expire after 30 days.
• Summary reports expire after 24 months.
• We keep the minimum evidence of consent while your choice applies and for 12 months after it expires or you withdraw it.
• Protected backups expire within seven days. We remove expired records from restored backups before the restored systems start processing again.

6.5 We match verified payment notifications to checkout records that we linked to analytics with your consent. If there’s no match, we may keep the payment time and an order reference protected by a key for up to one hour. This gives the records time to arrive and match. The analytics service doesn’t keep customer details or full payment notifications. We don’t send unmatched sales to Matomo.

6.6 Our legal basis for the limited payment matching in clause 6.5 is our legitimate interest in managing orders. We measure visits and link orders to campaigns only if you consent.

6.7 If you use a Moonbase feature, the site may open a page hosted by Moonbase or load code for its storefront. This includes actions such as viewing product information, using your account, buying a product, managing a licence or downloading a product. Moonbase and its providers may then write or read cookies or browser storage. Our Cookie and Local Storage Notice explains the controls that apply.

6.8 If you accept analytics, we let the storefront on our site use ad click identifiers from campaign links to see which ads lead to purchases. You can withdraw that consent in Privacy settings. Moonbase’s Privacy Policy for Buyers explains how it uses and keeps information in purchase records about how buyers reached the storefront.

YouTube videos

6.9 YouTube videos are optional and stay blocked until you allow them. Use Allow YouTube content in the popup or our privacy controls; Accept all also allows YouTube. Once we verify permission, allowing YouTube in a popup or opening one with saved permission loads the player and requests playback automatically.

6.10 In the EEA, YouTube is provided by Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. We choose the videos and when to connect; Google decides how its service uses data for its own purposes. The Google Privacy Policy explains its data use, retention and controls. The YouTube Terms of Service also apply.

6.11 We use the privacy-enhanced player at youtube-nocookie.com. It limits personalization but still sends personal data to Google: your IP address, browser and device details, our site origin, the video and playback activity. Google may use cookies, local storage or similar technologies for playback, security, non-personalized ads and measurement.

6.12 Where the GDPR applies, we rely on your consent under Article 6(1)(a). Where German law applies, consent also covers non-essential device storage or access under section 25(1) TDDDG. YouTube permission is separate from analytics.

6.13 We remember your YouTube choice for 182 days. Changing analytics alone does not renew it. Change or withdraw permission in Privacy Settings in the popup or footer. Withdrawal removes the player and blocks further loading; closing the popup stops playback but keeps your choice. Withdrawal does not undo earlier lawful processing or delete data Google already holds. Use Google’s privacy controls and your browser settings to manage that data and Google’s browser storage.

6.14 We keep a protected record of your choice, its time, purpose, language and wording version while it applies and for 12 months after expiry or withdrawal. Allowing YouTube alone does not enable analytics. Our consent records do not include your viewing history.

6.15 Google may process data outside the EEA, including in the US. It states that it uses the EU-US Data Privacy Framework and its UK Extension for covered transfers, and standard contractual clauses where required. See Google’s transfer safeguards and section 8. Permission to play a video does not replace those safeguards.

7. When we disclose personal data

7.1 We may share personal data with the following recipients when reasonably necessary.

• Moonbase, to handle customer accounts, sales, communications, delivery, licensing or update checks relevant to the product or interaction.
• Google, when an embedded YouTube player loads with your permission, as explained in clauses 6.9 to 6.15.
• An organisation that buys or manages a licence for you.
• Providers that host, protect or support our website, communications, licensing, update checks or business systems, or monitor their security or availability.
• Professional advisers, when we need advice or need to establish, exercise or defend legal claims.
• Authorities or courts, if the law requires or allows us to share the data.

8. International transfers

8.1 Moonbase may handle data outside your country. For Moonbase’s description of where and how it handles data, see its Privacy Policy for Buyers.

8.2 If Sweet Biz transfers data from the European Economic Area or United Kingdom to a country that isn’t recognised as providing adequate protection, we do so only if we have approved contract terms or another lawful way to make the transfer. We also put any required extra safeguards in place before transferring the data.

8.3 When Singapore’s PDPA applies to an overseas transfer, we take steps to make sure the data gets protection comparable to what Singapore law requires.

8.4 You can ask our privacy contact what safeguards Sweet Biz uses for a transfer and how to get a copy. We may redact parts of the copy where appropriate.

9. Retention

9.1 The retention duration depends on the purpose of data collection and any legal obligations. We keep personal data only as long as we need it for its original purpose or for another purpose the law allows. When we decide how long to keep it, we consider business needs and legal requirements, how long an account or licence lasts, how sensitive the data is, security needs, records we must keep by law, consumer remedies and any legal deadlines for bringing a claim.

9.2 Purchase and licensing records. We may keep basic records of purchases and rights to use a product if we need them to recognise and support an ongoing licence. We keep the online activation record while the activation takes up a licence slot. We may keep the minimum records of product-use rights and offline tokens while the licence or a token we’ve issued can still be used.

9.3 Licensing and update-check requests and errors. We keep detailed records only until we finish the related operations and security review. We may keep the relevant part longer if we need it for a specific support issue, security issue, dispute or claim.

9.4 Statutory transaction records. We keep these records for as long as the applicable law requires.

9.5 Support. We delete routine support conversations and attachments once the case is closed and 365 days have passed since the last reply from you or our support team. We may keep evidence for as long as we need it for a specific complaint, dispute, claim or duty to keep records by law.

9.6 Launch alerts. We keep subscription data while you’re subscribed. If you unsubscribe or the programme ends, we delete the active subscription data. To honour your choice and show that we followed the rules, we keep only the necessary records of consent and records that block further marketing. We apply the relevant legal deadlines for bringing a claim. We may keep short-term records of deliveries and failures until we finish the relevant delivery cycle and follow-up.

9.7 Trial eligibility. We may keep a record of whether a device qualifies for a trial while the product’s one-trial-per-device rule applies. We delete the record when that trial programme ends permanently unless we need relevant evidence for a documented dispute or claim.

9.8 Website logs. We delete routine Sweet Audio website request and security logs from our active logging systems within seven days. We may keep the relevant part if we need it for a specific incident, dispute or claim.

9.9 We delete or anonymise data once it no longer serves its original purpose and we no longer need it for legal or business reasons. Protected copies may remain in backups after we remove data from active systems. We restrict access to those copies and keep them out of day-to-day use until the set backup schedule overwrites or deletes them. If we restore a backup, we apply earlier deletion decisions again before the affected data can return to day-to-day use.

9.10 Moonbase follows its own rules for keeping data it controls for its separate purposes.

10. Automated licence checks

10.1 For plugins that use Moonbase licensing, we use your product and licence details and a device identifier to check whether your licence covers the plugin and whether you can activate it on that device. You can have up to three active devices per licence, including offline activations. If we offer a trial, Moonbase checks whether the device has already had a trial for that product. When you open the plugin, it checks whether your trial has expired.

10.2 If you activate online, the plugin contacts Moonbase from time to time to check that the activation is still valid. To activate offline, you use a device with internet access to send Moonbase a file with the product details and the identifier of the device you’re activating. Moonbase gives you a licence file that the plugin can check on your computer without going online.

10.3 If you already have three active devices, you’ll need to free up a spot before you can activate another. If your trial ends or you no longer have a valid activation, features that need activation may stop working.

10.4 If a check blocks or limits activation or use under your licence, you can ask for a human review at support@sweet-audio.net. You can explain your side and challenge the result. A person authorised to change the result will review the relevant records and any information you give us. We’ll tell you the outcome, fix any error and restore access if the licence allows it.

11. Your privacy rights

11.1 Your rights depend on where you are and which law applies. If the law’s conditions and exceptions allow it, you may be able to do the following.

• Access your personal data or get a copy.
• Correct wrong or incomplete data.
• Ask us to delete data or limit how we use it in certain circumstances.
• Get certain data in a format you can take elsewhere.
• Ask us to stop direct marketing.
• Object to how we use data based on legitimate interests.
• Ask us to explain a safeguard that applies to an international transfer.

11.2 When we use your personal information based on your consent, you have the right to withdraw that consent at any time. To stop getting marketing emails, follow the opt-out or unsubscribe instructions in the email or contact us. To withdraw consent for other uses of your data, get in touch with our privacy contact. Withdrawing consent does not affect anything we did lawfully with your data before you withdrew it.

11.3 To use one of your rights, email dpo@sweet-biz.com. To verify your identity for security, we may request extra information before addressing your data-related request. We’ll ask only for what we reasonably need to check who you are and whether you’re authorised to make the request.

Singapore

11.4 You can ask to see personal data about you that we hold or control, or ask us to correct it. You can also ask how we used or shared it, or how we may have used or shared it, in the year before your request.

11.5 You can withdraw consent by giving reasonable notice. We’ll explain what’s likely to happen if you withdraw it. Sweet Biz and its data intermediaries and agents will stop collecting, using or sharing the affected data unless the PDPA or other written law requires or allows us to continue without consent.

11.6 If your concern isn’t resolved, you can take it to the Personal Data Protection Commission.

European Economic Area and United Kingdom

11.7 EEA. You can complain to a data protection authority, particularly where you usually live or work or where you think a breach occurred.

11.8 United Kingdom. If UK data protection law applies, you can email us a data protection complaint at the address in Section 13. You can also complain to the UK Information Commission.

11.9 Right to object. You can object to how we use your data based on legitimate interests for reasons related to your situation. You can object to direct marketing at any time. If you do, we’ll stop using your personal data for direct marketing.

California

11.10 Section 3 lists the types of data we collect. Section 7 lists the types of recipients we share it with. Section 11 explains how to review your personal data or ask us to correct it. Section 12 explains how we change this Policy.

11.11 Sweet Biz does not collect information about your online activity over time and across third-party websites or online services if that information can identify you. That’s why browser “Do Not Track” signals don’t change how our pages work.

11.12 When you simply view a Sweet Audio page, no third party collects information that can identify you and show your activity over time and across third-party websites or online services. If you load a Moonbase feature on a Sweet Audio page, Moonbase or its providers may collect that kind of information as explained in Moonbase’s Privacy Policy for Buyers.

12. Changes to this Policy

12.1 We may update this Policy when our Services, providers or legal duties change. We’ll post the updated Policy on this page with a new effective date.

12.2 We’ll give you an additional form of notice about a significant change if the law requires it. If we need to give new notice or get new consent, we’ll do so before we start handling the data in the affected way.

13. Contact

13.1 For privacy questions, complaints or requests, email dpo@sweet-biz.com or write to the company address in Section 1.

13.2 For data that Moonbase handles as a separate controller, use the contact details in the Moonbase Privacy Policy for Buyers.