Terms, Privacy & Security

Terms of Use

Pre-release / private alpha

MultiPC VEGA is in private alpha. Features may change, be incomplete, or be discontinued. Any demos, screenshots, and examples are illustrative and not a promise of performance or availability.

Who may use

You must be authorized to operate the computers, accounts, and data you connect to VEGA. You are responsible for ensuring your use complies with your organization’s policies and applicable law.

Acceptable use / prohibited use

You agree not to:

• attempt to probe, scan, or test vulnerabilities of the site or software, or bypass access controls
• use VEGA to access systems you do not own or have explicit permission to operate
• upload malware, unlawful content, or infringing material
• reverse engineer or attempt to copy proprietary components (except to the extent legally prohibited from restricting)

Product access, trials, and billing

If we offer pre-release access, it may include a trial or pilot period. If we request payment method verification, we may place a $1 authorization hold to confirm the card is valid. This is not a charge and typically drops off automatically depending on the bank. Any future paid plans, fees, or deposit requirements (if any) will be disclosed clearly at the time you sign up.

Confidentiality (pre-release)

Any non-public materials shared for private alpha evaluation (download links, builds, roadmaps, pilot documentation) should be treated as confidential unless we state otherwise in writing.

Intellectual property

MultiPC, VEGA, and related materials are owned by MultiPC Technologies or its licensors. You may not copy, republish, or distribute our materials without written permission.

Disclaimers

The website and any pre-release software are provided “as is” and “as available,” without warranties of any kind to the maximum extent permitted by law.

Limitation of liability

To the maximum extent permitted by law, MultiPC Technologies will not be liable for indirect, incidental, special, consequential, or punitive damages, or for loss of profits, revenue, data, or goodwill.

Contact

Questions: support@multipc.io

Privacy

Plain-English summary

We don’t sell personal information. We collect only what we need to run the website, respond to requests, and operate pilots.

What we collect

• Contact information you provide (name, email, company) when you request access, join a waitlist, or contact support
• Basic website logs (IP address, user agent, timestamps, pages accessed) for security and reliability
• Account/billing metadata if you create an account (managed via our service providers; we do not store full card numbers)

Payment processing

If you enter payment information, it is processed by our payment provider (e.g., Stripe). We receive limited billing metadata (such as customer name/email and payment status). We do not receive or store full card details.

How we use information

• to operate and secure the website and services
• to respond to inquiries, schedule demos, and manage pilot access
• to improve reliability and product quality
• to prevent fraud and abuse

Sharing

We share information only with vendors who help us operate (hosting, analytics if used, email support, payment processing) and only as necessary to provide the service.

Data retention

We retain operational logs for a limited period for security and reliability, then delete or anonymize them. Support emails may be retained as needed to manage the relationship and comply with legal obligations.

Your choices

You can request access, correction, or deletion of your contact record by emailing support@multipc.io. We’ll honor requests where feasible and legally permitted.

Children

Our products are not intended for children under 13.

Security overview

Goal

Enable one operator to orchestrate many endpoints without expanding attack surface.

High-level controls

• Encrypted transport for control signaling using modern standards
• Device authorization: commands route only to endpoints explicitly paired/authorized
• Outbound-first posture (where possible) to reduce inbound exposure on endpoints
• Bounded execution: sensitive actions can require confirmation and can be restricted by policy (pilot-dependent)
• Auditability roadmap: expanded logging, hardened modes (e.g., LAN-only), and enterprise controls as deployments mature

Important clarification

VEGA is designed to operate within the permissions of the authorized machine and user context. Any file search or retrieval is intended to occur within authorized folders/systems and via normal OS permissions and indexing — no bypassing.

Enterprise pilots

For enterprise/MSP pilots, we can provide a security review packet describing deployment topology, access controls, and logging posture under NDA.

Contact

Support: support@multipc.io
Address: 6701 Corporate Dr, STE N, Johnston, Iowa 50131, USA