Skip to content

Acceptable Use Policy

One set of conduct rules for every surface you can write to, from an inquiry to a support thread, and what happens when one is broken.

Effective July 30, 2026
Contents · 11 sections

Plain-language overview. Seven places on this site take text or files from you, and Section 2 says what belongs in each.

Section 7 is the part that is not about etiquette. Nothing we make may be used to build or deliver a weapon, to surveil somebody who has not agreed to it, to move contraband, or to get in the way of emergency responders. Being a paying client changes none of it.

Section 9 is what happens when something goes wrong, and it starts with the narrowest step that holds. Your data rights are never part of it: access, export and deletion survive anything we do to an account.

Summary only. The numbered sections below are the document.

01

What this policy covers

This Acceptable Use Policy applies to everyone who uses anything SpaltX operates: the account area, the project desk, the support desk, and every form on the site. It applies whether you hold an account or not, and it applies to a person you let use your account.

It is part of the Terms of Service, so breaking it is a breach of your agreement with us.

Claims about material you own go through the Copyright and Trademark Policy rather than through this one.

02

Where you can write, and what each place is for

Every one of these takes text or files from you. Using one for something other than its purpose is the most common way this policy gets broken, and it is usually not malicious.

Surfaces that accept your input
SurfaceWhat belongs there
Project inquiriesThe work you want done. What exists now, what you want instead, and any constraint that has already been decided for you.
The thread on a projectQuestions and answers about that one project. Scoping happens here, so an answer given here is an answer we quote against.
Support ticketsA problem you want fixed, in the category that matches it. Attach what an engineer would need.
Contact formA question for the topic you picked. Law-enforcement data demands have their own topic and must not be filed as sales mail.
Help article feedbackWhether an article answered you, and what it left out when it did not.
Job applicationsYour own history, for a role that is open.
Organization spacesWork shared with people your organization has admitted. Join codes go to those people and nowhere else.
03

Content that is not allowed

Do not submit, upload, store or share any of the following, anywhere on the Platform:

  • Material that infringes copyright, trademark, patent, trade secret or any other right. This covers a model somebody else drew as much as it covers an image.
  • Confidential information you are not free to hand over, including a drawing covered by someone else’s non-disclosure agreement.
  • Personal data about other people beyond what a form asks for. Do not paste a customer list into a support ticket, and do not attach a file full of unrelated names to an inquiry.
  • Threats, harassment, sexual content involving minors, incitement to violence, or material that exists to demean a person or a group.
  • Malware, credential-stuffing lists, or code whose purpose is to compromise a system.
  • Deliberate falsehoods that we act on: a fabricated defect report, an invented organization, or a requirement you know to be wrong when we are quoting against it.
  • Advertising, link spam or bulk unsolicited mail, in an inquiry, a ticket or any other field.
  • Anything a law that applies to you or to us forbids you to hold or to send us.
04

Conduct that is not allowed

  • Pretending to be someone else. Do not open an account in another person’s name, claim a role you do not hold in an organization, or present yourself as connected to SpaltX when you are not.
  • Reaching data that is not yours. Do not try to open another account’s inquiries, proposals, tickets, projects or admin functions, whether by guessing an identifier, replaying a token, or asking support to hand them over.
  • Working around a limit. Rate limits and share-link caps are limits. Opening a second account to get past one is a breach, and so is sharing a login to spread an allowance across people.
  • Abusing staff. Support is answered by people. Abuse in a ticket gets the ticket closed, and a pattern of it gets the account restricted.
  • Using our processes as a weapon. Do not file a copyright notice you know to be groundless, a chargeback for work you accepted, or a stream of privacy requests intended to occupy us rather than to get your data.
05

Platform integrity, automation and load

The Platform is rate limited per person and per address, and the limits are set so that ordinary use never touches them. If you are hitting one, something about how you are using the Platform is unusual.

  • Automated access to public pages at a low volume is tolerated. Automated access that degrades the service for anyone else is not, and neither is bulk collection of help articles, blog posts or share pages.
  • Do not run a client against the account area other than through the site itself.
  • Do not probe, scan or load-test anything we run without written permission first. Section 8 explains how to ask.
  • Do not interfere with a security control: session handling, two-factor enrolment, email verification, row-level security, or the audit log.
07

Uses that are out of bounds regardless

Some uses are prohibited whatever the surface, and no contract with us changes that. Do not use anything SpaltX makes to:

  • Design, build, arm or deliver a weapon, or make a part whose purpose is to injure a person.
  • Follow, film, listen to or otherwise surveil a person who has not agreed to it, or to stalk, intimidate or harass anyone.
  • Carry contraband, deliver anything into a prison or a secure site, or move goods past a border control.
  • Interfere with emergency responders, disaster relief, law enforcement operations or a critical facility.
  • Supply anything of ours, or technical data derived from it, to a sanctioned party or an embargoed destination, or to any end use our export obligations forbid.
This list is not exhaustive

An activity we did not think to name here is still prohibited if it is unlawful where you are, if it endangers someone, or if a reasonable reader of this document would call it abuse. When something is close to the line, ask us before you do it rather than after.

08

Reporting something

What you foundWhere it goes
Abuse of the Platform, or content that breaks this policysupport@spaltx.com, subject line ABUSE. Include the URL, what you saw, and when.
A security vulnerabilitysupport@spaltx.com, subject line SECURITY, before any disclosure. Give us a window to fix it and we will not pursue research done inside that window.
Material you own that someone else postedThe Copyright and Trademark Policy, which has the notice requirements.
A problem with your own project or accountOpen a support ticket rather than an abuse report.

Report in good faith and give us enough to act on. We treat a report as confidential within our team, and we will not pass your identity to the account you reported unless a law obliges us.

09

What we do about a breach

We investigate what we receive, we look at logs where we need to, and we choose a response that fits what happened. These are the responses that exist:

Enforcement steps
StepWhat it does
Rate limitingAutomatic and immediate. It throttles a burst rather than judging it, and it clears on its own once the window passes.
Content removalA message is taken down, an attachment is removed, or a share link is revoked. Removal is specific to the item.
Feature restrictionOne feature is blocked for one account: new project inquiries, or new support tickets. Your existing projects and threads stay readable, and the block takes effect immediately.
Account suspensionSign-in stops. We use this where the breach is serious or ongoing and a narrower step will not hold it.
TerminationThe account and its access end, on the terms in the Terms of Service.
ReferralUnlawful conduct can be reported to the authorities, and we produce records only against valid legal process.
One thing we will not restrict

Data-subject rights are never taken away as a punishment. Access, export and deletion under Account, Privacy keep working on a restricted account and on a suspended one. A legal right is not ours to withhold from someone we are annoyed with.

10

How we decide, and how to challenge it

We aim to match the response to the harm. What we weigh is whether it was deliberate, whether it happened before, whether anyone was put at risk, and whether it can be undone. A first mistake made in good faith usually gets an email.

  • Notice. Where we restrict or suspend an account we write to the address on it, saying what was done and why. We skip the notice beforehand only where telling you first would let the harm continue, and we send it afterwards.
  • Reply to it. Answer the notice, or write to support@spaltx.com with APPEAL in the subject line. Tell us what we got wrong, or what has changed. Somebody other than the person who made the original decision reads it.
  • Timing. We answer an appeal within ten business days. A restriction usually stays in place while we look at it, and we lift it immediately when we find we were wrong.
11

Changes to this policy

We update this policy as the Platform grows new surfaces. The effective date at the top moves when we do, and a change that materially widens what is prohibited is announced to account holders by email before it takes effect.

Ask a question about it at support@spaltx.com. Asking whether something is allowed is always cheaper than finding out.

Acceptable Use Policy | SpaltX