Trust has to be specific.
Clear boundaries, inspectable permissions and a private route to report a concern.
Updated · NayakWhat this page describes
This page concerns the marketing website. It is not an independent security assessment, audit certificate or guarantee. Scout’s application security, account isolation, data storage, connected-account permissions and backups require separate product verification.
The marketing demos do not connect to your mailbox or send messages. Do not enter credentials, confidential customer data or real prospect lists into them.
Website controls
The website configuration sets a Content Security Policy, blocks embedding in frames, requests MIME-type checking and limits cross-site referrer information. Optional analytics and advertising loading is controlled by consent and deployment configuration.
Configuration is not proof that a live host serves every header correctly. Production HTTPS, effective headers, hosting access, logging, incident response and dependency updates must be checked in the deployed environment. We do not claim SOC 2, ISO 27001 certification, a penetration-test pass or that all data stays in India.
Early-access submissions
The form checks input lengths, email format and explicit access-email consent. Same-origin checks, a hidden spam field and submission limits reduce common abuse. Production signup success requires a durable database write; the service returns an error when storage is unavailable.
Personal signup information is not placed in URLs or advertising events. Database access belongs to authorised operators. These measures do not amount to independent certification or eliminate all abuse.
Before connecting a business system
In Scout, inspect the account being connected and the permissions requested by the provider. Confirm the product policy explains what is accessed, which service providers process it and how to disconnect or delete it. A tool logo on this website is not a permission grant or evidence of a verified connection.
Start by reviewing Scout’s work. As you come to trust him, he takes more on. Actual permissions and sending controls must be visible in the product.
Responsible disclosure
Privately email shivansh@nayakandco.in with “Security report”, the affected location, steps to reproduce and impact. Provide the minimum evidence needed and redact personal information.
Do not attempt persistence, data extraction, denial of service, social engineering or testing against someone else’s account. If you encounter private data accidentally, stop and report its location without copying more. No paid bounty or legal safe harbour is offered by this notice.
Security incidents and privacy
Security concerns need investigation and proportionate action. Applicable reporting obligations, including CERT-In directions where relevant, require operational arrangements beyond this page. We make no assertion that publishing this notice alone establishes compliance.
For information requests or a concern about personal data, see Privacy or contact us.