Privacy policy

Who is responsible for your data

The operator identified below is the data controller for the processing described in this policy. “StatTier”, “we” and “us” refer to that operator. This policy covers our website and the services we provide through it; other services you choose to visit have their own privacy policies.

Privacy contact

privacy@stattier.com

The operator’s legal identity or public contact details have not yet been provided. This notice is incomplete until those details are available.

Account and sign-in information

We process your email address, chosen username and the earlier usernames you used with the dates you changed them, an optional profile picture, internal account and sign-in identifiers, verification status, account dates, roles and account status. A sign-in provider may also supply a display name or avatar. Support and moderation staff can see your email and username history when they handle your account, a report or suspected abuse. Your username history is kept while your account exists and removed when account deletion completes; a username you give up stays reserved for you for 30 days. Google or Discord sign-in shares the identity information authorized during that sign-in flow; it does not give StatTier access to your unrelated messages or files.

Supabase Auth manages authentication, password credentials, verification and recovery. If you use an email and password, our sign-in, registration and password-reset forms relay those credentials through our server to Supabase. Our application database does not store your plaintext password. Authentication and email-delivery providers process the information necessary to complete these operations.

You can browse eligible public content without an account. Account information is required for features such as saving work to your account, publishing, commenting and submitting support requests.

Content and information you provide

We store the Templates, Cards, Stats, settings, images, versions, saved rankings and results you create or import. This includes their titles, descriptions, tags, values and other information you put in them. Uploaded files may initially contain embedded metadata; we process the file and create display versions with embedded image metadata removed. Original filenames and technical details such as format, dimensions and size can remain in media records and be visible to authorized recipients.

We also process Likes, creator stars, contribution and reward records, comments and replies, suggested corrections, recommendation dismissals and sharing or reuse choices. Suggestions can include the original and proposed values, a comment and a source link. The submitting user and the Template owner can view a suggestion; accepted changes become part of the Template.

If you contact support, report content or appeal a decision, we process your message, attachments you choose to provide, relevant content references, case status and the response. A screenshot may include personal information about you or someone else. Include only what is needed; remove passwords, access tokens and unrelated personal information before submitting it.

Technical and security information

Delivering the service requires processing network and request information such as IP addresses, browser and device information, request times, requested resources, authentication state and errors. Hosting, authentication, storage and security providers may process this information when handling requests. Security controls also use account or network-derived identifiers to limit abusive requests and protect access.

Operational logs and administrative audit records can include internal identifiers, action types, reasons and timestamps. Access is limited according to support, moderation and operational responsibilities. Private content is not generally accessible through public pages or ordinary user accounts, but authorized processing for support, security and legal obligations is possible.

Why we use personal data

We use data to authenticate you; save, display and share the content you request; provide rankings, comparison and reuse features; deliver account messages; answer support and data requests; maintain account limits; and handle account or content deletion.

We also use data to detect abuse, investigate reports, enforce content rules, troubleshoot failures, protect other users and maintain records needed for security or legal claims. Usage measurements help us understand service performance and improve features. Recommendations use the tags of Templates you liked or completed, together with Templates you dismissed; they are not based on the private text of your Cards.

Legal grounds for processing

Where the GDPR applies, processing necessary to provide the service you request relies on performance of a contract or steps you request before entering one. Optional analytics identifiers and account-linked product measurement rely on your consent. You can withdraw that consent without losing access to the core service.

Our legitimate interests include keeping StatTier secure and reliable, investigating misuse, maintaining necessary operational records, and providing relevant discovery and aggregate usage information. These interests must be balanced against your rights. Any measurement that requires consent under applicable tracking rules must have that consent; the absence of cookies alone does not establish an exemption.

We may also process information to comply with a legal obligation, such as responding to a valid legal request. We do not treat acceptance of this privacy policy or continued use of the site as blanket consent to processing. Different grounds and rights may apply under the law of your country.

What other people can see

Public Templates, their published Cards and images, public comments and author pages can be viewed by other people and indexed by search engines. Author information can include a username, a profile picture you choose once it passes our content check, join date, creator rank and public activity or contribution counts. We do not make your account email public as part of your profile. Information you include yourself in a title, image or comment can nevertheless be personal data.

Content shared by link is available to people who satisfy that link’s access requirements. A live-draft link can expose the current shared draft, including later changes. People with access may copy or download content. Revoking a link stops new access through that link; it cannot retrieve copies already received or immediately invalidate every previously issued temporary media URL.

An unshared individual ranking is not published as your personal result. However, completed rankings can contribute to community ranking statistics even if you have not shared the individual result. Community results require at least five eligible participants. Each displayed Card also requires rankings from at least five eligible participants; Cards below that threshold are omitted. These thresholds do not guarantee anonymity.

Copies, forks and community images

When you enable copying of a Template or sharing of your images with the community, other users can obtain permission to reuse the eligible content. Reuse can preserve the source content, attribution, image titles, tags and other relevant metadata. Only share material you are entitled to share, and avoid including personal information that should not remain available.

Turning off future sharing, removing an image from your library, or deleting the original Template or account does not necessarily remove copies or images that other users already acquired. Their results and permitted copies may retain the content they depend on. You can still contact us about personal-data rights, unlawful content or other grounds for restricting that material; a reuse permission does not override applicable law.

Screenshot recognition and local processing

Screenshot recognition in Stats and Fill Cards starts in your browser. Selecting a screenshot for recognition does not by itself upload it to your media library. Recognition assets are served by StatTier; the browser reads the image locally.

If recognition fails and you explicitly choose server processing, the prepared image region is sent to our server. The current fallback uses locally hosted recognition software, not an external generative-AI service. Temporary request files are removed after processing. Saving recognized fields or separately uploading an image stores the data you choose to save. Adjusting a display frame changes what is shown; it is not the same as permanently removing pixels from the source image.

Content checks, reports and decisions

Content you publish or share, including content accessible by link, community images and comments, may be checked automatically or reviewed following a report. Depending on the enabled moderation mode, checks can run before publication, after publication or when content is reported. A publicly visible item has not necessarily been reviewed or approved.

When OpenAI moderation is enabled, relevant text or a processed image is sent to OpenAI to assess potentially harmful content. We do not add your account email or username as separate identity fields to these requests, but the content itself may contain personal information. We store check results and records needed to apply and review decisions.

Automated checks can place content on hold or restrict its availability. Authorized moderators can review relevant content and record a decision; not every decision is made by a person. If a decision affects your content, use the available appeal option or contact us to request review. Do not send suspected illegal child-abuse material as an attachment; report the relevant location instead.

Service providers and other recipients

Supabase provides authentication. Your chosen Google or Discord sign-in provider processes its own sign-in flow under its terms. Hosting and database providers process the application’s stored data and requests; image-storage providers process uploaded files and delivery requests. The planned alpha deployment uses UpCloud servers for the application and an operator-managed PostgreSQL database, with Cloudflare R2 for image storage. Account emails are delivered through the email service configured for authentication. Zoho Mail processes correspondence sent to our support and privacy mailboxes.

OpenAI receives content submitted for automated moderation. Sentry receives limited error diagnostics when error monitoring is enabled. PostHog receives product-usage events when analytics is enabled, as described below. Optional Discord operational alerts contain service-incident status and an event reference, rather than report attachments or user-authored content.

Authorized support staff, moderators and operators may access information needed for their responsibilities. We may disclose information where required by law or where a lawful and necessary response is needed to protect people, investigate abuse or defend legal rights. Public content and content you authorize others to access are disclosed according to your sharing choices.

We do not sell personal data or use it to deliver behavioral advertising. A provider may also process service or security information under its own legal responsibilities. This policy does not mean that every provider uses information exclusively on our instructions for every purpose.

Product analytics and diagnostics

When PostHog is enabled, we send page-view and selected feature-action events, event times and technical browser or device information. Event URLs are reduced to remove query strings, link fragments, record identifiers and author handles. The event sanitizer removes page titles and campaign or search values. We do not intentionally include Template contents, entered Stat values, screenshot pixels, support messages or authentication tokens in product analytics.

If you allow optional analytics, PostHog may store an identifier in cookies and local storage and link activity to a pseudonymous account identifier. This identifier is derived from your account; pseudonymous information is not the same as anonymous information.

In the current cookieless measurement mode, declining optional analytics or leaving the choice unanswered does not stop all event transmission. Limited events still reach PostHog without a persistent analytics identifier on your device. The request includes network and browser information, including an IP address and user-agent information. These are individual measurement requests, not only precomputed totals. The choice applies to this browser; changing it does not itself delete events already received by the provider.

Sentry helps diagnose errors using information such as error type, code location, application release and environment. Our diagnostic filters remove user identity fields, request contents and other disallowed event data. The provider still handles the network connection, so filtering an IP address out of an event does not mean it is never processed during transmission. Session recording and automatic capture of clicks or typed content are disabled.

Service statistics and recommendations

Separate from PostHog, StatTier records Template views, starts, completions and contribution activity to provide creator statistics, popularity sorting, community results, rewards and service controls. The optional product-analytics choice does not disable these service records. A keyed account or network-derived identifier is used to deduplicate eligible views; creators receive aggregated statistics rather than a list of viewers’ network addresses.

Recommendations use your Likes, completed rankings and saved dismissals to suggest relevant Templates. You can turn recommendations off in Settings → Appearance and reset their history there. Resetting forgets earlier recommendation signals and dismissals without deleting your Likes or saved rankings. Turning recommendations off hides personalized and similar-template recommendations for your account; it does not delete the activity records needed for other service features. Public popularity and community ranking features use aggregate activity. Contact us if you wish to object to processing based on legitimate interests. Removing an individual record does not necessarily change statistics that can no longer be linked to that record.

Your private notification inbox shows up to 50 recent comments, replies and suggestion updates from the last 30 days. It stores a read-through timestamp rather than copies of comment or suggestion text. Visibility is checked again when you open the inbox. Authors can pause new comments or hide individual comments in their discussions; this does not override platform moderation. Creator charts can also show current Likes and visible comments grouped by their original date, so removing or hiding the source can reduce earlier totals.

Cookies and storage on your device

Necessary cookies support sign-in, sign-in verification, password recovery, protected share links and request-forgery protection. The main session cookie lasts up to seven days per issuance; sign-in handshakes last ten minutes, email verification or recovery handshakes one hour, and protected-share sessions six hours. A session may be renewed during use or cleared earlier. Browser preferences can use additional first-party storage.

Local storage also keeps interface preferences, your analytics choice, draft-recovery data and guest ranking progress. Some local records contain your work and may remain until you clear them or the application removes them; account deletion does not remotely erase every browser or downloaded file. On a shared device, sign out and clear stored site data when needed. Clearing storage may remove unsaved work.

If optional analytics is allowed, PostHog can use cookies and local storage for its identifier. The current SDK sets an analytics cookie lifetime of up to one year, which can be renewed; local-storage entries may persist until cleared. Declining keeps the choice itself in local storage and uses the cookieless mode described above. Blocking all site cookies can prevent authentication or protected sharing from working.

How long information is kept

Account and content data are kept while needed to provide the account, maintain the content you save, fulfill permitted sharing and reuse, or deal with security and legal matters. Retention is not identical for every type of data. The periods below describe scheduled cleanup eligibility; completion depends on background processing and any applicable legal preservation requirement.

A deleted Template normally has a seven-day recovery window unless you choose immediate permanent deletion. Ordinary media deletion normally has a 48-hour recovery period, subject to existing references. Removing a Template does not automatically remove its images from your media library. Other users’ saved dependencies and acquired community media are handled separately.

For first-party creator analytics, view-deduplication records become eligible for cleanup two days after the last counted view. Hourly aggregates are retained for 72 hours, daily aggregates for 90 days and monthly aggregates for 36 calendar months. Report evidence snapshots have a 30-day expiry or are cleared after the report is closed; this does not mean that the report, all attachments or every moderation record is deleted at that time.

Support correspondence, moderation decisions, appeals, administrative records and retained account identifiers may need to outlast an individual content item or account to resolve cases, enforce restrictions and protect legal rights. Provider telemetry, infrastructure logs and backups have separate retention settings. You can request information about the records retained about you and the applicable retention grounds. We do not promise that deleting an active record immediately removes every backup or provider copy.

Deleting your account or content

Where account deletion is enabled, you can request it from your account settings and cancel it, after confirming your identity, until the deadline shown: seven days after your deletion request. After that window, final deletion is processed in the background. Processing can take additional time, including retries when a provider is unavailable; seven days is not a guarantee that all copies have disappeared.

Final account processing removes your StatTier sign-in account from Supabase, clears your public profile details and deletes or clears eligible private content and activity records. A retained account record, including internal and authentication identifiers and lifecycle dates, can remain to prevent accidental account restoration and maintain security or dependency records. Deleting an account is therefore not a promise that every remaining record is anonymous.

Content needed by another user’s saved ranking or result, permitted forks, and acquired or promoted community images can remain, including text or attribution already contained in that content. Certain audit and moderation records may also remain. If retained content contains personal information you want removed, contact us so the request can be assessed separately. Public copies downloaded by others are outside our direct control.

When you request account deletion through the app, we also attempt to request deletion of account-linked PostHog data. This can happen during the seven-day cancellation window; cancelling account deletion does not restore analytics data already erased. Provider cleanup may need follow-up if its configuration or request fails. Use the privacy contact for an access or erasure request even if you no longer have an account. Your Google or Discord account is not deleted by deleting your StatTier account.

Security

We use access controls, authenticated storage access, limited-duration media links, role-based administrative permissions and restrictions on diagnostic data to protect information. Content is not end-to-end encrypted: the service and authorized providers must process it to deliver the features you request. No storage or transmission method can guarantee absolute security.

If a personal-data breach requires notification under applicable law, the operator must notify the relevant authority and affected individuals as required. Report a suspected security or privacy problem using the contact details below, without including unnecessary sensitive material.

International processing

Our operator and providers may process information in different countries, including outside your country of residence or the European Economic Area. Choosing an EU data-storage region for a provider does not by itself mean that every support, security or subprocessor operation stays in that region.

International transfers must have the protections required by applicable law, which may include an adequacy decision or appropriate contractual safeguards. Contact us for the recipients and transfer safeguards applicable to your information, including how to obtain a copy of relevant safeguards. We do not claim that all StatTier data is processed exclusively in the EU.

Your rights and how to contact us

Depending on the law that applies, you may request access to your personal data, correction, erasure, restriction of processing, or a portable copy of eligible data. You may object to processing based on legitimate interests and withdraw consent for consent-based processing. Withdrawal does not make earlier lawful processing unlawful. These rights can have conditions and exceptions, including the rights of other people.

Some changes and content exports are available in the application, but those exports are not a complete account-data archive. Use the privacy contact for a broader request or if you cannot sign in. We may request proportionate information to verify your identity; do not send an identity document unless it is necessary and specifically requested.

Where the GDPR applies, requests are normally answered within one month. If an extension is permitted because of the complexity or number of requests, we will explain it within that initial month. Other applicable laws may set different deadlines. If a request is refused, we will explain the reason and available avenues of complaint where required.

You can complain to a competent data-protection authority, including the authority in your EEA country of habitual residence, place of work or the alleged infringement where the GDPR applies. In Ukraine, you can contact the Ukrainian Parliament Commissioner for Human Rights. You do not have to contact us first to exercise a right to complain.

Information about children

Take particular care not to include children’s personal information in uploaded images, public content or support attachments. If you are a parent or guardian and believe that a child has provided personal data that should not be processed, contact us so we can review it and take the steps required by applicable law. This notice does not claim that StatTier verifies every user’s age.

Changes to this policy

We update this policy when our processing practices or applicable requirements change and identify the current version by the date above. We will draw attention to material changes through an appropriate service notice or other suitable communication. If a new use requires consent, we must obtain that consent; continuing to use StatTier is not a substitute.