Tenant isolation
Business data is separated by tenant-aware database rules and controlled server/RPC access rather than relying only on what the browser chooses to show.
Security & reliability
Trust should come from controlswe can actually explain.
LinkSlate handles operational and customer information, so security, backups and data portability are treated as product requirements. We would rather describe the safeguards we have implemented than display badges that imply more than they prove.
Role-aware access
Manager, employee, customer and platform-admin boundaries are treated separately so users only receive the access appropriate to their role.
File protection
Accepted job files are checked server-side by file signature rather than trusting the filename or browser-provided file type alone.
Independent file backup
Accepted job files are copied to an independent Cloudflare R2 backup and verified with SHA-256 metadata. Uploads fail closed if the independent backup cannot be completed.
Hardened public endpoints
Public enquiry and customer-facing entry points use server-side validation, rate limiting and deliberately restricted data access.
Release gates
Production changes pass dependency checks, public/product lint, security regression checks and a production build before deployment.
What we have tested
Security checks are part of release readiness.
Testing has included cross-tenant access boundaries, employee privilege restrictions, customer anonymous access, role separation and file-upload validation. Security tooling may still report informational findings where the architecture deliberately blocks direct table access and uses controlled server functions instead.
What this page does not claim
We do not claim an external certification unless and until it has actually been obtained.
We do not claim that any online service is risk-free or impossible to breach.
We do explain the controls, testing and backup design that are currently part of LinkSlate.
Data portability & continuity
Your business data should not become a hostage to the software supplier.
No supplier can honestly promise it will exist forever. The more useful protection is clear ownership, export rights, backups and an exit process that gives the customer a route to retrieve its information.
You retain your data rights
The customer retains its rights in the Customer Data it puts into LinkSlate.
Export during service
Available export functions can be used during the term, with reasonable support for a standard export where an appropriate built-in export is not available.
30-day retrieval window
The current contract template provides a 30-day standard retrieval/export period after termination or expiry, subject to authority and security checks.
No artificial exit charge
A normal available or reasonable standard export is not given an artificial exit fee; substantial reconstruction or non-standard migration work may be separately chargeable.
Independent file backup adds another resilience layer for accepted job files, but backup is not a substitute for customer export rights or the customer's own business-continuity planning.
See the commercial and exit position →Questions before you commit?
Ask us about the controls relevant to your workflow.
If your sector or customer contracts create specific privacy, access or resilience requirements, raise them during the enquiry or demo so we can tell you what LinkSlate supports and what would need separate scoping.