Privacy Policy

1. Overview

Stryx Development operates Peeksi ("Peeksi," "we," "our," or "us"). This Privacy Policy explains how we collect, use, disclose, retain, and protect information when you use peeksi.org, a public Peeksi server profile, Discord login and dashboard features, or the Peeksi Discord bot.

Peeksi is a server-level trust service. It is not designed to rate individual Discord users. Some information described below comes from Discord and is already public or visible to an authorized server administrator; other information is generated when Peeksi verifies a server or you interact with the service.

2. Public Discord Community and Invite Data

When a user asks to view a server, Peeksi may request public invite and server information from Discord. We may store and display:

• server ID, name, description, icon, banner, splash, features, verification level, content setting, creation time, boost level, and vanity invite;
• invite code, source classification, channel information, creation and expiration information, usage limits, and whether the invite was valid when checked;
• approximate member and online counts, rolling count snapshots, and normalized server-level activity summaries;
• community topics inferred from public server information; and
• first-seen, last-seen, synchronization, validation, and temporary error or backoff records.

Peeksi checks saved invites when a user needs a results page. It does not randomly poll invites in the background. When a displayed invite is dead, Peeksi may test another saved invite and delete the invalid one. Public profiles can remain available after an invite expires.

Peeksi does not intentionally retain arbitrary raw search text as a separate profile. Searches placed in a URL may still appear in browser history, security logs, or hosting logs. A valid invite or server result may become part of Peeksi's server catalog.

3. Discord Login and Dashboard

Discord OAuth login requests the identify and guilds scopes. Peeksi receives your Discord user ID, username, global display name, avatar, discriminator where available, and the servers Discord returns for your account, including your owner or administrator permissions and available approximate counts.

Peeksi does not request your Discord email address. Your signed-in user, server list, and OAuth access token are kept in a server-side session so the dashboard can work and you can manually sync your servers. The access token is not sent to your browser or stored in the Peeksi database, and Peeksi does not retain an OAuth refresh token. Sync uses the token only while it remains valid and your session is active. Sessions expire after inactivity and after an absolute time limit. Logging out clears the session and Peeksi attempts to revoke the access token with Discord.

The site owner may grant page-moderation access by entering a Discord user ID. Peeksi then performs one bot-authenticated Discord profile lookup and stores that account's ID, username, global display name, avatar details, discriminator where available, grant time, and granting owner ID. This lookup does not message the account or interact with a Discord server. The profile and grant are deleted when the owner removes that moderator.

4. Ownership Claims and Public Profiles

If you claim a server, Peeksi verifies that the bot is connected and that Discord identifies your signed-in account as the current owner. We then store your Discord ID, username, global display name, avatar, discriminator where available, profile update time, the claimed server, and claim timestamps.

A verified owner's username, display name, avatar, and server relationship are public and may be indexed by search engines. The claim flow tells you this before you confirm. If the bot is no longer recently connected or the current owner no longer matches, Peeksi may stop displaying the owner while retaining records needed for integrity, re-verification, disputes, or legal obligations.

5. Bot Connection and Setup Authorization

While the bot is in a server, Peeksi stores the server ID, server name, Discord owner ID, join or availability timestamps, and periodic connection heartbeats. The bot refreshes that connection periodically and after relevant connection events. It also stores aggregate supported-channel and readable-channel counts with the check time to measure evidence coverage. These access snapshots contain no channel names, channel IDs, or message content. Public profiles show aggregate access counts while current setup is accepted and access is confirmed; permission restrictions and stale checks are distinguished.

After an authorized administrator accepts the current setup-v2 authorization, the bot may create one reusable Discord invite with no scheduled expiration or usage limit in a channel visible to everyone when Peeksi has no active invite saved for the server. Peeksi stores the invite code, channel information, creation settings, and validation timestamps so the public server profile can remain reachable. An administrator can revoke a particular invite, but Peeksi may create a replacement while current setup remains accepted, no active invite is saved, and the bot still has Create Invite permission. Opting out prevents future fallback invite creation; it does not automatically revoke an invite already created. Peeksi does not list private channel invites or poll Discord invites in the background.

The /setup command is available to members with Manage Server permission. Peeksi stores whether setup was accepted or declined, the setup-policy version, the deciding Discord user ID, the decision time, and when the 15 setup points were awarded. The current setup-v2 authorization is required for server analysis. An earlier setup version may retain its historical award record but does not activate participation points or authorize message sampling. Repeated acceptance does not stack those points. Opting out immediately removes the active setup points, stops future sampling, and leaves the bot connected but idle.

Peeksi uses current bot-connection status, current setup authorization, and earned server-level evidence to calculate the displayed score, confidence, and verification status. A profile remains on the public-only model unless it has both a current bot connection and accepted current setup authorization. The public-only model converts up to 40 earned public points to a displayed score capped at 60, shows Low confidence, and is labeled Not Peeksi Verified. This includes newly connected servers before setup acceptance, declined or opted-out servers, and servers where the bot was removed. A current bot connection together with accepted current setup unlocks the 100-point model with Medium confidence below 90. The profile shows Verification in Progress while its trust score is below 90. Public evidence keeps the same calibration and contributes up to 60 displayed points; current ownership can add 5 and active setup can add 15 while the full model remains active. Connecting the bot alone grants no points and does not change confidence or verification status. An actively connected, setup-authorized profile may also reflect protected server-analysis and longitudinal evidence, which can raise or lower the overall trust score. Servers become Peeksi Verified automatically when their current trust score is 90 or higher. These profiles also show High confidence. If the score drops below 90, Peeksi Verified and High confidence are removed; confidence returns to Medium while the 100-point model remains active or Low on the public-only model.

Evidence coverage measures server transparency to Peeksi independently of the trust score: up to 20% for current public data, 20% for a recently confirmed valid invite, and 60% proportional to readable supported channels. Public data includes 10% for profile details and 10% for member and online counts, checked within seven days; the invite must also have been confirmed within seven days. Channel access requires a connected bot, accepted current setup, and an access check from the last 15 minutes that follows the latest setup decision. With full public and invite coverage, access to 1 of 20 supported channels gives 43% evidence coverage even if the trust score is 95. Coverage does not change the trust score, confidence label, or Peeksi Verified status. Banned listings show 0%. Channel coverage counts top-level text, announcement, forum, and media channels where Peeksi can view messages and read history. Categories and voice channels are excluded. Private and archived threads are not separately measured, and channel access does not mean every message was reviewed. Missing or stale checks earn no coverage for that source; the profile distinguishes those checks from confirmed limited access. Coverage is not a probability of safety.

With current setup accepted, Peeksi also counts new messages delivered to the bot in channels it can view for the public Recent Activity chart. Bot and webhook messages are excluded. This activity feature does not read message content or scan message history, and it does not retain member, message, or channel identifiers. It stores the server ID, hourly message counts, observed duration, and limited processing timestamps and service-instance metadata. Counts are saved in batches about once a minute to build the seven-day chart and are scheduled for deletion after eight days. The chart covers only messages the bot observed while connected and authorized; inaccessible channels and periods when the bot is offline are not measured. Activity counting does not run before current setup acceptance, after opting out, or for a banned listing. Banned listings display zero activity. Without a connected bot, the listing invites administrators to add the bot instead of displaying an invite-derived activity chart.

This setup selection is a server administrator's operational authorization. It is not consent on behalf of every server member and does not waive a member's privacy rights.

6. Moderation and Message Processing

Signing in with Discord is required to report a public listing. Peeksi stores the reported server ID and name, the selected reason, any explanation you provide, the submission time, and your Discord user ID, username, and display name. Reports are sent to an authorized Peeksi administrator for manual review and remain in the moderation record after their notification is cleared.

Signing in is also required to post a community review. Peeksi stores the listing, your Discord user ID, a copy of your username, display name and avatar details, your star rating and review text, and posting and editing times. Your username, avatar, rating, review text, and review dates are public while the review is visible. Reviews contribute to the community star average, not the Peeksi trust score.

If a listing owner or administrator disputes a review, Peeksi stores their Discord identity, the explanation, a copy of the review as it appeared when disputed, and the submission and decision times. These dispute details are available to authorized listing owners and administrators and authorized Peeksi page moderators, not public visitors. Pending disputes alert authorized Peeksi page moderators through the notification bell. Deleted reviews leave public view, but review history, dispute evidence, and account-and-listing removal records may remain to resolve disputes, prevent abuse, and enforce review restrictions.

For each selected sample, Peeksi analyzes message text only in memory for configured server-level safety signals and surrounding context, then immediately discards the sampled content. Peeksi does not retain message text, message snippets, content hashes, embeddings, detected phrases or matches, or member, message, or channel identifiers from this analysis. It does not create member-level scores or profiles from sampled messages.

Peeksi retains only one server-level aggregate for each day, an operational sample count, a private processing-version reference, and processing and finalization timestamps. Recent moderation-analysis records are kept for 30 days. To preserve cumulative earned trust, up to 561 of the most recent valid, completed daily aggregates with positive results and their limited operational metadata may be retained longer while the server profile exists; other records are scheduled for deletion after 30 days. Deleting the server profile also deletes its moderation-analysis records. The aggregate may raise or lower the server's overall trust score, but it is not displayed as a separate public score. Limited randomized sampling is not comprehensive and can miss or misread context. Server operators remain responsible for required member notice, an appropriate legal basis, human moderation, and appeals; a setup choice does not authorize unlawful surveillance.

An authorized Peeksi page moderator may manually request a silent, read-only server diagnostic when investigating a service or score problem. The diagnostic runs only after that moderator presses the diagnostic button. It retrieves channel and active-thread metadata available to the bot and stores only the requesting moderator's Discord user ID, aggregate channel-access and recent-activity counts, an optional latest-activity time, processing status, and timestamps. It does not post, mention, react, create an invite, change the server, inspect message content, or retain channel or thread names or IDs. Completed and failed diagnostic request records are scheduled for deletion after 24 hours.

7. Website Data, Cookies, and Analytics

Peeksi uses an essential session cookie for Discord login, OAuth security state, request protection, rate limiting, and dashboard access. In production it is configured as Secure, HttpOnly, and SameSite=Lax. After login, the cookie lasts for 24 hours so you can stay signed in when you close and reopen your browser. Logging out ends that session and clears the cookie. Before login, the cookie lasts only for the browser session.

The public homepage and public server listing pages use Google Analytics 4 to understand visits and website performance. Google may receive device and browser information, pages viewed, approximate location derived from an IP address, and analytics identifiers, and may set or read analytics storage depending on your browser and regional settings. Peeksi does not load Google Analytics on the dashboard, search, legal, maintenance, or error pages.

Our hosting and security providers may process IP addresses, user-agent information, request times, requested URLs, and diagnostic records in ordinary web-server or security logs. Your browser also requests server artwork from Discord's content-delivery network when that artwork is displayed. You can control cookies through your browser and use Google's available analytics opt-out controls, although disabling essential storage may prevent login or dashboard features from working.

8. How We Use Information

We use information to:

• respond to searches and maintain accurate public server profiles;
• validate invites, ownership, bot presence, setup status, and trust signals;
• calculate, explain, protect, and improve server-level trust scores;
• authenticate users and provide owner and administrator dashboards;
• operate limited, server-authorized trust-and-safety analysis;
• detect abuse, fraud, score manipulation, security incidents, and service failures;
• analyze website use and improve Peeksi; and
• respond to requests, disputes, law, and enforcement needs.

We do not sell Discord server or member data, use Discord API data for third-party advertising, or use Peeksi scores to make high-impact decisions about individuals.

9. Legal Bases

Where a law requires a legal basis, we process information as necessary to provide a service you request or perform our agreement with you; for legitimate interests such as operating, securing, improving, and protecting a server-level trust service; to comply with law; and with consent where a specific optional activity legally requires it. We balance legitimate interests against the rights and reasonable expectations of affected people.

A server's /setup authorization is not automatically our legal basis for every member's personal data. The appropriate basis for moderation processing depends on the active feature, the server operator's responsibilities, applicable law, and our role in that processing.

10. When We Disclose Information

We may disclose information:

• publicly, when it is part of a public server profile, score, invite status, community review, or verified ownership claim;
• to Discord through its API and content-delivery services;
• to hosting, database, analytics, security, and other vendors that process information for us under appropriate restrictions;
• when you choose an outbound link, such as a Discord invite, DISBOARD server page, or Top.gg server page;
• to comply with law, legal process, or a valid government request, or to protect rights, safety, and service integrity; and
• in connection with a merger, acquisition, financing, reorganization, bankruptcy, or sale of all or part of the service, subject to applicable law.

Peeksi does not sell personal information or Discord API data.

11. Retention and Deletion

We keep information for as long as reasonably needed for the purposes in this policy, including to operate public profiles, preserve score integrity, resolve disputes, maintain security, comply with law, and enforce agreements. Retention differs by record:

• login sessions expire after inactivity and an absolute session limit;
• invalid saved invites are deleted when demand-driven validation finds them;
• member-count and invite-derived activity data are kept as rolling server-level snapshots;
• bot activity counts, observed duration, and their limited processing metadata are scheduled for deletion after eight days;
• recent server-level moderation-analysis aggregates and their limited operational metadata are kept for 30 days; up to 561 of the most recent valid, completed daily aggregates with positive results and their limited operational metadata may be retained longer while the server profile exists to preserve cumulative earned trust; other records are scheduled for deletion after 30 days, and deleting the server profile also deletes its moderation-analysis records;
• on-demand page-moderator diagnostic requests and their aggregate results are scheduled for deletion after 24 hours;
• active page-moderator profile and grant records are deleted when the site owner removes that access;
• listing reports and their review audit fields may remain as needed to investigate abuse, prevent repeated reports, resolve disputes, and document moderation activity;
• community review history, dispute snapshots and decisions, and limited account activity records may remain for moderation and abuse prevention; account-and-listing removal records are retained to prevent a user from reviewing the same listing again after moderator removal;
• server catalog, ownership, claim, setup, audit, and profile records may remain until corrected, deleted on an eligible request, or no longer needed; and
• hosting, security, backup, and legal records may follow a provider's or legally required retention period.

Removing the bot or opting out immediately stops future message sampling and activity counting but does not automatically delete the public profile or its historical records. Retained moderation-analysis records do not provide positive score credit while the server has opted out or the bot is removed. Any retained moderation-analysis aggregate or bot activity count remains subject to the retention and deletion rules above. To request access, correction, unclaiming, delisting, or eligible deletion, contact us as described below. We may verify identity and retain limited information when required for law, safety, fraud prevention, dispute resolution, or proof that a request was honored.

12. Security and International Processing

We use administrative, technical, and organizational safeguards appropriate to the information and service, including restricted access, secure session settings, request-verification controls, prepared database operations, transport encryption where supported, and security headers. No internet service is completely secure, and we cannot guarantee that information will never be lost, altered, or accessed improperly.

Peeksi, Discord, Google, and our infrastructure providers may process information in countries other than yours. Where required, we rely on a recognized transfer mechanism or another lawful basis for international processing.

13. Your Choices and Privacy Rights

Depending on where you live, you may have rights to request access, correction, deletion, restriction, objection, or portability; withdraw consent where processing relies on consent; and complain to a data-protection authority. You may also:

• log out to end the current Peeksi session;
• decline or opt out of consent-gated bot verification through /setup;
• remove the bot from a server through Discord;
• ask us to correct or remove an inaccurate public ownership claim or server profile; and
• control analytics storage through your browser or Google's opt-out tools.

Send a request to [email protected]. Include enough information to identify the relevant Discord account or server, but do not email a password or bot token. We may verify your identity and authority before acting. Rights can be subject to exceptions under applicable law.

14. Children's Privacy

Peeksi is not directed to children under 13 or the higher minimum age required to use online services in their country. Users must also meet Discord's age requirements. If you believe a child provided personal information to Peeksi contrary to these requirements, contact us so we can review and take appropriate action.

15. Changes to This Policy

We may update this policy when our services, technology, providers, or legal obligations change. We will post the revised policy and update the date above. For a material change, we may also provide notice through the website, dashboard, bot, or setup flow. We will request a new authorization before materially different bot processing where required.

16. Contact Us

Privacy questions, rights requests, deletion requests, and concerns may be sent to: