Rulewisp / privacy
Your information should have a clear place in the workflow.
This notice explains what Rulewisp collects, why it uses the information, and the choices available to people who use or contact the service.
This notice applies to the Rulewisp website and workspace. It describes current product behavior; it does not promise a particular legal or compliance outcome.
Rulewisp is a single-default-workspace compliance product. The details below explain what information enters that workflow, how it is used, and how to ask a privacy question.
The short version
Useful records, stated plainly.
The current app has no published retention schedule or self-service privacy-request flow. Contact Rulewisp when you need a specific answer about your information.
01 / Information
Information we collect
When you create or use an account, Rulewisp receives account identity and sign-in data needed to operate authenticated access. Authenticated sessions use cookies.
If you use the contact form, Rulewisp stores the name, email address, message, and submission timestamp you provide. The form is intended for product questions, including privacy questions.
Workspace records can include an organization profile, privacy changes, policy metadata, status, tags, review dates, tasks, mappings, audit activity, and evidence metadata. Policy and evidence uploads may also be stored, along with extracted text when extraction succeeds.
When the optional deployment-injected visitor beacon is enabled, it creates a random visitor ID in browser localStorage and sends a page-load pixel to the configured Polsia analytics endpoint. This optional analytics behavior is not advertising or targeted advertising.
02 / Purpose
How we use information
Rulewisp uses information to operate authentication and the workspace; surface privacy and regulatory changes; manage policies, tasks, evidence, mappings, and audit history; process contact requests; maintain security; and diagnose service issues. When optional analytics is enabled, it also helps us understand site usage.
03 / Retention
Retention
Information is retained while it is needed to provide and operate the service, maintain workspace history, respond to requests, and meet applicable operational or legal needs. Contact submissions, account and workspace records, uploaded files, extracted text, and analytics identifiers may have different retention needs.
The current app does not publish fixed retention periods or provide an automatic deletion schedule or self-service deletion flow. Contact Rulewisp to ask about a particular record or submit a privacy request.
04 / Service providers
Sharing and service providers
Rulewisp may disclose information to infrastructure and service providers needed for the database, authentication, configured file storage, and optional Polsia analytics. Providers receive information needed for their role. Information may also be disclosed when needed for safety, legal process, or a business transition. This notice does not claim that Rulewisp sells information or publish a fixed vendor list or legal framework for every provider.
05 / Safeguards
Security practices
Rulewisp uses signed-in dashboard access, server-side administrator checks on protected operations, HTTPS/TLS deployment, a nonce-based strict content-security policy, security headers, and a permissions policy.
These safeguards reduce risk but are not an absolute security guarantee. This notice does not claim encryption at rest, customer-managed keys, certifications, or formal compliance attestations.
06 / Your choices
Your rights and choices
Depending on applicable law, you may have rights to access, correct, delete, restrict or object to certain uses of information, and receive a portable copy. These rights are not universal or automatic in every situation.
You can contact Rulewisp with a privacy question or request. We may need to verify identity or account ownership before responding. The current app has no self-service privacy-request workflow, and this notice does not promise a specific response deadline or outcome.
07 / Location
International transfers
Hosted infrastructure and service providers may process information outside your country. The current app does not establish a single processing region or publish a specific transfer mechanism or residency guarantee. Contact Rulewisp for current transfer details.
Privacy questions
Need a more specific answer?
Contact Rulewisp at rulewisp-2@rulewisp.com with a privacy question or request. Please share only the information needed for us to understand and verify your request.