Webopsy Full report

Draft. Built from a single check on November 22, 2026. It becomes a live page, re-checked every day and after every deploy, when payflip.xyz is under Watch.

Security and privacy, independently checked

payflip.xyz

Last checked
November 22, 2026
Monitoring
Not monitored
Controls verified
6 of 9
Clean Bill of Health
WO-2026-0036, valid to February 20, 2027

Controls

What a check of the live site, from outside, can establish. Each row is re-evaluated on every check.

Encryption in transitVerifiedHTTPS on every request, with HSTS telling browsers never to fall back to HTTP.
Browser security headersVerifiedContent-Security-Policy, HSTS, clickjacking and MIME-sniffing protections are set.
No server credentials in client codeVerifiedThe page and 6 script bundles were searched for server-side keys (payment, cloud, AI, source control); none found.
Privacy policyVerifiedPublished, and contains the disclosures GDPR, CCPA and PIPEDA expect.
Policy matches what the site runsPartlyNo trackers fired to compare against, or the policy could not be read.
No tracking before consentVerifiedNo analytics or advertising trackers run on load.
Terms of serviceVerifiedPublished.
Vulnerability disclosure contactPartlyNo /.well-known/security.txt; researchers have no published way to report a problem.
Accessibility (automated WCAG 2.2 checks)PartlyNo critical failures; some serious or moderate rules fail.

Sub-processors seen on the site

Third-party services a real browser saw the site load on November 22, 2026. A vendor list taken from the live site, not from a form.

None seen.

Security questionnaire answers

The questions vendor reviews ask that outside evidence can answer. Copy them into a questionnaire, or send this page.

Is data encrypted in transit?
Yes. HTTPS on every request, with HSTS telling browsers never to fall back to HTTP.
Do you use security headers such as Content-Security-Policy and HSTS?
Yes. Content-Security-Policy, HSTS, clickjacking and MIME-sniffing protections are set.
Are secrets and API keys kept out of client-side code?
Yes. The page and 6 script bundles were searched for server-side keys (payment, cloud, AI, source control); none found.
Do you have a published privacy policy?
Yes. Published, and contains the disclosures GDPR, CCPA and PIPEDA expect.
Which third parties (sub-processors) receive data from your website?
None were seen loading on the live site.
Do you obtain consent before setting non-essential cookies?
Yes. No analytics or advertising trackers run on load.
Do you have a process for receiving vulnerability reports?
Partly. No /.well-known/security.txt; researchers have no published way to report a problem.
Do you monitor your public-facing systems for security and privacy regressions?
Not continuously. This page reflects a single independent check.

Record of checks

Every independent check of payflip.xyz, newest first. Nothing is removed from this list.

CheckedScoreOpen findingsTrackers before consent
Nov 22, 2026, 11:59 a.m.963None
Nov 15, 2026, 11:45 a.m.963None
Nov 8, 2026, 11:13 a.m.962None
Oct 31, 2026, 10:23 p.m.981None
Oct 24, 2026, 1:59 a.m.981None
Oct 16, 2026, 10:45 a.m.982None
Oct 9, 2026, 7:28 a.m.982None
Oct 3, 2026, 8:23 p.m.982–
Oct 2, 2026, 4:21 a.m.982–
Oct 2, 2026, 1:20 a.m.982–
Sep 29, 2026, 11:46 p.m.982–

What this page does not cover.

It is an independent check of the public site, not an audit and not SOC 2. These cannot be seen from outside, so they are not answered here; ask payflip.xyz directly:

Checks are run by Webopsy, which payflip.xyz does not control. What each check verifies. Machine-readable: JSON.