1. Share only what the project needs
Before sharing a private repository, customer dataset or infrastructure access, contact us to agree the scope and any confidentiality requirements. Use sample or anonymized data wherever possible. An NDA and project-specific data handling terms can be discussed before discovery.
2. Agree access and handover responsibilities
Use separate project accounts and limited permissions where the provider supports them. Agree who owns the hosting, domain, repository and third-party subscriptions in the project scope. At handover, review collaborators, revoke temporary access and rotate credentials that were shared during delivery. Never send passwords, payment card details or secret keys through a public enquiry form.
3. Report a suspected vulnerability
Email contact@ubaiddev.in with the subject “Security report” and include the affected public URL, a description of the issue and the minimum steps needed to reproduce it. Use a test account and redact personal information, tokens and credentials from screenshots. Ask us for an appropriate transfer method before sending sensitive evidence.
4. Keep investigation safe and limited
Please do not access another person’s data, change or delete records, attempt to persist access, run denial-of-service tests or use social engineering. Stop testing if you encounter private information and tell us what happened without downloading or sharing it. This reporting channel does not authorize intrusive testing or offer a paid bug bounty.
5. Review and follow-up
We assess reports according to their impact and may ask for clarification. Please allow us to investigate and coordinate any public disclosure with us. Response times depend on the issue; this page does not establish a contractual response or uptime guarantee. Project-specific security obligations should be set out in the signed agreement.