At a glance
- Private API requests are authenticated and saved diagrams are checked against their owner.
- Password and session credentials are stored as hashes; production uses secure cookies and HTTPS.
- Report vulnerabilities privately to support@tingraph.com with the subject Security report.
This summary helps you navigate. Read the full policy below for the details and qualifications.
Implemented safeguards
The production setup uses HTTPS, HttpOnly secure session cookies, hashed session tokens and Argon2id password hashes. Account mutations require an allowed origin and session-bound CSRF token. Database credentials are separated between migration ownership and restricted application access.
Saved-diagram queries check the authenticated owner's account. Google sign-in validates OIDC state, browser binding, PKCE, nonce and verified identity. Payment activation relies on verified provider status, not a browser return URL. These controls reduce risk and are not a claim of perfect security or a certification.
Protect your account and content
Use a strong unique passphrase or a protected Google account. Do not share credentials, verification/reset links or payment-provider secrets. Sign out on shared devices and keep local exports of important work.
Do not upload secrets or confidential material to AI. Treat profile-image URLs as publicly accessible. Check exports for personal information before sharing them.
Report a vulnerability
Email support@tingraph.com with the subject Security report. Include affected routes/features, a minimal reproduction, the security impact and a safe way to contact you. Redact passwords, tokens and other users' personal data.
Use only accounts and material you own or are authorized to test. Stop once you have enough evidence; do not access, modify or delete other people's data, persist access, cause service disruption or exploit the issue further. Do not publish exploitable details before giving us a reasonable opportunity to investigate.
This page is a private reporting channel, not a paid bug-bounty offer, blanket testing authorization or legal immunity. We will review good-faith reports and coordinate an appropriate response, but do not promise a fixed response time or reward.
Suspected account or payment compromise
If your account may be compromised, change the password where applicable, protect your Google account and contact support from your account email. Include relevant timestamps and order IDs, without sending full payment credentials.
We will investigate within applicable duties and make legally required incident notifications. The Privacy Policy describes data processing and contact rights.