JAEN Contact
TENZOHby Recmill Inc.
Product · Point cloud sharing platform

Security: Point clouds, kept safe like a storehouse.

Point cloud data is an exact record of your facilities, infrastructure, and sites, which makes it a highly confidential asset. For TENZOH, security itself is the greatest value we deliver.

TENZOH showing a plant point cloud in a web browser
Actual screen (in a browser)

This page outlines how we think about security in TENZOH and the measures we have in place, so you can use it with confidence. We deliberately leave out specific implementation methods, configuration values, and similar details that an attacker or a competitor could exploit or copy.

Principles: Four ideas behind the design.

TENZOH doesn't rely on a single control. It layers several independent defenses, and we run our own system that keeps checking, continuously and automatically, whether those defenses are holding.

01Defense in depth

Authentication, permissions, encryption, network, application, and monitoring each defend as an independent layer.

Even if one layer is breached, the whole system stays protected

02Least privilege

We grant every user and every component only the permissions they need.

If something does go wrong, the impact stays contained

03Secure by default

If something is misconfigured or goes wrong, the system fails closed, not open.

A failure ends in downtime, not a data leak

04Continuous verification

We don't stop once a control is in place. We keep testing it.

Quality does not degrade over time

Measures: Five areas, defended in layers.

Access control

We keep tight control over who can get in.

Invitation only
We don't offer open sign-up
Multi-factor authentication (MFA) required
We don't rely on passwords alone
Strong password policy
Passwords are stored in a form that cannot be recovered
Role-based permissions
Users cannot create permissions stronger than their own
Immediate removal and deactivation
Access ends the moment an account is turned off
Impersonation tracking
When an action is taken on someone's behalf, the record shows who actually performed it

Data isolation and protection

We protect your data by keeping it structurally separate from every other organization's.

Tenant (organization) isolation
Every data operation is constrained to one organization, so access cannot cross between them
Encryption at rest
Stored data is kept encrypted
Encryption in transit
Traffic to and from the browser is always encrypted
Private data infrastructure
Isolated where the internet cannot reach it directly
Restricted data delivery
Data is released only after a permission check, and only for a limited time

Application hardening

We apply industry-standard defenses in multiple layers against the common attacks aimed at web applications.

  • Information that users enter or save is processed and displayed safely, so malicious content cannot run
  • Critical information is protected so that it cannot be altered or forged from the user's side
  • Standard browser protections block takeover attempts that embed TENZOH pages in an outside site or redirect users to one
  • Files are served and stored in a way that errs on the side of safety

Abuse and overload protection

We build in safeguards that keep the system from being broken or driven into a runaway state.

Unauthorized access control
We detect and throttle brute-force attempts and high-volume access
Anomaly detection
We watch for usage patterns that differ from the norm
Runaway cost prevention
Caps and monitoring keep heavy processing from running away with resources
Protection against invalid data
When unexpected data is submitted, processing stops safely

Monitoring and auditing

Visible now. Traceable later.

Audit logging
We record key actions so you can trace and review them later
Monitoring and alerts
We continuously monitor cost, access, and processing health
Traceability
When something goes wrong, you can go back and see what happened and when

How we keep handovers safe.

For confidential data, we recommend sharing by invitation instead of relying on public links.

Recommended

Visible only to the viewers you invite

MFA, per-user permissions, instant revocation, and an audit log. You can trace who viewed what, and cut off access the moment you need to. This invited-viewer method is what TENZOH recommends by default.

Alternative

Password-protected public links

It's convenient, but URLs and passwords can spread, so it is not inherently secure. Managing this method is your responsibility.

Assurance: Quality means we keep testing our own work.

What sets TENZOH apart is that we don't secure it once and call it done. Recmill runs the RECMILL Security Assurance Platform, a verification system we built ourselves to hold security quality steady over time. Every month it runs the same cycle automatically: verify, record, share, and strengthen.

  1. Verify

    We verify our core security commitments automatically, every month. The same checks run on every change we ship, so regressions get caught.

  2. Record

    We build up a history of verification results. Every check leaves a record of what was verified and when.

  3. Share

    We share the results with you, past runs included. You can confirm for yourself that the commitments are holding.

  4. Strengthen

    We fix what we find, most serious first, and keep strengthening our controls.

AssuranceAdversarial self-testing

We test TENZOH from an attacker's point of view, again and again, and fix what we find right away.

AssuranceAutomated regression testing

We verify our security commitments with automated checks.

AssuranceScheduled monthly verification

We run the checks every month and share the results, past runs included.

AssuranceComponent vulnerability management

We keep checking the third-party components we use for known risks and fix them early.

This is how we run TENZOH. Automated checks confirm, continuously, that its security commitments are holding right now.

Who runs it, and shared responsibility.

Fix on discovery
When we find a vulnerability or a gap, we fix it and ship the change quickly, starting with the most serious.
Shared responsibility model
TENZOH is responsible for the security of the platform and the application, and we ask you to manage your accounts and credentials properly.

What we ask of you

  • Invite only the people who need access, and grant only the permissions they need.
  • Turn on MFA, and never share or reuse passwords.
  • Share confidential data by invitation, not through public links.
  • When someone leaves or changes roles, disable the account and review permissions right away.

Note: This page is an overview written for customers. The measures described here are strengthened and updated on an ongoing basis. We do not publish implementation details, to keep them from being copied or abused. For the measures we take across the company, beyond TENZOH, see Information security.

Contact: Store your point clouds with confidence.

Ask us a security question, request the verification results, or talk to us about rolling out TENZOH.