Privacy Policy

Effective date: 2026-11-09

The additions in section 2.1b take effect on 3 November 2026 (announced on 19 October 2026). Until then, the version of 19 October 2026 applies; it is this text without section 2.1b.

The additions in sections 2.1c, 2.1d and 2.1e, and the rows that refer to them in sections 3 and 6, take effect on 9 November 2026 (announced on 26 October 2026). Until then, the text without those additions applies.

The measurement defaults described in the Google Analytics 4 row of section 6 (outside the EEA, the UK and Switzerland, analytics and advertising measurement on by default, with opt-out under Privacy choices and Global Privacy Control honoured), and the matching statements in sections 5 and 8, take effect on 7 November 2026.

The comparison of signup identifiers in section 2.1, the logging of the account-creation request in section 2.2, the /64 rule for the free de-artifact preview in section 2.2, and the matching row in section 3 take effect on 7 November 2026.

This Privacy Policy describes how Intrect ("we") collects, uses, and protects your personal information when you use ArtifactNet. We comply with the EU General Data Protection Regulation (GDPR), the California Consumer Privacy Act (CCPA / CPRA), and the Korean Personal Information Protection Act (PIPA).

The short version.

1. Data Controller

Intrect, contact: privacy@intrect.io

2. Information We Collect

2.1 Account information

2.1a Product update email (optional)

We send Intrect's own product updates — new releases and features — to accounts that opted in: by ticking the optional checkbox when they signed up, or later with the switch in Settings on the dashboard. The box is unticked by default and is separate from accepting the terms; leaving it unticked does not limit the service. Accounts created before 1 October 2026 were never shown the box, and we do not send them product updates unless they opt in there; the dashboard asks them once, and closing that question without answering records nothing. The switch also turns the updates off again at any time. Every update is marked as advertising, names us as the sender, and carries an unsubscribe link; unsubscribing takes effect at once, and you can also email privacy@intrect.io. Account email that is part of the service — sign-in links, receipts, report notices — is not marketing and is sent regardless of this choice.

2.1b de-artifact trial email (optional)

On the de-artifact download page you can ask for three short emails during the 14-day trial: how to start, how far to push the cleanup, and what changes when the trial ends (the last one includes the purchase link, so these emails are advertising). We collect only the email address you type, the time you asked, and a pseudonymous hash of your IP address used to limit abuse; no account is created. Nothing is sent until you click the confirmation link we email you. Each email is marked as advertising, names us as the sender, and carries a one-click unsubscribe link. An address that is never confirmed is deleted after 7 days; an address that received all three emails or unsubscribed is deleted 30 days later.

2.1c One-time offer after an unfinished plug-in checkout

When someone starts a plug-in checkout and leaves before paying, our payment processor Paddle keeps the unfinished checkout, including the email address typed into it. We read those checkouts from Paddle for the 30 days before an offer is sent, leave out anyone who completed a purchase later, and compare each address (ignoring upper and lower case) with the email addresses of Intrect accounts. We send one email with a single-use discount code only to an account that matches and has opted in to product updates under section 2.1a; it is advertising and follows the same rules. If you linked a plug-in trial to your account (section 2.1d), we may also use whether that trial has ended to decide who receives the offer. An address that matches no account, or an account that has not opted in, receives nothing, and we do not keep it: the comparison happens when the offer is prepared and its result is discarded. An account receives at most one such offer in any 12 months: for each offer sent we keep the account ID, the code, and the time it was sent for 12 months, and check that record before the next one; the code itself expires 7 days after it is sent. Turning product updates off (the switch in Settings, or the unsubscribe link in any update) stops these offers.

2.1d Linking a plug-in trial to your account (optional)

When a de-artifact trial has ended, the plug-in can open our website with a one-time link code; if you then sign in on app.intrect.io and confirm, we link that trial to your account. Nothing is linked unless you press the button. The plug-in sends the code request with the trial record we already keep to give each computer one trial (the computer's one-way machine fingerprint, the plug-in and the trial dates); we store only a one-way hash of the code, which expires after 30 minutes. Once you confirm, we store your account ID and email next to that trial record, the time you linked it, and which version of the confirmation text you saw. A trial can be linked to one account only. We use the link to know that your trial has ended, to help you in support, and, only if you opted in under section 2.1a, for the offer in section 2.1c. The link is kept for 90 days after you linked it, unless you ask us to remove it sooner. If you ask us to delete your account, we delete the link when we process that request. To remove it, email privacy@intrect.io or open a support ticket; removing it does not change your trial or any licence you own.

2.1e Marketing choice in Paddle's checkout (optional)

Paddle's checkout has an optional box for receiving marketing from us, and Paddle can record your choice there before any payment is made, for example in a checkout you did not finish. We read that choice from Paddle and record it on the Intrect account that matches your Paddle customer record, by the Paddle customer ID we hold or by email address. This applies only to choices Paddle reports for checkouts on or after 9 November 2026; choices made in Paddle's checkout before that date are not imported. A yes there counts as opting in to product updates under section 2.1a, including for accounts created before 1 October 2026, but it is recorded only when it is newer than any no you gave us. A later no there withdraws only a yes that came from Paddle, not one you gave us. Neither undoes an unsubscribe. We store what Paddle reported, that it came from Paddle, and when we read it; if no Intrect account matches, we record nothing. The switch in Settings and the unsubscribe link turn off a yes that came from Paddle in the same way as any other.

2.2 Audio submissions

Signed-in Clean Audio: job metadata (time, settings, processing status, duration and filename) remains in your account history until account deletion. Original inputs are removed after processing; remaining input and output audio, including depth previews, are automatically removed after 7 days. Audio expiry does not delete the job record. Older records already removed under the previous 30-day policy cannot be recovered. Anonymous preview retention is unchanged.

2.3 Usage logs

3. How We Use Your Information

PurposeLegal basis (GDPR Art. 6)
Provide the inference ServiceContract performance
Authenticate users and enforce quotasContract performance
Bill paid subscribersContract performance
Improve detection accuracy (non-reconstructable spectral residual and numeric features only — never raw audio, never for generative AI)Legitimate interest
Detect abuse, fraud, or security incidentsLegitimate interest
Apply the free allowance per person rather than per account (§ 2.1, § 2.3)Legitimate interest
Send service notifications and security alertsLegitimate interest
Send a one-time offer after an unfinished plug-in checkout, to accounts that opted in to product updates (§ 2.1c)Consent
Link a plug-in trial to your account when you ask for it (§ 2.1d)Consent
Record on your account the marketing choice you made in Paddle's checkout (§ 2.1e)Consent
Comply with legal obligations (court orders, etc.)Legal obligation

4. What we store (and don't)

We do not keep the original audio you submit. Whether it comes from the demo or the dashboard, the uploaded file is held in our object storage only while it is analysed and is deleted when the analysis finishes. The single exception is a free-demo Report (§ 4.1): sending one attaches the original audio, which that form requires, and we keep it for 30 days.

ArtifactNet is a detection classifier, not a generative model. Nothing you send to us is used to train music-generating AI. We do not build, license, or sell generative audio models.

4.1 Free demo (demo.intrect.io) — zero-retention

Effective 2026-04-22 the free demo operates under a zero-retention policy. What this means in practice:

DataRetentionPurpose
Original audioHeld in object storage only while it is analysed, then deleted.Running the analysis.
Analysis result in server-side cache (spectral scores + feature vectors, no IP, no filename, no URL)1 hour. Automatically discarded after that — nothing is transferred to long-term storage.Lets you press "Report" if you believe the verdict is wrong.
Reported submissions (only when you press Report)30 days on object storage, then deleted automatically; long enough to investigate the reported verdict and improve the detector.False-positive / false-negative investigation, classifier improvement.
Original audio attached to a Report (every demo Report includes it)30 days, same as above.Only used to reproduce and debug the reported analysis.
Shared result page (only when you press Share)Until you revoke it. Stores the verdict, its probability, the segment scores, the analysed length, and the model version — plus any track name you type in yourself. Not the audio, not your uploaded filename, not your IP.Publishes that one result at a link you can send to other people.
Client IPTransient (rate-limiter cache, minutes), then discarded. Not included in reports.Rate limiting, abuse prevention.

If you close the browser without pressing Report or Share within 1 hour, every server-side trace of your demo submission is gone.

A shared page is unlisted by default: search engines are told not to index it, and only someone who has the link can open it. You can opt a page into search indexing when you create it. When you create the link we also hand you a management token — keep it, because without an account that token is the only way to take the page down again.

4.2 Paid tiers (Creator / Pro / Enterprise)

Paid subscribers are processed under stricter retention:

DataRetention
Uploaded audioHeld in object storage while the job runs; deleted when it finishes.
Spectral residualDeleted within 24 hours after analysis.
Forensic features (segment scores, internal feature vectors)30 days after the analysis, then deleted, unless your account has agreed a different period with us — not retained for model improvement.
Analysis results (verdict, probability, model version)Kept in your account's history until you delete your account.
Submission metadata (filename, URL, format, duration)Kept with your job history until you delete your account.
Account record, including its signup acquisition snapshotUntil you delete your account.

4.3 Usage / security logs (all tiers)

DataRetention
Usage logs (quota, billing)12 months
Per-account activity dates (account ID + KST date only)365 days or until you delete the account, whichever comes first.
Security and audit logs12 months
Signed-in API request log (timestamp, endpoint, response code, account ID, IP address, browser identifier)30 days, then deleted. Free-demo requests are not written to it at all.

5. We Do NOT

5a. Requesting deletion of your submissions

You may email privacy@intrect.io at any time with a request to delete specific submissions (identify by filename, timestamp, or approximate time of use). We will remove them from active storage and any offline improvement set within 30 days. GDPR / CCPA / PIPA deletion requests are handled under the same process.

6. Third-Party Processors

ProviderPurposeRegion
Google (OAuth)AuthenticationUSA / global
Google Analytics 4Usage measurement on the website, dashboard and demo pages: page and event data, linked across intrect.io, app.intrect.io, demo.intrect.io and try.intrect.io. In the EEA, the UK and Switzerland analytics, Google advertising measurement and Meta advertising measurement are separate opt-in choices, off until allowed. Elsewhere all three are on by default and each can be turned off at any time under Privacy choices; a Global Privacy Control signal keeps advertising measurement off. Google ad personalisation follows Google advertising measurement outside those three areas and stays denied inside them.USA / global
Google Ads / Data ManagerWith Google advertising measurement consent: advertising click identifiers and verified purchase product, value, currency and event time. No email or email hash is sent through this connection.USA / global
Meta Pixel / Conversions APIWith Meta advertising measurement consent: permitted website actions and verified first paid purchases, browser/click identifiers, IP address, browser user agent, a pseudonymous consent identifier and normalized, hashed checkout email. Hashing does not make an email anonymous. Automatic advanced matching is disabled.USA / global
GitHub (OAuth)AuthenticationUSA / global
Paddle.com Market LimitedPayment processing as our Merchant of Record. Paddle collects your billing details directly; we receive order metadata by webhook (order ID, billing email, country, Paddle customer ID), and query Paddle's API for your billing email when a webhook omits it. We also read from Paddle the email typed into a plug-in checkout that was not completed, for the offer in § 2.1c, and whether you ticked the marketing box in Paddle's checkout, for § 2.1e. Your card number never reaches us.USA / EU / global
Neon (managed PostgreSQL)Hosts the application database: your account record, usage history, and credit ledger.USA (us-east-1)
Upstash (managed Redis)Short-lived operational data such as rate-limit counters and the one-hour demo result cache.Provider-managed
Cloudflare (R2, Workers, Pages, DNS, Web Analytics)Object storage for reported demo submissions and paid-tier forensic artefacts under the retention rules in § 4; edge delivery, DNS, and bot protection for every request to this service; and cookieless page-view and performance measurement.USA / global edge
ResendOutbound email: address verification, report notifications and operational alerts, and Intrect's own product updates and offers to accounts that opted in (§ 2.1a, § 2.1c). Resend sends on our behalf and does not use the addresses for its own purposes.USA / global

7. International Transfers

Your data may be processed in the United States, the European Union, and the Republic of Korea. Audio you submit for analysis is processed on hardware we operate in South Korea; it is not sent to a third-party inference provider. We rely on Standard Contractual Clauses (SCC) for transfers outside the EU/EEA where applicable.

8. Your Rights

GDPR (EU/EEA users)

CCPA / CPRA (California users)

PIPA (Korean users)

To exercise any rights, email privacy@intrect.io with the subject "Data Subject Request". We respond within 30 days. You can also delete your account yourself in Settings → Account in the dashboard.

9. Security

Despite our safeguards, no system is 100% secure. If you discover a vulnerability, please report it to security@intrect.io.

10. Children

The Service is not directed to children under 16. We do not knowingly collect personal information from children. If you believe we have collected data from a child, contact us and we will delete it promptly.

11. Changes

We may update this Policy. Material changes will be announced via email and on the dashboard at least 14 days in advance.