A clear view of protection
MeshDex One brings business modules into a shared workspace with governed access. Data protection includes confidentiality, controls that help preserve accurate records, and recovery preparations.
This guide describes implemented product controls and their scope. It is not a certification, an independent security assessment or a contractual availability or recovery guarantee. Confirm requirements specific to your business before onboarding.
Workspace access and account protection
Workspace roles, module permissions and record ownership checks govern access. Sharing a platform does not give every member access to every module or record. This does not imply a separate server or database for each customer.
Profile includes password controls, available two-factor settings and recent sign-in activity. Use the session controls actually offered by the screen; recent browser activity does not mean every individual web session can be revoked there.
Connections and hosting
HTTPS protects browser connections to the service. Request checks and sign-in abuse controls provide additional protection around supported entry points.
MeshDex One operates the hosting environment used to deliver the service. Hosting does not by itself prove encryption coverage, dedicated customer infrastructure or a particular data-residency commitment. Ask about your location or contractual requirements before transferring regulated information.
What encryption covers
Application-level encryption support is implemented for selected connected-service credentials and two-factor secrets. Passwords are stored as hashes for verification rather than as recoverable passwords. These controls have different purposes.
Encryption of selected fields, protected document storage and encrypted backups are separate controls. This guide does not claim that every business record has application-level encryption or that the service uses end-to-end encryption. Ask for current scope confirmation if encryption is a procurement requirement.
Private documents and record integrity
People private-document handling includes authenticated downloads, workspace and profile ownership checks, upload size and file-type checks, integrity metadata and encrypted storage support for new uploads. Older documents may follow a compatibility path. Do not assume identical coverage for every attachment in every module or universal malware scanning.
Supported finance and payment workflows use coordinated updates and duplicate-operation controls to help preserve consistency. Activity and audit records support review in the workflows that provide them. These controls do not make every record immutable or replace approval and reconciliation responsibilities.
Backups and recovery
Encrypted backups, integrity verification and isolated recovery checks are part of the recovery approach. Completed recovery exercises provide evidence for the scope and date tested; they do not prove current coverage for every module, uploaded file or connected service.
Recovery is an operational process, not a self-service undo for every action. A fixed recovery point, recovery time, backup retention period or uninterrupted availability is not promised by this guide. Confirm required coverage and commitments before relying on them; retain business exports where available.
Data use, connected services and AI
The Privacy Policy describes data use, service-provider processing and permitted access. MeshDex One states that it does not sell customer or personal data. Support, security and legal handling must follow the applicable policy; this guide does not promise that service personnel can never access data.
Connecting a service authorizes the relevant workflow to exchange data with that service. Supported AI requests can send the selected content and relevant workflow context for processing. Review what you submit and your workspace policies; do not assume processing stays entirely within MeshDex One or that every service has identical retention or training terms.
Ask for current processing-provider, location and contractual information relevant to your intended use. This page is not a published subprocessor register, a signed data-processing agreement or an approval for regulated workloads.
Retention, export, correction and deletion
Workspace data is retained for the operating relationship, subject to applicable requests and retention obligations described in the Privacy Policy. Accounting, billing, employment, security or legal records may need different treatment. A single deletion deadline does not apply to every category.
Workspace admins can request export, correction or deletion of eligible data through support. Identity, authority and scope must be verified first. Removing access or disconnecting an integration does not automatically erase historical business records, backups or copies held by a connected service.
Backup copies may persist until their applicable retention cycle ends. Ask for the current category-specific retention and deletion position when this is a contractual requirement. Do not send passwords, access tokens or unredacted sensitive records with a request.
What your team controls
Assign the minimum access each person needs, review members when responsibilities change, and enable available two-factor protection. Protect recovery methods and review unfamiliar sign-in activity.
Choose connected services deliberately, review AI submissions and outputs, and use the approval and reconciliation controls offered by each module. Confirm the module’s availability and scope before relying on a workflow; shared access and billing do not imply automatic transfers between all modules.
Planned improvements — not current guarantees
The security roadmap includes broader authorization testing, stronger confirmation for sensitive actions, expanded data-governance and recovery verification, and independent security assessment. These are planned improvements; this guide does not present them as completed or assign a delivery date.
A formal disclosure program and additional assurance material remain roadmap work. This page makes no claim of security certification, a completed independent penetration test, a public live-status service or a standard service-level agreement. Ask for the latest available evidence and contractual terms.
Report a concern or ask for details
Send security reports and privacy questions to [email protected], or use Contact. Describe the affected feature, when you observed the issue and safe reproduction steps. Share only sanitized details; arrange a secure exchange before sending sensitive evidence.
Do not access another customer’s records, disrupt the service or continue testing beyond your authorization. This reporting channel is available now; it is not a bug-bounty or safe-harbor commitment. For a data request, identify your workspace and requested scope without including credentials.
Related guides
Ask your workspace administrator for access or contact support with the page name and a sanitized error message.