Privacy Policy
How Parsepad handles data, browser storage, and operational signals in practical terms.
- Browser-firstcommon utility work stays close to the task
- Minimal logsoperational signals support reliability and troubleshooting
- Shared responsibilityusers should avoid sending sensitive payloads unless approved
At a glance
A four-line summary of this policy.
-
Core purpose
Tool processing
Inputs are processed to produce the requested output. That is the primary purpose of the service.
-
Operational signals
Minimal logs
Request timing and error signals may be retained to keep the platform stable and debuggable.
-
User responsibility
Avoid sensitive data
Teams should avoid sending secrets or regulated data unless they have explicitly approved that workflow.
-
Browser storage
Preferences stay local
Interface settings and session data may be stored in your browser to improve repeat visits.
Data usage
Tool inputs are processed to produce outputs. Minimal operational data supports reliability.
When you run a tool, Parsepad processes the input needed to produce the output you requested. That is the primary purpose of the service.
We also keep minimal operational data like request timing and error signals so we can keep the service stable, debug failures, and improve reliability.
-
Tool processing
Inputs are handled to produce the requested result
The primary purpose of the service is to take the data you submit and return the output the tool is designed to generate.
-
Operational signals
Reliability data helps keep the service stable
Request timing, health indicators, and error signals may be used for troubleshooting, support, and reliability work.
-
Browser storage
Preferences may stay in your browser
Useful local settings such as interface preferences or continuity helpers can be stored in the browser to improve repeat visits.
What to avoid submitting
Do not paste secrets, private keys, regulated records, or sensitive personal data unless your team has explicitly approved that workflow.
Please do not paste secrets, private keys, regulated records, or sensitive personal data unless your team has explicitly approved that workflow.
-
Use samples
Prefer synthetic fixtures
If you only need a structure or failure shape, sample data is safer than real customer content.
-
Redact first
Strip secrets and identifiers
Remove tokens, private keys, email addresses, and personal identifiers before sharing anything with a public tool.
-
Minimize scope
Share the smallest useful excerpt
A short payload fragment that still reproduces the issue is usually safer and easier to reason about than a full dataset.
Common privacy questions
Practical questions most teams need answered before they decide whether a public browser workflow is appropriate.
-
Sensitive data
Should I paste production data here?
Read full answer -
Operational logs
What is kept for reliability?
Read full answer -
Direct review
When should I contact the team?
Read full answer
Sensitive data Should I paste production data here?
Only if your team has explicitly approved that workflow. The safer default is a redacted or synthetic sample that still reproduces the issue.
Operational logs What is kept for reliability?
Minimal operational signals such as request timing, runtime health, and error data may be retained so the service can be monitored and debugged.
Direct review When should I contact the team?
Use direct contact when a workflow needs privacy review, legal context, or a human answer that the general policy page cannot settle by itself.
Retention and protection
We keep data only as long as needed for operations, reliability, and security. We do not keep everything forever.
We keep data only as long as needed for operations, reliability, and security. We do not keep everything forever.
Access to platform systems is restricted and monitored so we can reduce misuse risk.
Cookies and browser storage
We use cookies and browser storage for session handling, preferences, and useful browsing continuity.
We use cookies and browser storage for practical platform behavior like session handling, preferences, and useful browsing continuity.
Details are in the Cookie Policy.
Your responsibilities
Teams decide what is safe to process and how outputs are validated.
Parsepad can make common workflows easier, but teams still need to decide what is safe to process and how outputs are validated.
-
Before input
Decide whether the data is safe to process
Teams are responsible for deciding whether a payload is appropriate for a public browser workflow before it is pasted into a tool.
-
Before sharing
Limit what other people need to see
Use redacted or sample data whenever possible so debugging and review do not depend on exposing real customer content.
-
Before shipping
Validate the result in your own delivery flow
Parsepad can speed up routine work, but teams still need their own tests, CI, and policy checks before production use.
Reporting a security issue
Report vulnerabilities privately through a GitHub Security Advisory or the contact form. We acknowledge within 5 business days and coordinate the fix before public disclosure.
If you believe you have found a security issue in Parsepad, please report it privately so the team can investigate and ship a fix before it is public.
Two routes are supported. The preferred route is a private GitHub Security Advisory, which keeps the report scoped to repository maintainers. As a fallback, the contact form accepts Security report as a subject and lands the message in the admin inbox for manual triage.
The full policy — scope, what to include, what to leave out, response timelines, and credit — lives in SECURITY.md at the repository root.
Policy updates
We publish changes here. Check back periodically or contact us with questions.
If our data handling practices materially change, this page will be updated with a new version date and a brief summary of what changed.
Still unsure?
-
Cookies
Cookie policy
See how Parsepad uses browser storage, sessions, and preference cookies.
Read cookies -
Terms
Terms of use
Understand the legal framework, acceptable use, and liability boundaries.
Read terms -
Need a human
Contact us
Reach out when a specific workflow needs human review or legal clarification.
Contact us