RyphexGuard
Marketplaceseparate Get started
RYPHEXGUARD TRUST CENTER

Trust should be checkable,
not just claimed.

This page separates what RyphexGuard can prove today from what is still a future goal. Review permissions, data handling, operational status, product history, Marketplace separation and external-proof status before connecting a server.

Review Discord permissionsReport a security issue
01

Evidence you can inspect now

These are public first-party sources, not badges invented for the homepage.

Service statusLive application checks and published incident updates
→
Public changelogRelease history showing ongoing product work
→
OAuth permission referenceWhat each Discord scope is for and what it cannot access
→
Privacy & deletionPublic data-handling and account-deletion rules
→
02

Who operates the product

RyphexGuard does not fabricate founder history or a company registration that does not exist.

RyphexGuard
PRODUCTRyphexGuardA Ryphex project · launched 2026

A public individual/operator or registered company identity has not been configured on this deployment. RyphexGuard shows this honestly instead of inventing one. The operator can add verified public business details later through deployment settings.

03

Discord access, in plain language

The sensitive part of a Discord recovery product should not be hidden behind “Connect” buttons.

AccessWhy it existsImportant limit
identifyRead Discord user ID, username and avatar for verification.Does not expose a Discord password.
guilds.joinAdd an eligible previously-authorized member to a target server during recovery/delivery.Depends on valid authorization and Discord API rules.
emailUsed only in workflows that actually request/need a contact email.Not a Discord DM permission.
Manage RolesCore bot permission used to assign the configured verification role.Administrator is not required for this core role flow.
Feature-specific permissionsTools such as AI server building can need permissions to create/manage Discord structures.Only grant them when using that feature.
RyphexGuard never asks for your Discord account password.

Discord authentication happens on Discord. Review the full scope reference before authorizing.

Full permissions reference →
04

Data lifecycle

What can be stored, what customers can see, and how deletion is handled.

Data used by enabled workflows

  • Discord IDs, usernames and avatars
  • Server, role and verification records
  • Backup metadata and authorized recovery records
  • Marketplace orders, payment references and seller settlement records
  • Support, security and account activity records

Customer-facing privacy controls

  • Customer dashboards do not expose raw OAuth secrets
  • Downloaded backup data excludes recovery secrets
  • IP/location information is not presented as a customer member-tracking feature
  • Account deletion is available through account controls/support
  • Secrets should never be pasted into support tickets
05

Current security controls

Product controls that exist today, without pretending they equal an external certification.

Server-side secret handling

Bot tokens and private keys are intended to remain server-side and encrypted where the product stores credentials.

Implemented

TOTP two-factor authentication

RyphexGuard-managed accounts can enable authenticator-based TOTP with recovery codes.

Available

Server-scoped team permissions

Owners can limit collaborator access to selected servers and product areas.

Available

Activity & support records

Important product actions, support requests and marketplace states can be recorded for troubleshooting.

Implemented

These controls are product features. They are not a SOC 2, ISO 27001, penetration-test, or other third-party certification.

06

Marketplace is separated from core recovery

Buying/selling member delivery has a different risk profile from server verification and backup.

Core protection

Verification, backups, server ownership checks and recovery documentation live in the core RyphexGuard product.

SEPARATE FROM

Marketplace

Listings, buyers, seller earnings, LTC/card payments, disputes and delivery rules have their own policies and safety page.

Read Marketplace safety & limitations →
07

Operational status & incident history

Current status comes from this application instance. Published incidents are maintained separately and do not pretend to be an external SLA monitor.

Current checks operationalLast page check: 8/24/2026, 11:47:15 AM
Open full status page →
No public incident entries have been published yet.That is not presented as proof of perfect historical uptime. The public incident log begins when incidents are actually published.
08

Independent / third-party proof

This section intentionally shows “not published yet” until a real external source exists.

DISCORD APP DIRECTORY

Not published yet

RyphexGuard will not show a Discord Directory badge until a real listing exists.

SECURITY ASSESSMENT

No independent audit published

No audit badge or penetration-test claim is displayed without an actual report.

INDEPENDENT REVIEWS

No review profile linked yet

RyphexGuard does not fabricate testimonials or buy fake reviews to fill this space.

RECOVERY CASE STUDY

No customer case study published yet

A recovery story will only be published after a real incident and with the customer’s permission. No invented server logos or testimonials.

SECURITY & PRIVACY CONTACT

Found a security or privacy issue?

Use responsible disclosure. Do not include passwords, bot tokens, private API keys or unrelated customer data.

Disclosure instructionsGeneral support

RyphexGuard launched in 2026. This Trust Center is designed to distinguish implemented controls from future goals and independent evidence. Missing external proof is shown as missing rather than replaced with fake badges or unsupported claims.