Privacy Notice

This notice applies to visitors, prospective customers, portal users, authorized testers, and organizations evaluating or using Veqa. For a customer-operated call flow, the customer generally determines why and how caller information is used, while Machplace processes information to provide the agreed service. The signed agreement must define the parties' roles for the specific use.

Website and inquiries.

When you contact us, we process the name, work contact details, organization, and message you provide. Web infrastructure may also record connection and security information such as an IP address, user agent, request path, and timestamp.

Portal accounts.

We process account identifiers, work contact details, role, organization, authentication state, security settings, and activity needed to provide and protect the portal. The portal may display operational, usage, and billing information made available by the current service.

Calls and service events.

Depending on configuration, Veqa may process caller audio, working transcripts, collected field values, action requests and caller-safe results, call routing details, timestamps, language, outcome, duration, correlation identifiers, and troubleshooting events. Authorized teams may use the live call inspector and related evidence during implementation and QA.

Current internal implementation and QA environments can retain recordings, transcripts, and related events because they are important for diagnosing speech, workflow, integration, and call-control problems. A customer evaluation may also retain them when the configuration and written terms say so.

The generally available tenant controls for collection, notice, consent, access, independent recording and transcript retention, deletion, redaction, and backup alignment are still launch gates. Until those controls and a project-specific schedule are accepted, Veqa should be used only with synthetic data or expressly authorized test calls.

Some authorized internal tests may derive a mathematical representation from speech and compare it with an enrolled reference to support fraud-risk monitoring. This is a sensitive, optional capability and is not part of the standard customer configuration.

Commercial activation requires explicit tenant enablement, tenant-isolated storage, access and audit controls, a defined retention and deletion schedule, and confirmation of any required notice, consent, or legal basis. Results are for monitoring and human review and must never be the sole basis for an automatic denial. Cross-customer matching is outside the offered scope.

• to operate, secure, diagnose, and improve Veqa;
• to evaluate and validate configured call workflows;
• to perform approved actions and return caller-safe results;
• to authenticate users and protect portal accounts;
• to respond to inquiries and provide agreed support;
• to measure service usage and meet legal obligations; and
• for other purposes documented in an applicable agreement.

Veqa is designed for customer-site and Machplace-managed deployments. The public site does not promise a particular data location, infrastructure owner, isolation mechanism, or provider list for every deployment. Those facts must be recorded in the accepted architecture and customer terms.

Machplace may use infrastructure, network protection, email, support, and other service providers where needed to operate the website, portal, or agreed service. Project-specific terms must identify material subprocessors and transfers where required.

Retention depends on the data category, environment, and accepted project policy. Internal QA evidence may remain available for troubleshooting until it is deliberately removed under the current QA process. Portal, inquiry, security, operational, and commercial records may be kept as needed for their purpose and applicable obligations.

Before commercial launch, each tenant must have documented defaults and enforceable schedules for recordings, transcripts, speaker-derived data when enabled, service metadata, deletion, and protected backup copies. A signed agreement controls if it specifies a stricter lifecycle.

Machplace uses administrative, technical, and operational safeguards intended to limit access and protect service data. Safeguards and responsibilities vary by deployment and must be verified during acceptance. No public statement should be read as a certification, guarantee, or replacement for a customer-specific security review.

Depending on applicable law, you may have rights to access, correct, delete, restrict, or object to processing of personal information. When Veqa processes information for a customer, requests should normally be directed to that customer; we will support the customer as required by the applicable agreement. For website inquiries and portal account information that Machplace controls directly, contact us below.

Regulated-workload terms, data-processing terms, or similar commitments are available only if expressly included in a signed agreement after legal and security review. They are not created by this website notice.

The portal uses cookies needed for authentication and service security. Website infrastructure may use limited operational measurement for reliability and protection. Veqa does not present third-party behavioral advertising on these sites.

Veqa is a business service and is not directed to children. Customers are responsible for determining whether a proposed call flow may involve children and for establishing the required legal and consent controls before activation.

We may update this notice as the product and accepted data practices change. We will revise the date above and provide any additional notice required by an applicable agreement or law.

For privacy questions or requests, contact [email protected]. Machplace LLC, St. Petersburg, Florida, United States.