Terms of use

Last updated:

Important status

These terms are a placeholder requiring qualified legal review and verified company details before production use.

Website information

Content is general product and educational information. Features, integrations, availability and commercial terms must be confirmed in a written offer. Nothing on this site guarantees platform approval, message delivery or verification.

Acceptable use

Do not misuse the site, attempt unauthorised access or submit sensitive credentials through public forms.

Continue exploring

Follow the most relevant product, workflow and implementation paths for this topic.

FAQ

Frequently asked questions

What is Terms of use?

Starter terms for use of the VartaFlow marketing website pending review by qualified legal counsel.

How should a team evaluate terms of use?

Start with the customer journey, consent requirements, accountable team, connected data and a clear path to human support. Confirm current product availability and limits before implementation.

How can I get help with terms of use?

Contact VartaFlow with your workflow, team size and integration requirements. The team can help you identify the relevant product area and the details that still need verification.

Who should evaluate terms of use?

Include the team that owns the customer journey, operational users, a technical owner, and the people responsible for consent, privacy, security and commercial approval.

What should we prepare before discussing terms of use?

Document the customer use case, expected volume, team roles, current tools, required integrations, consent source, exception handling and the outcome you want to measure.

How is human handover handled?

Define when automation should stop, which team should receive the conversation, what context must be transferred and how unresolved or sensitive cases will be reviewed.

What customer consent considerations apply?

Use an appropriate consent process for the intended communication, retain evidence where required and provide a clear way for customers to change their communication preferences.

How should privacy and security requirements be reviewed?

Identify the data involved, access roles, retention needs, connected processors and incident responsibilities. Request current written security and privacy information during evaluation.

Can this connect with our existing business tools?

Potential connections depend on the system and the currently supported integration method. Confirm available records, events, direction, retries and ownership before implementation.

How long does implementation take?

Timing depends on account readiness, approvals, data, integrations, workflow complexity, testing and team training. Ask for a scoped implementation plan rather than assuming a standard timeline.