Overview
When you use our services, you’re trusting us with your information. We understand this is a big responsibility and work hard to protect your information and put you in control.
What is Suloro? Suloro is a privacy-first platform providing Single Sign-On (SSO), developer OAuth 2.0 with PKCE authorization, end-to-end data encryption, Suloro Ads across apps, strict adherence to the DPDP Act and international privacy laws, and zero cross-site behavioral surveillance tracking.
- Zero Data Sales: Personal information is never sold, leased, or monetized with advertising brokers.
- Encrypted Architecture: Sensitive records, transit channels, and session data are fully encrypted at rest and in transit.
- Least-Privilege Scopes: Third-party applications only receive scopes explicitly approved by the user.
- Immediate Revocation: Password updates automatically terminate all active sessions across all devices.
Privacy Policy
Explains what information we collect and why, how we use it, and how to review and update it.
Terms of Service
Describes the rules you agree to when using our services.
Our Privacy and Security Principles
Our foundational commitment to zero advertising tracking, zero data sales, client-side encryption, and strict least-privilege authorization across every product.
Frequently Asked Questions & Knowledge Base
Explore in-depth answers regarding account management, cryptographic tokens, OAuth 2.0 PKCE, session isolation, and account recovery.
Frequently Asked Questions Highlights
Quick answers to common questions about accounts, security, and developer integration.
What is a Suloro Account?
A single, secure identity for accessing Suloro productivity apps and authorized third-party services with built-in cryptographic protection.
Learn more in FAQDoes Suloro sell or share my data?
Never. We enforce a zero-ad-tracking and zero-data-sales policy. Your profile is never monetized or exposed to ad brokers.
Read Privacy Rights in FAQHow are passwords protected?
Suloro uses memory-hard cryptographic hashing resistant to GPU brute-forcing. Passwords are never saved in plaintext or logged.
Read Security details in FAQHow do developers use OAuth 2.0 with PKCE?
Developers can register client applications in the Developer Console and implement RFC 7636 PKCE (S256) for secure user authentication.
Read Developer specs in FAQ