Community verificationMEMBER VERIFICATION
The people are the point.
Keep community-specific authorizations with a searchable member list. Members choose to opt in and can withdraw at any time.
COMMUNITY RECOVERY, WITH CONSENT
Keep your
community
within reach.
A server can disappear. The connections you built don't have to. Verify your members, save your structure, and prepare a clear path back.
Encrypted authorization Member-controlled consent
COMMUNITY OVERVIEW
Your people.
Your recovery plan.
Member authorizations
A clear view of who has opted in.
Ccinder Active consent
Oorin Active consent
Aavena Active consent
Recovery enabledPrivate workspace
Prepared before you need it.Consent and structure stay together.
Interactive illustration · No live Discord requests
Built for Discord communitiesConsent before recoveryScoped access for your team
01 / PREPAREYour recovery plan.
Your recovery plan.
Already in place.
Protect the people and structure that make your server feel like home.
Community verificationStructure backupSaved
# welcome
# community-chat
community roles
permission overwrites
Daily or weekly.
One less thing to remember.
One less thing to remember.
SERVER BACKUPS
Keep the shape of your server.
Schedule private role and channel snapshots. Add or reuse the structure you need when you rebuild.
02 / STAY IN CONTROLA calm place
A calm place
to handle the unexpected.
Track recoveries, review the operation log, and give your team the access they need. Every important change leaves a record.
Explore the workflowRecover with a clear destinationChoose a connected server and confirm before sending live requests.
Give each teammate a defined roleScope members, settings, backups and recoveries to selected servers.
Keep authorization privateEncrypted credentials stay out of pages, exports and operation logs.
03 / GET STARTEDA few steps today.
A few steps today.
A plan for tomorrow.
Use your own Discord application to keep your community connected.
- 01
Connect your bot
Create or connect your Discord application and invite it to your server.
- 02
Let members opt in
Publish your verification message. Members authorize recovery with clear consent.
- 03
Save your structure
Create a snapshot or set a schedule. Review your backup whenever you need it.
- 04
Recover when you're ready
Choose the destination, confirm the action, and follow the saved progress.
THE DETAILSGood questions.
Good questions.
Clear answers.
Know what recovery can do
before you need it.
Members explicitly authorize your Discord application for a named community. When you need a replacement server, start a recovery from that community and select a server connected to the same bot.
Recovery requires active authorization and consent. Revoked permissions, bans, server limits and Discord enforcement can prevent a join. Guardcord records the result of each request.
Supported category, text and voice channels, non-managed roles, and role permission overwrites. Messages, files, threads, forums, emojis and exact role ordering are excluded. Channels with member-specific permissions require manual recreation.
Yes. Members can withdraw community consent here or revoke the application under Discord's Authorized Apps. Leaving a community also prevents recovery from that community.
Bot owners grant registered teammates specific permissions and allowed servers. Permissions apply to both the source and destination of a recovery.
Bot credentials and member authorization tokens are encrypted in the service's database. They are never displayed in the dashboard or included in structure downloads.
KEEP WHAT YOU BUILTGive your community
Sign in to get startedGive your community
a way back.
Start with verification. Build your recovery plan from there.