Version 1Published Last updated 8 November 2026

Vulnerability Disclosure Policy

How to report a security vulnerability in Pagelove, which systems you may test, and what you can expect from us.

1Our commitment

Pagelove welcomes good-faith security research that helps protect our platform and the people who use it. This policy explains which systems you may test, how to report a vulnerability, and what you can expect from us.

2Report a vulnerability

Email security@pagelove.com with the subject Security report: [short description]. Report suspected vulnerabilities promptly; you do not need a complete exploit or a severity score. You may report anonymously, although we need a reply address to discuss the issue and provide updates.

Please include, where available:

  • The affected hostname, URL or feature, and when you observed the issue, including the time zone.
  • A description of the issue, its potential impact, and any access or account permissions needed to reproduce it.
  • Clear reproduction steps using accounts and test data you control.
  • Minimal supporting evidence, such as redacted requests, screenshots or a small proof of concept.
  • Whether you encountered anyone else’s data, observed active exploitation, or have already shared the finding.

Do not include passwords, API keys, session tokens or customer data in ordinary email. If evidence is sensitive, send a summary first and ask us to arrange a secure transfer method. Do not post an unresolved report in a public issue tracker.

3Scope

This policy covers the following Pagelove-operated services, subject to the testing rules below:

ServicePermitted scope
pagelove.com and www.pagelove.comPagelove’s public website.
console.pagelove.comPagelove’s account and site management console, using your own test accounts.
Sites under *.onpagelove.com that you create and controlPagelove’s hosting and platform behavior, using your own test sites and synthetic data only.

We particularly welcome reports of authentication or authorization failures, unintended access between tenants, exposed credentials, and failures to enforce platform permissions or document constraints. To test isolation between accounts or sites, create and control both sides of the test.

Other customers’ sites, content, accounts and data are outside the authorization granted by this policy. A public URL or a Pagelove hostname does not grant permission to test someone else’s application. Third-party services, integrations and infrastructure are also excluded, even if linked from an in-scope service. Other hostnames, custom domains and systems are not included unless we authorize them separately in writing.

If you are unsure whether a target or method is covered, contact security@pagelove.com before testing. You may still report an issue encountered accidentally outside scope; receiving a report does not authorize further testing.

4Testing rules

Conduct research to identify and help correct security flaws. Keep tests limited, reversible and designed to avoid harm.

  • Use accounts, sites and data you control. Do not use another person’s credentials or access their account.
  • Use the minimum activity needed to demonstrate the issue. Stop once you have enough evidence; do not expand access to show a larger impact.
  • Keep automated testing low volume. Respect rate limits and stop if you observe errors, slowdowns or other effects on service availability.
  • Do not perform denial-of-service, stress or load testing; send spam; conduct credential stuffing or password guessing; or attempt social engineering, phishing or physical intrusion.
  • Do not install malware, establish persistence, move into other systems, or change or delete data belonging to others. Do not trigger charges or communications to other users.
  • If you unexpectedly encounter personal information, secrets or other confidential data, stop immediately and report the exposure. Do not browse further, download additional records or share the data. Retain only the minimum redacted evidence needed for the report and arrange secure handling and deletion with us.

A report that lacks demonstrated impact may still be useful. Explain the plausible security consequence rather than running more intrusive tests to prove it.

5Safe harbor for good faith research

We consider research on in-scope systems authorized when you make a good-faith effort to follow this policy. For that research, Pagelove will not initiate or recommend legal action against you. We waive restrictions in our own terms that would otherwise prohibit the research, solely to the extent needed for activity covered by this policy.

An accidental mistake does not automatically remove this protection if you stop, report it promptly and cooperate to limit harm. If you are uncertain about an activity, pause and ask us before continuing.

We can make these commitments only for Pagelove and rights we control. We cannot authorize testing of third-party systems or bind customers, other service providers or public authorities. If a third party takes action concerning research covered by this policy, we will make our authorization known.

Policy changes apply prospectively and do not withdraw protection for research covered when it occurred.

6How we handle reports

If you provide a reply address, we aim to:

StepTarget
Acknowledge receiptWithin 3 business days.
Provide an initial assessment or request for more informationWithin 10 business days.
Update you while an accepted issue remains openAt least every 30 calendar days, and when there is a material change.

We prioritize reports by potential harm, likelihood of exploitation and affected users. These are communication targets, not guaranteed resolution deadlines. We will explain significant delays and coordinate verification of a fix where appropriate. If you have not received an acknowledgment within 3 business days, please follow up on the same email thread.

We use reports to investigate, mitigate and remediate vulnerabilities. Access is limited to people who need the information, including affected providers when coordination is necessary. We will not publicly identify you without your permission, and will not share your identity outside the response team without your consent unless legally required.

7Coordinated public disclosure

Please allow us time to investigate and protect users before publishing exploit details. We propose coordinating disclosure within 90 calendar days of your initial report, or sooner when a fix or effective mitigation is available. We will discuss a publication date with you and request any extension with a reason and a specific end date.

This is not an indefinite confidentiality requirement. If we cannot agree on timing, please give us advance notice of your intended publication so we can prepare advice for users. A disagreement about timing alone does not remove safe-harbor protection for otherwise covered research. Never publish customer data, credentials or other confidential information obtained during testing.

8Recognition and rewards

With your permission, we may acknowledge your contribution publicly using your preferred name or alias. Anonymous reporting is welcome.

This is a vulnerability disclosure program, not a paid bug bounty program. We do not promise payment or other rewards for reports.