Security, privacy and reliability at Pulcenow
This page is maintained by Pulcenow to answer common security and privacy questions about our platform. It describes controls currently enabled in the application. It is editable content owned by Pulcenow and is not an independent certification or third-party audit.
Our core pillars
Security
Defense-in-depth controls across authentication, data, and infrastructure.
Privacy
Your data is yours. We collect only what the product needs to operate.
Reliability
Backups, monitoring, and disciplined change management keep the platform stable.
Transparency
Clear documentation of the controls we run and the practices we follow.
Security controls
The technical safeguards we run today across access, data, and the surfaces users interact with.
Access & authentication
Every interaction requires authentication. Sessions are issued as short-lived tokens that expire automatically. Roles (admin, manager, member) are stored in a dedicated, server-controlled table and cannot be tampered with from the browser.
Project isolation
Data is partitioned per project. Row-level rules verify on every request that the caller belongs to the project the data belongs to.
Encryption in transit
All traffic between your browser and Pulcenow is encrypted over HTTPS/TLS. Plain-text connections are not accepted.
Encryption at rest
Stored data is encrypted at rest by the underlying infrastructure. Uploaded files live in private buckets and are served only through short-lived signed URLs.
Audit & monitoring
Administrative writes, financial data access, role changes and destructive actions are recorded in internal audit logs. Authentication events are monitored for abnormal patterns.
Input validation & abuse prevention
Input is validated and sanitized on both client and server. Rich-text and SVG content are sanitized to prevent script injection. Sensitive endpoints are rate-limited.
Privacy & data handling
What we collect, why we collect it, how long we keep it, and the rights you have over it.
What we collect
Account data (name, email, role), the projects and records you create inside the app, and operational metadata such as timestamps of actions you perform.
How it is used
Strictly to operate Pulcenow: authenticating you, scoping access to your projects, attributing actions in audit logs, and delivering the features you use. Your data is not sold.
How long it is kept
Project and account data are retained while the account and related projects remain active. Items deleted through the app are removed from the live system; routine backups may hold copies for a limited rotation period.
Your rights
You can request an export of your account data or the deletion of your account by emailing the contact below from the address associated with your account.
Keeping the platform running
Operational practices that protect availability and the integrity of your data over time.
Backups & recovery
Production data is backed up on a regular schedule with retention windows designed to support point-in-time recovery.
Change management
Code changes go through review and automated checks before reaching production. Database changes are tracked as versioned migrations.
Monitoring
The platform is monitored for errors, performance regressions, and abnormal authentication activity, with alerts routed to the engineering team.
Frequently asked questions
Found something? Tell us first.
If you believe you have found a security vulnerability or have a privacy question, please contact us before any public disclosure. We aim to acknowledge reports within a reasonable timeframe.