# Terms of use

The rules for using releaseszn and what you agree to when you post a release.

> [!NOTE]
> Draft, not yet in force. Before releaseszn opens to the public, it will
> be reviewed and will name who runs releaseszn, with a contact address
> and the province whose law applies. Last updated: October 21, 2026.

releaseszn is run from Canada. By using the site or its
API you agree to these terms. If you don't, please don't use releaseszn.
How we handle your data is in the [privacy policy](/docs/privacy).

## Your account

- You sign in with a GitHub account and must follow GitHub's own terms.
- One person, one account. Accounts created to vote, view or post on
  someone's behalf are not allowed.
- Keep your API tokens secret. You're responsible for what's done with
  them; revoke a token on `/settings/tokens` if it leaks.

## What you post

- **Only post software you made or are allowed to post**, with screenshots
  that show it truthfully.
- **You keep your rights.** By posting a project, release, changelog,
  screenshot or GIF, you give releaseszn a worldwide, free,
  non-exclusive licence to store, copy, resize, convert (for example GIF to
  video), display and distribute it on releaseszn, in its feeds, boards,
  badges and API, and in posts promoting releaseszn. The licence ends when
  you delete the content, except for copies already in backups (until they
  expire) and posts already published.
- You confirm that what you post doesn't break anyone's copyright,
  trademark, privacy or other rights, or the law.
- Release requirements (screenshot quality, changelog, versions) are on
  [release requirements](/docs/release-requirements); posts that don't meet
  them aren't published or ranked.

## Not allowed

- Spam, advertising disguised as a release, or the same release posted
  again to gain visibility.
- Malware, or software that harms its users or their devices.
- Misleading screenshots or descriptions.
- Hateful, harassing, sexual or illegal content.
- **Gaming the boards:** buying, trading or coordinating votes, voting or
  viewing with extra accounts, scripted views or votes, or asking people
  outside the site to upvote in bulk.
- Getting around rate limits, probing for security holes without telling
  us, or loading the site or API harder than normal use. Found a security
  problem? Report it through the [feedback form](/feedback) and we'll
  thank you.

## Moderation

We can hide or remove any project, release or media, refuse
submissions, discount votes we believe are not genuine, and suspend or ban
accounts that break these terms, with or without notice. Placements on the
boards can be withdrawn if they were won by breaking these terms.

If we hide one of your projects or releases, your settings page says so, and
[/appeal](/appeal) shows what was hidden and why. You can appeal each
decision once, in up to 1000 characters; a moderator reviews it and either
reverses the decision or keeps it. A suspended account can't sign in, but
signing in with GitHub still opens the appeal page. For anything else, use
the [feedback form](/feedback).

Anyone can report a release with the **report** link on its page.

## The boards

Release of the Day, Week and Month are decided by votes, weighted as
described in [how ranking works](/docs/ranking). Rankings and placements
are our editorial decision: nobody is owed a placement, and **no placement
can be bought**.

## Our service

- releaseszn is provided **as is**, without warranty. We try to keep it
  running and your content safe, but we may change, pause or stop any part
  of it, including the API.
- Software listed on releaseszn is made by its authors, not by us. We don't
  check it for safety; download and run it at your own risk.
- To the extent the law allows, we're not liable for indirect or
  consequential losses, lost data or lost profits from using releaseszn.

## Ending

You can stop using releaseszn and delete your projects at any time. We can
end your access if you break these terms.

## Changes and law

If these terms change, the new version is posted here with its date, and
significant changes are announced on the [blog](/blog). Continuing to use
releaseszn after a change means you accept it.

Questions: the [feedback form](/feedback).