Skip to content
RSX

RSX-CNT-01

Content
policy.

What may and may not be stored on RSX, how content is reviewed, how anyone can report it, what we do about it, and how a decision is challenged.

Effective
6 September 2026
Version
1.0
Applies to
Anyone storing or sharing content on an RSX service

01What this policy covers

1.1
This Content Policy governs everything you upload to, store on, or make available through an RSX service, and everything a link you create points at. It applies in full to the RSX CDN, and to any other Service that accepts content from you.
1.2
It forms part of the Terms of Service and is incorporated into it. Everything prohibited by section 5 of those terms is also prohibited here; where this document is more specific about content, this document controls.
1.3
Content means any file, its filename, the metadata you attach to it, and any preview generated from it. It does not matter whether content is public, unlisted, or private: this policy applies to all three, because storing something on our systems is what engages our obligations, not who can see it.
1.4
RSX is a hosting service established in the European Union. We store content at your request and we do not select or modify it. Our obligations, and the limits on them, come from that role: we are not liable for content we do not know about, we are not obliged to monitor what you upload, and we must act once we do know.
1.5
Terms used here have the meanings given in the Terms of Service.

02Your content is yours

2.1
You keep ownership of what you upload. You are responsible for it, for having the rights to it, and for the consequences of publishing it. We do not acquire it and we do not want it.
2.2
Before you upload, you must hold every right needed to store the content on our systems and to make it available at the visibility you choose. If you did not make it, you need permission from whoever did.
2.3
Visibility is your decision and your responsibility. Public and unlisted content is delivered to anyone holding the link, cached at the edge, and may be copied, embedded, or archived by third parties beyond our reach. Setting content to private later does not retrieve what has already been taken.
2.4
Do not upload content containing other people’s personal data unless you have a lawful basis for doing so. If you publish such content, you are the controller of it, not us, and a request from the person concerned is yours to answer.
2.5
Storage is not backup. Keep your own copy of anything you cannot afford to lose. Content can be removed under this policy, lost to a fault, or ended with the account that holds it, and we give no undertaking that it will still be there.

03Content that is never permitted

3.1
The following must not be uploaded, stored, linked to, or made available through any RSX service, at any visibility setting. This list is not exhaustive: content may be removed for being unlawful even where it is not described below.
3.2
Child sexual abuse material and the sexualisation of minors. This includes real, drawn, generated, and edited depictions, and content that sexualises a person who is or appears to be under 18. There is no exception, no context in which it is permitted, and no route by which an account removed for it is reinstated. See sections 5.3 and 12.
3.3
Intimate images published without consent, including images obtained by deception or intrusion, images generated or edited to depict a real person sexually, and threats to publish either.
3.4
Terrorist and violent extremist content: material that incites, glorifies, solicits support for, or provides instruction to further terrorism or violent extremism.
3.5
Incitement and targeted hate. Content inciting violence, hatred, or discrimination against a person or group on the basis of a protected characteristic, and content that harasses, threatens, or is intended to intimidate a specific person.
3.6
Doxxing. Another person’s private information published in order to expose, harass, or endanger them: home address, identity documents, private contact details, workplace, or the aggregation of these into a profile.
3.7
Malicious software and attack tooling. Malware, ransomware, stealers, loaders, botnet components, exploit kits, phishing kits, credential harvesters, and tooling whose principal purpose is unauthorised access to systems or accounts. Malware samples shared for coordinated research are handled through security@rsx.group, not by uploading them here.
3.8
Fraud and deception. Phishing pages, spoofed sign-in screens, fake documents, counterfeit assets, and material forming part of a scheme to deceive anyone out of money, credentials, or property.
3.9
Sexually explicit material. Pornography and sexually explicit imagery are not permitted. RSX accounts are open from age 16, we operate no age assurance, and a CDN link is by design something that renders in someone else’s message. This is a decision about what this service is for rather than a judgement about the content.
3.10
Content facilitating serious crime: the sale or supply of controlled drugs, weapons, or stolen data; human trafficking; and instructions for manufacturing weapons capable of mass harm.
3.11
Infringing content. Material that infringes copyright, trade marks, database rights, or other intellectual property, including circumvention tools and material published in breach of a licence. See section 10.
3.12
Content unlawful where we operate. Anything unlawful under Polish or European Union law, or under the law of a country whose authorities lawfully require us to act.
3.13
Impersonation. Content presenting itself as coming from RSX, Whitehill Group, our staff, another user, or any organisation, where it does not.

04Content that is permitted, with conditions

4.1
Some content is allowed but constrained. Where a condition below is not met, the content is treated as breaching this policy.
ContentCondition
Graphic violence, injury, or deathNot permitted at public visibility. Documentary, news, medical, and safety material may be stored unlisted or private.
Security research artefactsProof-of-concept code and captured traffic are permitted where they are not weaponised and do not contain live credentials or third-party personal data.
Datasets containing personal dataPermitted only where you hold a lawful basis, and not at public visibility. You remain the controller.
Content about a real personPermitted where it is accurate or clearly identified as fiction, satire, or edited. Synthetic depictions must not be presented as genuine.
Automated or bulk uploadsPermitted within the published limits and from your own account. Spreading load across accounts or keys to defeat a limit is not.
Redistribution of someone else's workPermitted where the licence allows it. Keep the notices the licence requires.
4.2
Storage is provided for your own use. Using an account principally as free infrastructure for a third-party product, or as an origin for another service’s traffic at a volume the free quota is not intended to carry, is a breach of these conditions rather than a clever use of them.

05How content is reviewed

5.1
We do not monitor what you upload. There is no general review of content, no operator reads your files as a matter of course, and no obligation is placed on us to look. Content is examined only in the circumstances in this section.
5.2
We reserve the right to review any content. Where we have a reason to, we may open, inspect, and where necessary retain a copy of any file, at any visibility, including private files. We do not undertake to do so, and the absence of review is never an approval of what you have uploaded.
5.3
Automated scanning. Images passing through our infrastructure are matched against hashes of known child sexual abuse material by a tool operated by our infrastructure provider. This is the only automated content scanning we run. It compares hashes and does not read, classify, or profile your files, and no operator sees a file because of it unless it produces a match.
5.4
Everything else is reactive. Content is reviewed where it is reported under section 6, where an automated abuse or security signal identifies it, where it is relevant to an investigation into an account, or where an authority lawfully requires it.
5.5
Decisions are made by a person. Except for automated matches under clause 5.3, and for automated rate and abuse controls that restrict traffic rather than remove content, a decision to remove content or act against an account is taken by a human being who has looked at the material and the report.
5.6
Operators reviewing content do so under confidentiality, with the least access the task needs, and every review is recorded in an audit log against the file and the operator.

06Reporting content

6.1
Anyone may report content, whether or not they hold an RSX account. Write to abuse@rsx.group. This is our notice and action mechanism, and it is the address to use for content believed to be illegal as well as for content believed to breach this policy.
6.2
A report is easier to act on quickly when it contains:
  • ·the link, in full, to each item you are reporting;
  • ·what is wrong with it, and which part of this policy or which law you say it breaches;
  • ·enough explanation for us to see why, without us having to guess;
  • ·a statement that you believe your report to be accurate and complete, made in good faith;
  • ·your name and an email address, unless the report concerns the sexual abuse of a child, in which case you may report anonymously.
6.3
We acknowledge reports without undue delay, and normally within three working days. We decide in a timely, diligent, non-arbitrary and objective manner, and we tell you what we decided and why.
6.4
A report that contains the information in clause 6.2 and concerns content we can identify from it gives us actual knowledge of that content. We act on that knowledge; we do not treat a report as read.
6.5
Do not attach the material to your report. Link to it. Sending files, particularly content depicting the abuse of a child, may itself be an offence.
6.6
Reports made in bad faith, at volume, or without foundation are themselves a breach. See section 11.

07What we do about it

7.1
Where content breaches this policy we take the least action that resolves it. What is available to us:
MeasureEffect
Revoke a linkThe link stops resolving and is purged from the edge. The content is retained and the action can be reversed.
Delete contentThe link is removed permanently. The stored bytes are erased once no other link points at them.
Purge contentEvery link to that content is removed, including links held by other accounts. Reason-required, and used for takedowns.
Restrict visibilityContent is forced to unlisted or private rather than removed.
Block deliveryAn account's content stops being served while a matter is open.
Restrict the accountUploads blocked, quota reduced, or rate limits tightened.
Suspend or terminateAccess ends and the account’s content stops being served, on the grounds and by the process in section 7 of the Terms of Service.
7.2
The first six measures act on content. The last acts on the account, and is governed by the Terms of Service rather than by this policy: a file is removed under this document, a person is removed under that one.
7.3
Action is proportionate to what happened. We weigh the severity of the breach, whether it was deliberate, whether the content was public, whether anyone was harmed, and what has happened on the account before.
7.4
Immediate removal without prior notice applies to content within clauses 3.2 to 3.4, to an active attack, and to anything we are lawfully ordered to remove. Notice follows the action rather than preceding it.
7.5
Because identical content is stored once and shared between the links that point at it, deleting your link does not necessarily erase the bytes: they remain while another account holds a live link to the same content, as that account’s content rather than yours. A purge under clause 7.1 removes every one of them.

08Telling you why

8.1
When we restrict or remove your content, we tell you. Our statement of reasons will say:
  • ·what we did, and to which content;
  • ·whether the content was removed, made inaccessible, restricted, or left in place with the account restricted instead;
  • ·whether the decision followed a report, an automated signal, our own detection, or an order from an authority;
  • ·whether automated means were used, and if so where;
  • ·the ground: which clause of this policy, or which law, and how the content breached it;
  • ·how to challenge it, and by when.
8.2
We send it to the email address on the account, without undue delay after the action takes effect.
8.3
We may withhold detail where giving it would prejudice an investigation, breach a legal obligation or an order, put a person at risk, or reveal how a detection measure works. We will say that we have withheld it.
8.4
Where the content was reported, we tell the person who reported it what we decided, without disclosing your identity to them.

09Challenging a decision

9.1
You may challenge any decision to remove or restrict your content, or to act against your account. Write to appeals@rsx.group within 30 days of the statement of reasons, from the email address on the account.
9.2
Say which decision you are challenging and why it is wrong. New information helps. One appeal per decision.
9.3
Appeals are decided by a person, and never by the automated system that produced the decision. Where practical, by someone other than whoever decided first. We aim to respond within 14 days.
9.4
If we were wrong, we reverse it and say so. Content removed but not erased is restored. Content already erased cannot be, which is one of the reasons erasure is reserved for cases where it is warranted.
9.5
Terminations for content within clause 3.2 are final and are not reinstated on appeal. This mirrors clause 7.3 of the Terms of Service.
9.6
Nothing here removes your right to go to a court, or to complain to a competent authority. RSX is operated by a very small group and the exemptions available to providers of our size mean we are not obliged to operate a formal internal complaint-handling system or to submit to out-of-court dispute settlement. The process in this section is offered anyway, and we hold ourselves to it.

11Repeat breaches and misuse of reporting

11.1
An account that repeatedly uploads content in breach of this policy is suspended, and on continued breach terminated, whether or not each individual item was serious. Repetition is itself the ground.
11.2
We warn before suspending, except where the content falls within clause 7.4.
11.3
A person or organisation that repeatedly sends reports or notices that are manifestly unfounded may have their reports deprioritised, and we may decline to process further reports from them for a stated period. We will tell them first.
11.4
Creating new accounts to continue after a suspension or termination is evasion, and is grounds for terminating every account involved under section 7 of the Terms of Service.

12Authorities and mandatory reporting

12.1
We act on orders from competent authorities to remove specific illegal content, and on lawful orders to provide information about a user. We check that each order is valid, specific, and within the issuing authority’s jurisdiction, and we act only within its scope.
12.2
We inform the issuing authority of the effect given to its order, and we tell the user concerned unless the order or the law prohibits it.
12.3
Child sexual abuse material is reported. Confirmed material is preserved as required, reported to the competent authorities and to the relevant reporting body, and the account is terminated. This happens without notice to the account holder and is not subject to appeal.
12.4
Where we become aware of information giving rise to a suspicion that a criminal offence involving a threat to the life or safety of a person has taken place, is taking place, or is likely to take place, we inform the relevant law enforcement or judicial authority.
12.5
Requests from authorities go to legal@rsx.group, in English or Polish. What we retain, and for how long, is in the Privacy Policy.

13Changes to this policy

13.1
We update this policy as the Services change, as we learn what actually turns up on them, and as the law changes. It is the document we expect to amend most often, which is why it is separate from the Terms of Service rather than a section inside them.
13.2
For changes that materially restrict what you may store, or that materially change how we enforce, we give at least 30 days’ notice by email or through the ID Portal before they take effect. Content that was permitted when uploaded is not removed without that notice, unless it is unlawful.
13.3
Clarifications, examples, and changes to contact details take effect when published.
13.4
The version and effective date at the top of this page always reflect the current text. Superseded versions are available on request from legal@rsx.group.

14Contact

14.1
Report content: abuse@rsx.group. Challenge a decision: appeals@rsx.group. Copyright, legal notices, and orders from authorities: legal@rsx.group. Privacy and data rights: privacy@rsx.group. Vulnerabilities: security@rsx.group.
14.2
legal@rsx.group is our single point of contact for authorities and for users in relation to this policy. We accept correspondence in English and Polish.
14.3
RSX is an unincorporated group operating from Silesia, Poland, under the Whitehill Group banner. Responsible operator: paige@rsx.group.