Privacy policy

Last updated: 31 October 2026

S-Tier.app lets you create, save and share tierlists. This policy explains what information is used when you visit s-tier.app, sign in, save content online or share it with other people.

Who is responsible and how to contact us

S-Tier.app is operated by S-Tier.app, based in the Netherlands. For privacy questions and requests about your personal information, contact privacy@s-tier.app.

Information we use

• Account information. Google Firebase Authentication handles sign-in. If you use Google sign-in, it receives your Google account identity and basic profile information, including your name and email address. The app uses an account identifier, email and verification status, and a display name that you can edit. Our application database stores your account identifier, display name, plan, account status and creation time. We do not receive your Google password or request access to Gmail, Drive or your contacts.
• Your content. Tierlist names, descriptions, categories, tags, rankings, formatting, images, visibility choices, comments, likes and associated timestamps are processed when you create or interact with them. Uploaded images retain their original file metadata, which may include information such as a photo's location. Remove metadata or private details before sharing images if you do not want to disclose them.
• Technical information. Hosting and security services process information needed to deliver requests and protect the service, such as IP addresses, browser or device details, request times, errors and security events. The app also keeps records of sync operations and administrative actions.
• Limited website analytics. Cloudflare Web Analytics measures aggregate traffic and loading performance on the public homepage and privacy policy only. It does not run in the tierlist editor, My tierlists, accounts, image library, shared-tierlist pages or administration pages. Measurements can include page views, browser and device type, country, an origin-only referring website and performance timings. Performance diagnostics can include CSS selectors identifying page elements and source URLs of public images or other resources. Cloudflare receives technical request information, including IP addresses and user-agent details. This is not a promise that the underlying requests are anonymous. We do not deliberately send account identifiers, emails, display names, private tierlist content, searches or form entries.
• Messages you send us. If you contact us, we use the information in your message to respond and handle your request.

Why we use this information

We use account and content information to provide the features you request: signing in, saving and syncing tierlists, managing images, sharing lists, commenting and liking. Our legal basis for these requested account features is performance of our agreement with you (Article 6(1)(b) GDPR). We use technical and administrative records for our legitimate interests in operating a reliable service, preventing abuse and resolving sync problems. Processing necessary to meet legal obligations, including handling your statutory privacy rights, is based on Article 6(1)(c) GDPR. Where a feature relies on consent, we will ask for that consent separately.

We use limited Cloudflare measurements for our legitimate interests in understanding public website traffic and improving loading performance (Article 6(1)(f) GDPR). We restrict this measurement to reduce its privacy impact: only the production homepage and privacy policy can load it, pages with query strings or URL fragments are skipped, and a referring address is accepted only when it contains an origin without credentials, a page path, query or fragment. We do not use these measurements to build individual visitor histories across sites. This limited setup does not use an analytics consent popup.

We do not sell personal information or use analytics for advertising, and we do not link website measurements to your S-Tier.app account. Google account information is used to authenticate your account and provide the requested account features, not for advertising or training AI models.

What stays on your device and what syncs

Your browser stores drafts, cached images and pending changes locally so that editing can continue offline. Device-only drafts stay in that browser until you choose to add them to an account or otherwise upload them. Account tierlists and pending changes can sync automatically when a connection is available, as well as when you choose Sync.

Signing out hides account drafts but does not erase their local copies. You can remove local data through your browser's site-data controls. Clearing site data can permanently remove device-only drafts and changes that have not synced. Data saved online is separate from your browser's local copy.

Sharing and visibility

New tierlists are private by default. A public tierlist can appear in Explore and be viewed by other people. An unlisted tierlist can be viewed by anyone who has its link. Using Share on a private tierlist makes it unlisted so the link can work for its recipients.

Shared tierlists can reveal their content, images, your display name, comments and activity counts. People may save or copy shared content. Making the original private or deleting it does not remove copies already made by other people. Avoid adding personal information to content you intend to share.

Services that process information

• Google Firebase Authentication provides account authentication, sign-in and related account emails.
• Google Cloud Run and Cloud Tasks run the application's API and background account-deletion tasks.
• Google Analytics 4 previously processed optional, consent-based usage measurements. We no longer send new measurements to Google Analytics; historical measurements remain subject to the retention described below.
• Neon PostgreSQL stores application account records, tierlists, content metadata and related interactions.
• Cloudflare delivers the website and its security services, and provides the limited Web Analytics measurements described above. Cloudflare R2 stores uploaded image files. Cloudflare Email Routing forwards messages sent to our privacy address to a Google Gmail inbox so that we can respond.

These providers process information to supply their services. Information may also be disclosed when legally required or necessary to investigate misuse and protect people's rights or the service. We do not give other users access to private account content through ordinary sharing features.

Where information is processed

The configured application database is in Frankfurt, Germany, and the API runs in Belgium. These locations do not mean that all processing is limited to the European Economic Area: Google, Cloudflare and other service providers may process information in other countries. Their applicable data-processing terms and international-transfer safeguards govern that processing.

How long information is kept and how deletion works

Account information and saved content are kept to provide your account and the features you use. There is currently no automatic deletion of accounts just because they are inactive.

Deleting a tierlist removes it from normal access but does not immediately purge every underlying database record. Sync-operation records can also contain earlier submitted content. Removing an image from one list does not necessarily delete the file if it remains in an image library, template or another copy of a tierlist.

Delete your account: open Account, choose Delete account and complete the confirmation and recent sign-in check. Once accepted, the account is disabled while deletion runs. The process removes your Firebase sign-in identity and application account record, your owned tierlists and templates, your comments and likes, and associated sync-operation and administrative records.

Image files that are no longer needed by another account, tierlist or template are deleted from R2. Images and independent copies still used by other people can remain; the link to your deleted account is removed. The original image bytes, including any embedded metadata, may remain in those copies. Copies downloaded outside S-Tier.app cannot be withdrawn by us.

Deletion can remain in progress while an upload link expires or a provider is unavailable. Accepted requests are recorded durably and retried; the app shows whether the request is pending or completed. A temporary hashed account identifier and processing timestamps prevent old sign-in tokens from recreating a deleted account. They become eligible for cleanup after the token-protection period. No password or sign-in token is stored in the server's deletion record.

The browser performing the deletion clears the deleted account's local drafts, cached images and queued changes. Unrelated device-only drafts remain. Other browsers may still hold offline copies, which you can remove using their site-data controls. Provider backups and operational logs can remain until their separate retention periods expire; deleting an account does not immediately remove those copies. Our ordinary Google Cloud application logs are configured for 30 days. Contact us if you need help deleting data or confirming an outstanding request.

Website analytics has a separate retention period from account content. Cloudflare documents seven days of unsampled beacon data, followed by aggregation and sampling for longer-term storage; Web Analytics reports are accessible for the previous six months. The existing Google Analytics property is not deleted: its historical user-level and event-level measurements remain configured for two months of retention, without resetting on new activity, and aggregate reports may remain longer. Removing Google Analytics stops new collection but does not erase measurements already received. Because analytics is not linked to accounts, deleting your account does not identify or automatically erase previous analytics measurements. Contact us for help with an analytics data request.

Cookies and browser storage

The app uses browser storage for sign-in sessions, appearance preferences, offline editing and caching its application files. Authentication credentials are kept in the tab's session storage; the Firebase popup SDK uses an in-memory session. Google sign-in and hosting or security providers may use their own cookies or similar storage to perform authentication and protect their services. We do not use application cookies for advertising.

Cloudflare Web Analytics does not create analytics cookies or local-storage visitor identifiers and does not use fingerprinting to identify visitors. You can disable browser measurement using the control below. We store only a simple disabled preference in this browser until you change it or clear site data; it is not a visitor identifier. An unexpired rejection from the former Google Analytics controls is converted to this disabled preference, then the former choice record is removed. Do Not Track and Global Privacy Control also prevent measurement, even if you enable it here. Disabling analytics reloads measured public pages to stop an already loaded beacon; this does not reload the editor. The app removes its former Google Analytics cookies, including stier_ga and stier_ga_6DNHKEQQRT, when this cleanup can run in your browser. Browser storage used for the app's requested features remains as described above. You can also object to processing based on legitimate interests by contacting us.

Your choices and rights

You can edit your display name, change sharing settings and remove content using the app's available controls. Depending on the law that applies to you, you can also request access to your personal information, correction, erasure, restriction, an export in a usable format, or object to processing based on legitimate interests. Where processing depends on consent, you can withdraw that consent. Contact us to make a request; these rights may have legal limits.

You can raise a concern with the data-protection authority where you live or work. As we are based in the Netherlands, you can complain to the Autoriteit Persoonsgegevens.

Changes to this policy

We may update this policy as the service changes. The date above identifies the current version. Material changes will be explained through an appropriate notice in the service or another suitable channel.