Relay Policy & Terms of Use

1What hasky.chat is

hasky.chat is a Nostr relay — a server that receives, stores, and forwards signed messages ("events") on behalf of the people and applications that connect to it. It is operated by an individual, not a company. Connecting to it, reading from it, or publishing to it means you accept this policy.

The relay is a piece of communications infrastructure, comparable to a mail server or a message queue. It carries what its users send. It does not curate, recommend, or editorialise that content.

2The operator's role

The operator provides hasky.chat as a passive conduit and host for user-published events. The operator:

• does not author the content that users publish;
• does not review or pre-screen events before they are stored or served — content appears without prior human moderation;
• does not monitor traffic for content, beyond automated limits that protect the service (see §7); and
• does act on valid reports by removing specific content and, where necessary, blocking the source (see §8–9).

3Acceptable use

You may use hasky.chat to publish and retrieve Nostr events for lawful purposes. When you publish through this relay, you confirm that:

• you have the right to publish the content;
• the content does not break the law of any jurisdiction that applies to you or to the operator; and
• you will not use the relay to harm the service or other users.

4Prohibited content and conduct

The following are not permitted on hasky.chat. Publishing them is a breach of this policy and will lead to removal and blocking:

• Child sexual abuse material (CSAM) or any sexualisation of minors — zero tolerance; such material is removed on discovery and reported to the relevant authorities.
• Content that is illegal under applicable law, or that solicits, facilitates, or incentivises illegal acts.
• Credible threats of violence, incitement to violence, or targeted harassment of a person.
• Malware, phishing, or content designed to compromise devices or steal credentials.
• Non-consensual intimate imagery, doxxing, or material that violates another person's privacy.
• Content that infringes copyright, trademark, or other intellectual-property rights.
• Spam and automated abuse — high-volume flooding, artificial engagement, or scripted traffic that degrades the service.

5Private messages

Some events the relay carries are encrypted direct messages (for example NIP-17 "gift wrap" events). These are end-to-end encrypted between sender and recipient.

Because their content is invisible to the operator, encrypted messages are governed by the abuse process in §8–9 only to the extent that the outer event can be identified.

6Data and privacy

What the relay stores

• Published events — the signed events you send, kept so they can be served to other clients. Public events are, by design, public.
• Operational logs — connection metadata (such as IP address, timestamps, and request counts) generated automatically by the server and its proxy, used to run and protect the service. These are not published and are retained only as long as needed for operations and security.

Deletion

You may request deletion of your own events using a standard Nostr deletion event (NIP-09) signed by the key that created them; the relay honours these. Note that Nostr is a distributed network — content you published may already exist on other relays beyond the operator's control, and deletion here does not remove it elsewhere.

7Enforcement and service protection

To keep the relay available and within these rules, the operator may, at its discretion and without notice:

• apply automated rate limits, size limits, and event-kind restrictions;
• refuse, remove, or stop serving specific events;
• block specific keys or network sources from publishing;
• restrict who may publish, up to and including limiting writes to an allowlist; and
• suspend or discontinue the service.

These measures protect the service and other users and do not amount to editorial review of content.

8Reporting abuse

If you believe content on hasky.chat breaches §4, or infringes your rights, report it to the contact in §11. To let the operator act quickly, please include:

• the event ID (and author public key, if known) of the content;
• a short description of the problem and which rule it breaches; and
• for rights complaints, enough detail to identify the right and your relationship to it.

Reports made in good faith are welcome. Reports that are knowingly false or abusive may themselves be treated as misuse of the service.

9Takedown process

On receiving a valid report, the operator aims to review it promptly and, where the content breaches this policy or the law, remove it from the relay and, where appropriate, block its source. CSAM and imminent-harm reports are prioritised and acted on as fast as reasonably possible.

Removal from hasky.chat affects this relay only; it does not remove content from any other relay on the Nostr network.

10No warranty; limitation

hasky.chat is provided "as is", without warranty of any kind, and may be slow, unavailable, or discontinued at any time. The operator does not guarantee that any event will be stored, served, or retained. To the fullest extent permitted by applicable law, the operator is not liable for content published by users, for loss of data, or for any damages arising from use of or inability to use the relay.

11Changes, governing law & contact

This policy may be updated; the effective date and version at the top reflect the current version, and continued use of the relay means acceptance of the current policy.

Governing law confirm — This policy is intended to be governed by the laws of Denmark and the European Union. Confirm this with a qualified lawyer before relying on it.