Terms of Service
Last updated: 13 November 2026. These changes take effect on 16 December 2026. Until then, the version of 1 July 2026 applies.
1. Agreement
By accessing or using the Datavtar platform ("Service") operated by Datavtar AI Private Limited ("Datavtar," "we," "us"), you agree to be bound by these Terms of Service ("Terms"). If you do not agree, do not use the Service.
2. Service Description
Datavtar is an AI operating system for logistics that enables organizations to connect their knowledge, activate domain expertise, and orchestrate business outcomes. The Service is provided on an ongoing basis and may be updated, improved, or expanded over time. We may add, modify, or discontinue features at our discretion, and will give reasonable notice of any material change that adversely affects a feature you rely on.
3. Account and Access
You are responsible for maintaining the confidentiality of your account credentials and for all activities that occur under your account. You must provide accurate and complete information when creating an account. You agree to notify us immediately of any unauthorized use of your account.
4. Acceptable Use
You agree not to:
- Use the Service for any unlawful purpose or in violation of any applicable laws
- Upload content that infringes on intellectual property rights of others
- Attempt to gain unauthorized access to the Service or its related systems
- Interfere with or disrupt the integrity or performance of the Service
- Use the Service to develop a competing product or service
- Reverse engineer, decompile, or disassemble any part of the Service
Acceptable use of AI
You use the Service's AI features, and the apps and Flows you build with them, only in ways the EU Artificial Intelligence Act (Regulation (EU) 2024/1689) allows. In particular, you agree to:
- Tell people outside your organization that they are dealing with AI whenever an app or Flow sends them a message an AI wrote, or holds a conversation or a call with them
- Never use the Service to infer the emotions of people at work, or to score people on their social behavior or personal characteristics
- Keep a person responsible for every decision that affects a worker, such as a sanction, a suspension, an evaluation, or the end of their work
- Never use the Service for any other practice the Act prohibits, such as manipulating people in ways that harm them or exploiting their vulnerabilities
The app builder works from the same rules when it builds an app: it designs apps that tell people outside your organization when AI writes to them or talks with them, leave decisions about a worker to a person, and record why work was assigned. A Flow's result email says the attached result was prepared with AI. You remain responsible for how you use each app and Flow, and for reviewing it before you rely on it.
5. Your Data and AI-Generated Content
You retain all rights to the data and content you provide to the Service, whether uploaded directly or accessed through connected services such as Google Drive. We do not claim ownership of your content. We use your content solely to provide the Service to you, as described in our Privacy Policy.
Content the Service generates for you, including applications, code, documents, and other outputs produced by features such as Apps, is yours. Datavtar claims no ownership of it, and you are free to use it as you see fit. The platform's own files that run each app, which Datavtar supplies to every app alike, remain Datavtar's (Section 14).
AI-generated content may be inaccurate, incomplete, or require modification. You are responsible for reviewing and validating any AI-generated output before relying on it in production or making business decisions based on it.
We never use your data to train AI models. Your data is logically isolated, with a dedicated content store for your organization. You can delete your data or disconnect external sources at any time; deletion is permanent, on the timelines described in our Privacy Policy and Section 13.
6. Intellectual Property
The Service, including its design, features, content, and underlying technology, is owned by Datavtar AI Private Limited and is protected by intellectual property laws. These Terms do not grant you any rights to use our trademarks, logos, or brand features without prior written consent.
7. Confidentiality
Each party agrees to treat the other party's non-public information as confidential. Datavtar will treat all content you provide to or connect with the Service, including documents, queries, and data from connected services, as your confidential information. We will not disclose your confidential information to any third party except as necessary to provide the Service (e.g., sub-processors listed in our Privacy Policy), with your consent, or as required by law.
8. Third-Party Services
AI Providers
The Service uses third-party AI providers, currently Google, Anthropic and OpenAI, to process queries, generate responses, and build applications. They process your content solely to deliver the features you use, under data processing agreements, and do not use it to train their AI models.
Google API Services
The Service offers integration with Google Drive via OAuth. When you connect your Google account, you authorize Datavtar to access only the specific files you choose, as described in our Privacy Policy. This integration is governed by Google's Terms of Service in addition to these Terms.
You are responsible for ensuring that you have the right to grant Datavtar access to the files you connect, including files in shared drives or shared with you by others. If your organization manages your Google Workspace account, your organization's policies may govern your ability to connect external services.
Datavtar's use of Google API data complies with the Google API Services User Data Policy, including the Limited Use requirements. You may revoke Datavtar's access to your Google account at any time through your Datavtar settings or through your Google Account permissions.
9. Availability and Support
We strive to maintain high availability of the Service and use commercially reasonable efforts to provide reliable access and responsive support. The Service may be temporarily unavailable for scheduled maintenance, updates, or circumstances beyond our reasonable control. Any availability or support commitments agreed in a separate written order form or service-level agreement take precedence over this section.
Except as expressly set out in a separate written agreement, the Service is provided on an "as available" basis without warranties of any kind, whether express or implied, including the implied warranties of merchantability, fitness for a particular purpose, and non-infringement. We do not warrant that the Service will be error-free or that AI-generated responses will be accurate or complete; you remain responsible for reviewing AI-generated output before relying on it.
10. Limitation of Liability
To the maximum extent permitted by applicable law, Datavtar AI Private Limited shall not be liable for any indirect, incidental, special, consequential, or punitive damages, including loss of profits, data, or business opportunities, arising from your use of or inability to use the Service.
Our total liability for any claims arising from these Terms or your use of the Service shall not exceed the amount you paid to us in the twelve months preceding the claim.
11. Indemnification
You agree to indemnify and hold harmless Datavtar AI Private Limited from any claims, damages, or expenses arising from your violation of these Terms or your misuse of the Service.
Any indemnification or defense obligations that Datavtar agrees to provide are set out in a separate written agreement (such as an order form or master services agreement) and, together with all other liability, are subject to the limitations and cap in Section 10.
12. Modifications
We may update these Terms from time to time. Material changes will be communicated via email to registered users at least 30 days before taking effect. Continued use of the Service after changes take effect constitutes acceptance of the updated Terms.
13. Termination
Either party may terminate the use of the Service by providing 30 days' written notice to the other party. Either party may terminate immediately if the other party materially breaches these Terms and fails to cure the breach within 15 days of written notice, or engages in unlawful or unethical conduct in connection with the Service.
Upon termination, your right to access the Service ceases at the end of the notice period, or at the end of the transitional period when your organization is switching provider (Section 14). Your organization's admins can still sign in to export its data until the organization is deleted, including after its subscription has ended.
Connected third-party services (such as Google Drive) are disconnected and the permissions they were given are deleted at the point of termination. After termination, your data enters a recovery window of up to 90 days, during which an export can be requested from support@datavtar.com and the deletion reversed, after which active data is permanently and irreversibly deleted from Datavtar's systems and from your organization's AI content store. A copy an AI provider keeps of a request it processed is deleted on that provider's own schedule, set out in our Privacy Policy. Residual copies in encrypted backups are purged on the standard backup rotation cycle and remain inaccessible for live use until then.
14. Switching and export
Your organization can move its data to another provider or to its own systems at any time, as the EU Data Act (Regulation (EU) 2023/2854) provides. Datavtar charges nothing for switching, for exporting data, or for erasing it. This section applies to every organization, wherever it is established.
Exporting at any time
An admin can export the organization's data at any time from its Export settings in Datavtar, including after its subscription has ended. The export is a set of files, mostly ZIP archives, kept for 7 days for the admin who started it to download. It holds what that admin can open in Datavtar, in structured, commonly used, machine-readable formats:
- Documents: each file in the format it was added in, with each earlier version whose content differs, and an index (CSV) of its Space and folder, version, title, type, size and dates
- Pages: each page as Markdown, with its earlier versions and its images
- Insights: each Space's Insights, such as its glossary, as Markdown
- Boards: each board (JSON) with its lanes, labels, fields, card templates, shared views and Routines, and its cards, with each card's checklist, field values, items, linked cards, comments and files; the board's history, and its Routines' runs with each step of each run (CSV)
- Offices: each office (JSON) with its people, guidelines, key priorities, pins, Access and AI staff, and the organization's own guidelines; the answers an office approved; the emails and requests each office received with the answers drafted for them, the replies approved and the emails sent; the decisions asked on cards and the answers to requests; what AI staff worked on, wrote to apps and Experts and proposed; and the teams formed for a goal, with who joined (JSON). An email set aside from an unproven sender is included as the email file it arrived as
- Collab: each Collab (JSON) with every canvas's drawing and its comments
- Flows: each Flow (JSON) with its versions, owners, rules, triggers, approvals and the Spaces it reads, the files it keeps of its own, and each draft worked out with Diva, with its conversation and the results it made on the examples; the rules for every Flow; and the services the organization's Flows connect to, without their logins
- Flow runs: each run (JSON) with how it went, its items, each attempt of each step with what it wrote to its log, checks, reviews and deliveries, and the files it kept (what arrived, what each step made and what it delivered) in their own formats
- Reports and dashboards: the dashboards shared with the organization and the admin's own, with their tiles, the organization's definitions with every version, its data sources without their logins, and the admin's own saved answers and dashboard drafts (JSON)
- Conversations: the conversations and searches of the admin who started the export (JSON)
- Research in Leads: the organization's Leads setup, and each run (JSON) with every company's result
- Lists in Leads: each list (CSV), as its own download has it
- Marketing: each brand's profile, Brand elements, websites and content, each campaign with its reviews and its drafts as Markdown, and each website assessment's findings (JSON)
- Experts from Expert Studio: each Expert your organization authored (JSON), with its versions, tools, Marketplace submissions and the documents its authors added; its Marketplace storefront and the policies it publishes; and the Experts your organization subscribes to, with how each one updates
- Audit log: the organization's audit log (CSV)
- Members and access: the organization's members and open invitations (CSV), requests to join, the Spaces each member or office is limited to or given, and what is connected to it, such as its integrations, their webhooks and the apps an admin approved (JSON)
- Billing and requests: the organization's billing details, its plan and each app's plan with their history, the Marketplace apps it got and what it paid, its sales of its own Marketplace apps as Studio lists them, the requests it sent to Datavtar (for a connector, an Enterprise plan, a refund or to publish in the Marketplace) with how each was settled, and the Marketplace policies its members accepted (JSON); and replies to Datavtar's emails from people outside the organization, such as someone copied in or a former member, as the email files they arrived as
- Apps: each app's code (ZIP), where its downloads are on; its saved data, as a SQLite database or a PostgreSQL archive; its versions with what each was asked for and changed, its automations and their runs, who may use it, its design documents, its setup, the systems people described for it, and its emails (JSON and CSV); and the organization's QuickApps library and WhatsApp lines
- Contents: a file (JSON) naming every file in the export, what each part holds, and anything left out, with the reason
The files, pages and Insights in the Spaces of offices the admin isn't in stay out, as they do in Datavtar itself: an admin who adds themselves to an office, which tells its head and deputies, includes its Space in the next export. Boards, Collabs and each office's own records, which an admin can open wherever they are filed, are all included, apart from what an office's people wrote among themselves about a request that admin sent it. The audit log lists what happened in those Spaces and who did it, without naming the items.
Each member's own export
What a member keeps private stays out of the organization's export, so that it stays private. Each member can export it at any time from Export in their account settings in Datavtar. The export is kept for 7 days for that member alone to download, in the same formats, and holds:
- Files in My Space: each file in the format it was added in, with each earlier version whose content differs, and an index (CSV) of its folder, version, title, type, size and dates
- Pages in My Space: each page as Markdown, with its earlier versions and its images
- Conversations: the member's conversations and searches (JSON)
- Private dashboards and saved answers: the member's private dashboards with their tiles, their private data sources without their logins, their saved answers and their dashboard drafts (JSON)
- Board views and follows: the member's own board views, the views and cards they follow, the board notices they chose, and the cards they move without being asked about their other boards (JSON)
- Unsent app changes: the member's requests to change an app that are still unsent, each kept for 7 days after its last edit (JSON)
- Preferences and reviews: the member's preferences in Analytics and Leads, the emails they turned on or off, their reviews of Experts and apps, and the webhooks of the apps they connected (JSON)
- Home and notices: the briefings and day plans Diva wrote for the member, and the notices in their bell (JSON)
- Replies to Datavtar's emails: the member's replies to Datavtar's emails, as the email files they arrived as, with an index (CSV)
- Contents: a file (JSON) naming every file in the export, what each part holds, and anything left out, with the reason
Once the organization's subscription has ended, only its admins can still sign in. Any other member then asks support@datavtar.com for their own export, and Datavtar prepares it and provides it to that member alone, until the organization is deleted and during the recovery window in Section 13. If Datavtar has suspended the organization, its admins ask support for the organization's export in the same way, and each member for their own: Datavtar prepares it without lifting the suspension and emails its links to the person it is for.
What stays with Datavtar
The two exports above are the complete list of what can be exported. Everything else stays with Datavtar, for one of four reasons:
- Datavtar's trade secrets. Its code and prompts, including the platform's own files inside each app; the records it keeps to run itself, such as delivery queues, editing sessions and progress markers; the search indexes and other working copies it builds from your content; its operational logs, such as the steps and tests it runs while building or changing an app, the events a Flow's engine records, and each call an Expert's tools serve; its own records of what running the Service costs; and Datavtar's own records about your organization, such as how it signed up and the days its members were active.
- Security. Logins and keys saved in the Service, and sign-in and security records, stay out for their security: a copy of them could be used to reach your organization's accounts and systems.
- Records held by others. Invoices and receipts come from Paddle, which issues them to your organization. The content of Experts that other publishers provide belongs to them.
- A former member's privacy. What a member kept private stays unread by anyone after they leave the organization. An admin can hand the items in their My Space to a colleague, an office or the organization's Space, and the exports then hold them where they were handed. Their conversations, private dashboards and saved answers stay with Datavtar until the organization is deleted.
None of this limits anyone's rights under data protection law. The Privacy Policy sets out how a person asks for their own data.
Datavtar keeps this section's lists of what can be exported, and of their formats, up to date.
Switching to another provider
To switch, your organization tells Datavtar at support@datavtar.com, giving the notice in Section 13, and says whether it is moving to another provider (naming it, if it wants Datavtar to work with that provider), moving to its own systems, or only wants its data erased. The notice period is never longer than two months. Then:
- Transitional period. The switch is completed within 30 calendar days of the end of the notice period. During it, the Service keeps running for your organization on its current plan, which continues until the switch is complete, with the same security as before, and Datavtar gives reasonable help with the move: information about the export and its formats, support for your organization's exit plan, and notice of any known risk to the continuity of its work. Your organization may extend the period once, to a length it considers more suitable.
- If 30 days is not feasible. Datavtar says so within 14 working days of the request, with its reasons, and proposes another period of at most seven months, during which the Service keeps running.
- End of the agreement. The agreement ends, and Datavtar confirms it to your organization, once the switch is complete, or at the end of the notice period when your organization only wants its data erased.
- Retrieval. For at least 30 days after the transitional period, your organization's data stays available to export: its admins can export it themselves until the organization is deleted, and an export can be requested from support during the recovery window in Section 13.
- Erasure. Once the retrieval period has passed, Datavtar deletes your organization, and all of its data is erased as Section 13 describes.
15. Data Processing
For organizations subject to the GDPR or similar data protection regulations, Datavtar offers a Data Processing Agreement (DPA) that governs our role as a data processor for your organization's content. To request a DPA, contact us at legal@datavtar.com.
In the event of any conflict between these Terms and an executed DPA, the DPA will take precedence with respect to the processing of your organization's personal data.
16. Assignment
You may not assign or transfer these Terms without our prior written consent. Datavtar may assign these Terms in connection with a merger, acquisition, or sale of all or substantially all of its assets, provided the assignee agrees to be bound by these Terms. We will notify you of any such assignment.
17. Force Majeure
Neither party shall be liable for any delay or failure to perform obligations under these Terms due to causes beyond its reasonable control, including but not limited to natural disasters, acts of government, internet or infrastructure failures, or third-party service outages.
18. Survival
Sections relating to confidentiality, intellectual property, limitation of liability, indemnification, data processing obligations, the retrieval and erasure of data after switching, and governing law shall survive termination of these Terms.
19. Severability
If any provision of these Terms is found to be unenforceable or invalid by a court of competent jurisdiction, that provision will be limited or eliminated to the minimum extent necessary, and the remaining provisions will remain in full force and effect.
20. Governing Law
For an organization established in the European Economic Area, these Terms are governed by the laws of the Netherlands, and the courts of the Netherlands have exclusive jurisdiction over any dispute arising from them, as they do for the Data Processing Agreement.
For any other organization, these Terms are governed by the laws of the Republic of India. Any disputes arising from these Terms shall be subject to the exclusive jurisdiction of the courts in Pune, Maharashtra, India.
21. Contact
For questions about these Terms, contact us at legal@datavtar.com.
Datavtar AI Private Limited