Mardly
JournalAboutSquadsProduct
Open MardlyJoin
☰
Trust & Safety

Security is part of the product.

Mardly is built to give people places to connect without treating safety as an afterthought. This page outlines the principles behind account security, community protection and responsible reporting.

Platform safetyAccount securityCommunity standards
Security & SafetyHelp CenterFAQContactPrivacyTerms
⌁
A safer Mardly starts with better defaults.

The policies below are launch-era placeholder content and should be reviewed against Mardly's final operational, moderation and legal processes before publication.

Account security

Protecting an account starts with strong credentials, sensible session handling and clear recovery paths. Mardly should never ask you to share your password with another person, moderator or third-party service.

  • Use a unique password for your Mardly account.
  • Keep your recovery information current where available.
  • Sign out of devices you no longer control.
  • Report suspicious login activity as soon as you notice it.

Community safety

Squads are communities, and communities need boundaries. Mardly's safety approach is intended to reduce harassment, threats, spam, impersonation, abusive behaviour and other conduct that makes people unsafe or unable to participate.

Report problems

If you encounter content or behaviour that violates Mardly's rules, use the reporting tools available in the product. Reports should include enough context for the moderation team to understand what happened.

Protect your information

Never publish passwords, authentication codes, financial credentials, private addresses or other sensitive information in a public Squad or conversation.

Platform security

Mardly's engineering team should continuously review authentication, authorization, data access, dependency updates, logging and infrastructure controls. Security work is an ongoing process rather than a one-time certification.

Security reports.
If you believe you have discovered a security vulnerability, use Mardly's official support/contact channel rather than publicly disclosing exploitable details first. A dedicated security-reporting address can be added here when the operational mailbox is finalized.

Safety principles

Protect people from abuse and harassmentCore principle
Protect accounts and authenticationCore principle
Give communities clear rules and reporting pathsCore principle
Improve safety controls as Mardly growsOngoing
© Mardly SocialSafety · Privacy · Terms · Contact