Trust
Security and compliance
Last updated: November 16, 2026
In brief. AvklarePlan separates every workspace's data in the database itself, records who changed what in a plan and why, and keeps roles and approvals distinct, so a plan can stand up to an audit. It is a planning tool, not a financial system of record, and we don't yet hold third-party certifications such as a SOC 2 report. This page says exactly what we do and don't provide, so your team can judge the fit.
SOX and internal controls
The Sarbanes-Oxley Act asks public companies to maintain controls over financial reporting. Sales and inventory plans usually sit outside that scope, because they aren't financial statements. Some companies do bring planning data into scope, for example when forecasts support inventory valuation, reserves or forward-looking disclosures. That decision belongs to your company and its auditors.
Where plans do matter to your controls, AvklarePlan provides:
- Access by role. Owner, Admin, Contributor and Read-only roles with distinct rights. Only Owners and Admins import data or change settings; Read-only members can't change anything.
- Separation of duties for approval. Contributors change plans; only the workspace's Owner approves a version as the baseline.
- A complete change trail. Every plan change is recorded with who made it, when, the filter it used and the exact plan lines it touched. Plan values are rebuilt from that record, so the trail and the numbers can't disagree.
- Reversal on the record. Removing a step is itself recorded; history is never silently rewritten.
- Snapshots and baselines. Versions can be frozen as snapshots, and comparisons run against the approved baseline.
- Evidence you can keep. Plans and their full change history export as files, for your own records and for auditors.
- Administrative records. Membership and role changes, ownership transfers, subscription changes and workspace deletions are recorded with who did them and when.
- Precision without silent rounding. Figures are stored at full precision and rounded only for display.
Your side of the controls typically includes reviewing who has access to each workspace, approving plans through the Owner, and keeping exported plans and history as evidence for the periods your policies require.
Workspace isolation
Every table holding workspace data carries the workspace it belongs to, and every query names it. On top of that, the database enforces row-level security: each request runs on a database connection locked to the signed-in member's workspace, so even a mistake in application code can't return another workspace's rows. The workspace always comes from the member's verified sign-in, never from anything a browser sends.
Sign-in and accounts
- Passwords stored only as salted PBKDF2 hashes; we can't see them.
- Limits on sign-in and reset attempts, per email address and per network address.
- Email addresses verified before use; one-time links (verification, password reset, invitations) stored only as hashes and expiring.
- Membership and role re-checked on every request, so removing someone takes effect immediately.
- Changing a password signs out the account's other sessions.
Application and infrastructure
- Encrypted connections (HTTPS) for all traffic, through CloudFlare.
- All database access through stored procedures with typed parameters; no SQL is built from user input.
- Forms protected against cross-site request forgery.
- A build that fails if any software package has a known vulnerability.
- Errors recorded centrally so problems are found and fixed; diagnostic logs expire after 90 days.
- Hosted on SmarterASP.net in a dedicated application pool, separate from our other products.
Payments
Card and bank payments are taken on Stripe's own pages. Card details never pass through or rest on AvklarePlan's servers; Stripe is certified to the PCI DSS standard for handling them. Stripe also calculates sales tax.
Data retention
| Data | Kept |
|---|---|
| Workspace data (items, actuals, plans, history) | Until the Owner deletes the workspace, or 90 days after a lapsed workspace locks, with notice to the Owner at lock and at least 14 days before deletion |
| Uploaded import rows, including unmapped columns | 7 days after the import is loaded, or after upload if never loaded |
| Error and diagnostic logs | 90 days |
| Security and audit records | Kept, to protect the service and answer disputes |
| Billing and invoice records | Kept by Stripe, as tax law requires |
Workspace deletion is permanent and covers every table that holds the workspace's data; a record that the deletion happened is kept.
Providers
AvklarePlan uses SmarterASP.net (hosting), CloudFlare (secure delivery), Stripe (billing) and Brevo (email). Our Privacy Policy lists what each handles.
Privacy laws
For a workspace's business data, we act on the workspace's behalf, as its processor. Requests to see, correct or delete personal data can be sent to [email protected], and we answer within 30 days. See the Privacy Policy.
Incidents
If we learn of a security incident affecting a workspace's data, we'll tell its Owner promptly, with what we know, what we're doing about it, and what they may need to do.
Not offered yet
So there are no surprises, AvklarePlan doesn't currently offer:
- a SOC 1 or SOC 2 report, ISO 27001 certification, or other third-party attestation;
- single sign-on (SAML or OpenID Connect) or two-step sign-in;
- a contractual service level agreement or uptime commitment;
- a choice of the country where data is stored.
If one of these is a requirement for you, tell us at [email protected]. Customer needs decide what we build next, and we're glad to answer security questionnaires.