Acceptable Use Policy

Scope

This policy covers:

• The store — publishing, listing, and distributing packs.
• Shared graphs and links — any graph, stream, or link you make accessible to another person.
• Community spaces — Discord, GitHub Discussions, and any other spaces we run or moderate.
• The relay — the sync channel that moves graph events between your devices.

Local-only use of the desktop or web app is not covered here; your licence for that is the EULA.

What is not allowed

### Malware and deceptive code

You may not publish or distribute content that contains malicious code, hidden behaviour, or code that does something materially different from what is described. This includes packs that execute arbitrary code outside their declared plugin interface, packs that harvest data without disclosure, and packs that exploit or attack the user's machine or other services.

### Intellectual property infringement

You may not upload or share content you do not have the right to distribute. This includes packs that reproduce third-party code under an incompatible licence, content that infringes copyright, and the use of another party's trademark in a way that misrepresents origin.

### Illegal content

You may not use Fixnet services to host, share, or distribute content that is illegal in Sweden or under applicable EU law. This includes but is not limited to child sexual abuse material (CSAM), content that incites violence or hatred, and content that violates privacy rights.

### Harassment, hate, and abuse

You may not use Fixnet services to threaten, harass, or demean any person or group, or to distribute content that does so. You may not use community spaces or shared graphs to bully, stalk, or coordinate campaigns against individuals.

### Spam and platform abuse

You may not:

• Submit packs that exist primarily to advertise, redirect, or generate artificial engagement rather than to provide genuine functionality.
• Scrape, flood, or send automated requests to the relay or store API beyond what normal use requires.
• Create multiple accounts or use automated means to circumvent account bans or entitlement limits.
• Publish packs that call third-party services without clearly disclosing that they do so in the pack description and manifest.

Enforcement

When we become aware of a potential violation we follow a graduated process. Every step is logged in our moderation audit trail (`pack_actions`) and affected parties are notified.

### The ladder

1. Warning. For a first or minor violation, we contact the account holder, describe the issue, and give a reasonable deadline to remedy it. No visibility change for borderline cases.

2. Unlist. Content that violates this policy is set to `unlisted`: it disappears from search and browse results. Existing buyers keep their access. A buyer who purchased a pack before it was unlisted retains the right to install and re-download the versions that existed at the time of purchase — bytes are never mutated, only state changes (anchor S8). The only exception is a legal-compulsion takedown or confirmed malware (see below).

3. Takedown. Confirmed serious violations — malware, CSAM, illegal content, or a valid legal order — result in a full takedown: `visibility = 'removed'` and every distributable version moved to `taken_down`. Installed users are notified on next launch. In malware and legal-compulsion cases, existing-buyer access may also be withdrawn to protect users.

4. Account ban. Repeated violations, circumvention of prior sanctions, or a single severe violation may result in permanent account suspension. Banned accounts lose access to network services; local app use and previously purchased content are unaffected to the extent the law allows.

### Appeals

If you believe an action was taken in error, email us at support@fixa.sh with the subject line "Moderation appeal" and your account identifier. We will review the decision and respond within 10 business days. Frivolous or repeated appeals may not receive a response.

### Reporting a violation

Anyone — including people without an account — can report a pack or shared content via the flag icon on the pack detail page, or by emailing support@fixa.sh. Malware and CSAM can be reported directly and will be treated as urgent.

Moderation transparency

All moderation actions are recorded in an append-only audit log (`pack_actions`). Affected users receive a statement of reasons at the time of action. We do not publish individual case details, but we maintain the audit log as the legal record for every decision.

For notice-and-action requests under the EU Digital Services Act, use the dedicated Notice & Takedown page.

See also the Code of Conduct for community-space rules, and the Store Author Agreement for the contractual obligations that apply when you publish a pack.