Bentokai

Terms of Service

These Terms of Service govern your use of this website and of the Bentokai platform at app.bentokai.com. By creating an account or using the service, you agree to these terms.

1. Who provides the service

Bentokai is operated by Umai Media, S.L. (VAT ESB26634485), Calle San Gerardo 50, 28035 Madrid, Spain ("Umai Media", "we", "us"). These terms are a contract between you and Umai Media, S.L.

2. The service

Bentokai is a business-management platform for companies and their brands. Depending on your configuration, it provides tools such as brand, user and permission management; a contacts directory; invoicing (proformas, invoices, credit notes, numbering series and payment tracking); expense tracking, including supplier bills received through the integrations and email mailboxes you connect; accounting features based on the Spanish general chart of accounts; tax-filing tracking and an informational fiscal calendar; a Treasury feature that lets you connect your own bank accounts to view balances and transactions; document import with automated data extraction; first-party web analytics for your websites, through a script you add to them, including the detection of visits from automated crawlers; site-search analytics, search-performance reports based on Google Search Console and page-speed monitoring; uptime monitoring and public status pages, to which people can subscribe to receive incident updates by email; a customer-support desk, with a public portal and website forms through which your customers can open tickets; project management, with tasks, files, documents, roadmaps, time tracking and budgets, and a portal to which you can invite clients to follow a project; social media management, which lets you link Facebook Pages, Instagram professional accounts, LinkedIn company pages and Google Business Profile locations to a brand, compose, internally approve, schedule and publish posts to them, see statistics and reports on how the profiles and their posts perform, including by scheduled email, and, where you switch it on, read and answer comments, reviews and messages in an inbox (see section 6); dashboards; an activity log; notifications in the app and by email; an optional connector through which your users can let AI apps of their own choice work with a brand's contacts, its web-analytics reports, its uptime monitoring, its site-speed measurements, its projects and its site-search analytics; and an optional API through which your own software can read and change a brand's contacts, read the reports of its web analytics, read and operate its uptime monitoring, read and operate its site-speed measurements, and read and work on its projects, and read its site-search analytics and ask for a sync of it (both in section 7). Features may change over time as described in section 14.

Features that involve other people. Some features collect personal data from, or show content to, people outside your team: the scripts and crawler reports you add to your websites, your status pages, your support portal and website forms, your project portal and the Social inbox. You decide whether and how to use them, and for the personal data they involve you are the controller (section 12): you are responsible for having a legal basis for it, for informing the people concerned as the law requires, for example in your own privacy notice, and for configuring those features accordingly.

3. Eligibility and accounts

Bentokai is intended for business use by authorised representatives of a company. You are responsible for the accuracy of the information you provide, for keeping your credentials secure, and for the activity that takes place under your account. You must be authorised to connect any bank account or social media profile you link.

4. Your responsibility to review final data

Bentokai is a tool: it computes, formats, stores and transmits the information that you and your team put into it, and you remain solely responsible for that information and for everything you produce with it. In particular, you are responsible for reviewing all final data before relying on it or acting on it: invoices and credit notes before issuing them (issued documents are immutable), accounting entries and reports before filing or sharing them, deadlines before relying on them, imported or automatically extracted data before saving it, and any figures before making business decisions based on them. Bentokai does not review your data for correctness or legal compliance.

5. Bank connections and third-party providers

When you connect a bank account, you authorise the connection directly with your bank through a licensed account-information service provider (Enable Banking or, where applicable, GoCardless Bank Account Data). This access is read only: Bentokai retrieves balances and transactions to display them to you and does not initiate payments or move funds. Your online banking credentials are never seen or stored by Bentokai. You can disconnect a linked account at any time. Availability of specific banks and data depends on those providers and on your bank.

6. Social media accounts

The Social feature lets you connect social media profiles to a brand through each platform's own authorisation screen and act on them from Bentokai. How we handle the data involved is described in section 4 of the Privacy Policy.

Your authorisation. By connecting a profile, you confirm that you hold the role on the platform needed to manage it and that the profile's owner has authorised you to connect it to Bentokai and, through Bentokai, to publish and schedule posts on it, view its statistics, and read and answer its comments, reviews and messages. If that authorisation ends, you must disconnect the profile.

Your instructions and your content. Bentokai publishes, replies and hides or shows comments on a connected profile only on the instructions of you and the users you give access to the Social feature: the posts they write, approve and schedule, the replies they write and send, and the comments they choose to hide or show. You are responsible for all content that you or your users publish, schedule, approve or reply with through Bentokai, and for holding all the rights, licences and permissions it needs, including for any text, images, videos, music, trademarks and personal data it contains. The approval step is a tool for your own internal review: Bentokai does not check content for accuracy, lawfulness or compliance with platform rules.

The platforms' terms. Each platform's terms and policies apply to you directly, and you must comply with them, including: for Facebook and Instagram, Facebook's Terms of Service, the Instagram Terms of Use, the Meta Commercial Terms and Meta's Pages, Groups and Events Policies; for LinkedIn, the User Agreement and the LinkedIn Pages Terms; and for Google Business Profile, the Google Terms of Service, the Google Business Profile Additional Terms of Service and the Business Profile policies and guidelines, including the third-party policies when you manage a profile for a business you do not own. Bentokai's own access to the platforms is governed by the Meta Platform Terms, the LinkedIn API Terms of Use, the Google APIs Terms of Service and the Google API Services User Data Policy, including its Limited Use requirements, and you must not use Bentokai in a way that would cause us to breach them. In particular, you may use the data Bentokai receives from a platform, such as statistics, comments, reviews and messages, only to manage the profiles you connected and to answer the people who write to them, and you must respect the limits those terms set on how long that data may be kept and how it may be used, which Bentokai applies as described in section 4 of the Privacy Policy.

The platforms control their services. Each platform decides on its own whether, when and how to accept, show and keep content. A platform may reject, delay, review, remove or limit the reach of a post; change, restrict or withdraw access to its API; limit the number of requests Bentokai can make; or restrict, suspend or remove your profiles or accounts. Features that depend on a platform may therefore change, be limited or stop being available. Bentokai does not control these decisions and cannot guarantee that a post will be published at the scheduled time, or at all, or that it will remain published.

Scheduling, retries and uncertain outcomes. When a platform reports a temporary error, Bentokai retries automatically for a limited time. If a scheduled post cannot be sent within several hours of its scheduled time, Bentokai does not publish it late: it marks it as missed and notifies the users who wrote and approved it, and you can retry it. If Bentokai cannot confirm whether a post was published (for example, because the platform did not answer, or answered with an error after receiving the post), it does not publish it again on its own and tells you so. Before retrying such a post, check the profile on the platform: the post may already be live, and a retry could publish it twice.

Media. Images and videos you upload for publication may be converted or resized to meet each platform's requirements. Some platforms only accept them by fetching them from a web address; for those, while a post is being published, Bentokai places a temporary copy of the file at a public but unguessable address and removes it within 48 hours. Storage for uploaded media is limited per brand: once a brand reaches its limit, new uploads are refused until space is freed or the limit is raised.

Statistics and reports. Profile and post statistics, and the reports built from them, including scheduled email reports, are based on the figures each platform provides. Those figures may arrive late, be revised, be incomplete or be unavailable for some periods, metrics or posts, and may differ from those shown in the platform's own tools. Scheduled email reports are sent only for a brand whose manager switches them on, and only to the users who have access to that brand's statistics; each of them can stop receiving them at any time.

The inbox. The inbox brings together the comments on your profiles' posts, the direct messages sent to your Facebook Page and Instagram account and the reviews of your Google Business Profile locations, so that the users you give access to it can read and answer them, hide or show other people's comments on Facebook and Instagram, delete your profile's own replies and keep track of each conversation. It is off for each brand until whoever manages the brand in Bentokai switches it on; until then, Bentokai reads none of this. Bentokai sends a reply only when one of your users writes and sends it: it never replies automatically and does not write replies with artificial intelligence. A direct message can be answered only within 24 hours of the person's last message, as the platforms require. Because some platforms limit how long their data may be kept (section 4 of the Privacy Policy), older texts disappear from the inbox and remain available only on the platform, and there is no export of inbox content. If Bentokai cannot confirm whether a reply was posted, it tells you so and does not send it again on its own: check the platform before sending it again, because a second reply would be public too.

Replies to Google reviews. Google requires the authorisation of the business concerned before anyone replies to its reviews on its behalf. Replies to Google reviews are therefore off for each brand until whoever manages the brand in Bentokai switches them on, and switching them on records your confirmation that the business has given you that authorisation. Switch them on only once you hold that authorisation, and switch them off if it is withdrawn. Google may hold a reply for review before publishing it, or reject it.

The people who write to you. Comments, reviews and messages come from members of the public. For their personal data you are the controller, and Umai Media processes it on your behalf under section 12. You are responsible for having a legal basis for that processing and for giving those people the information that data-protection law requires, for example in your privacy notice or on your profiles, and you must use their data only to manage your profiles and answer them. Some platforms restrict further use: for example, LinkedIn does not allow its members' comments to be exported or combined with other data, and Google does not allow reviews to be aggregated. You must not copy inbox content out of Bentokai to get around those restrictions.

Disconnecting. You can disconnect a profile in Bentokai at any time, and you can also revoke Bentokai's access in the platform's own settings, as described in section 4 of the Privacy Policy. Once a profile is disconnected, Bentokai stops acting on it, cancels the posts still waiting to be published to it and deletes the statistics and inbox content received from it. Bentokai does not delete posts or replies that have already been published: they stay on the platform until you remove them there.

7. Connected AI apps (MCP) and the API

Bentokai includes a connector based on the Model Context Protocol (MCP), an open standard through which an AI app, such as an AI assistant, can work with the data of another service on a person's behalf. Through it, a user can let an AI app of their own choice search and read a brand's contacts, with their tags and the notes that user can read, and, if the user allows it, create and update contacts and add notes to them. The app can also read the reports of a brand's web analytics: totals about the visits to its website, never a single visitor's. It can also read a brand's uptime monitoring (its monitors, with their checks and uptime, its incidents with their notes, its maintenance windows and its status pages) and, if the user allows it, pause, resume and check monitors and acknowledge, assign and resolve incidents and add internal notes to them. It never publishes anything on a status page or sends anything to the people subscribed to one, but pausing a monitor shows it as unknown on the status pages that list it, and resolving a public incident shows it as resolved there. It can also read a brand's site-speed measurements (its sites' addresses, their lab scores and the figures its visitors' browsers report about how fast its pages load, the suggestions to make them faster, its speed reports, deploy markers and speed alerts) and, if the user allows it, pause and resume the measuring of a site, measure a site now and add and delete deploy markers. Pausing a site also closes its open speed alerts, and measuring a site now uses a limited number of measurements shared with the rest of Bentokai. It can also read a brand's projects (their names, codes, dates, status and descriptions; their tasks with their titles, descriptions, dates, estimates and assignees' names; their comments, including the names of clients who wrote through the client portal; their statuses; the names and roles of their team members; their roadmap; the hours logged on them, with the person, the date, the duration, the note and whether they are billable; and their budget summary) and, if the user allows it, create and change tasks, move them, add comments and log hours. Comments added this way are internal unless the app says otherwise, and these changes notify the project's team as Bentokai itself does. It can also read a brand's site-search analytics (the names of its search connections and of the indexes they track, the terms visitors typed into the site's search and how many times each was searched, the searches that found nothing, the indexes' sizes, and the search server's performance and health) and, if the user allows it, sync a search connection now. It never learns who searched, although a search term can contain personal data if a visitor typed it, and a sync reads the brand's own search server and is limited to a few each hour. Today the connector serves the contacts directory, the web analytics, the uptime monitoring, the site-speed measurements, the projects and the site-search analytics, and it cannot change anything in the web analytics. It cannot delete a contact or a note, but an update it makes can remove information from a contact, for example by clearing a field. How we handle the data involved is described in the Privacy Policy (sections 2, 5, 6, 7, 8 and 9).

Switching it on. The connector is off for each brand until you, or we at your written request, switch it on for that brand's contacts directory, its web analytics, its uptime monitoring, its site-speed measurements, its projects, its site-search analytics, or several of them; we never switch it on without such a request, and whoever switches it on is asked to confirm their identity again. Either way, switching it on for a service is your instruction to let the users of your account who have access to that service on that brand connect AI apps to it, and to answer those apps' requests as this section describes. Switching it off, or switching off that service for that brand, stops every connected app from reaching that service on that brand from its next request.

Connecting an app. Each user decides whether to connect an AI app, and which one. The user starts the connection from the app, signs in to Bentokai and approves it on Bentokai's own consent screen, which names the app, says where it will return, lists the brands it can reach and lets the user refuse it permission to make changes. The app then acts on that user's behalf and never with more than that user's own permissions: it reaches only the brands of your account on which the connector is on and, on each of them, only the services the connector is on for and that user can view, and it can make changes only where that user can edit the contacts, or the monitors or incidents of the uptime monitoring, or the sites of the site-speed measurements, or the projects, or the search connections of the site-search analytics, and allowed changes when connecting it. The app, and the company that provides it, are chosen by your user, not by us. Their use is governed by that company's own terms and privacy policy, which apply between that company and you or your user. Bentokai does not review or endorse any AI app, does not guarantee that a particular app works with the connector, and is not responsible for any app or for its provider.

What an app does in your name. A connected app acts in the name of the user who connected it, and you are responsible for what it does in Bentokai as you are for that user's own activity (section 3). AI apps can misunderstand a request, rely on wrong information or make changes the user did not intend, and the changes an app makes are saved as soon as it makes them. Check them before relying on them, as sections 4 and 9 require, and connect an app without permission to make changes where reading is enough. Every change an app makes is recorded in the activity log in the name of the user who connected it, marked with the app's name (for example, "MCP · Claude"). What an app reads is not recorded there request by request; the user's Security page shows when each connection was last used.

The data you share with an app. Whatever a connected app reads, including the personal data of your contacts, goes to that app and to the company that provides it, which may process it outside the European Economic Area. Bentokai sends it only in answer to the app's requests through a connection your user approved, never on its own initiative. Once sent, it is governed by the provider's terms, and disconnecting the app does not delete it. For that personal data you are the controller (section 12). You are responsible for having a legal basis for disclosing it to the provider of the app, for informing the people concerned as the law requires and, where the law requires it, for having your own agreement with that provider, such as a data processing agreement. Bentokai does not let you restrict which apps your users connect, so switch the connector on only if your users may share the brand's contacts with the AI apps they choose, and tell them which apps they may use. For the web analytics, what an app reads is aggregate data about the visits to your website: counts and percentages by page, source, place and device, and the addresses of the links your visitors clicked, as their browsers reported them, which can be web addresses, email addresses (mailto: links) or phone numbers (tel: and sms: links). It identifies no visitor, although a page's title, or an address of your website or of a clicked link, can itself contain information about a person if your website puts it there. For the uptime monitoring, what an app reads is the names and targets of your monitors, their states, checks and uptime, your incidents with the notes your users wrote on them and the names of the staff who wrote them, acknowledged an incident or were assigned to one, and, where you allow changes, of the staff who could be assigned one, your maintenance windows and your status pages; those notes can contain personal data if your users put it there. For the site-speed measurements, what an app reads is the names and addresses of your sites, their scores and measurements, the suggestions to improve them, the figures your visitors' browsers report about how fast your pages load, your deploy markers and your speed alerts; it identifies no visitor, although an address of your website can itself contain information about a person if your website puts it there. For the projects, what an app reads is their names, codes, dates, status and descriptions, their tasks, their comments (including the names of clients who wrote through the client portal), their statuses, the names and roles of their team members, their roadmap, the hours logged on them and their budget summary (the invoiced and spent amounts only where the user can see the services that hold them). For the site-search analytics, what an app reads is the names of your search connections and of the indexes they track, the terms your visitors typed into your website's search and how many times each was searched, the indexes' sizes and your search server's performance and health; it identifies no visitor, although a search term can itself contain personal data if a visitor typed it.

Security, limits and changes. Treat a connected app like any other way into your account: connect only apps you trust, and disconnect the ones you no longer use. Each user sees and ends their own connections on their Security page; to end all of a user's connections at once, whoever manages your users can sign that user out everywhere. Each connection lasts at most 90 days, after which the app has to be connected again, and it ends earlier in the cases described in section 8 of the Privacy Policy, for example when the user's password is reset or changed. We apply rate limits to the connector, and we may limit, suspend or end any connection, or stop answering an app, to protect the service, your data or other users, or if these terms are breached. The connector and the protocol it is based on are new and still evolving: we may change what the connector offers, or withdraw it, as described in section 14.

The API

Bentokai also offers an API: an interface through which your own software, or software run for you, can read a brand's contacts, with their tags and the notes visible to everyone in the brand, and, if you allow it, create, change and delete contacts and add notes to them, and can read the reports of its web analytics, and can read its uptime monitoring and, if you allow it, pause, resume and check monitors and acknowledge, assign and resolve incidents and add internal notes to them, and can read its site-speed measurements and, if you allow it, pause and resume the measuring of a site, measure a site now and add and delete deploy markers, and can read its projects and, if you allow it, create and change tasks, add comments and log hours for a member of a project's team, and can read its site-search analytics and, if you allow it, sync a search connection now, using an API key of that brand. Today the API serves the contacts directory, the web analytics, the uptime monitoring, the site-speed measurements, the projects and the site-search analytics, and it cannot change anything in the web analytics. Syncing a search connection through it reads your search server and counts against a small hourly limit shared with Bentokai itself. Nothing done through it publishes anything on a status page or sends anything to the people subscribed to one, but pausing a monitor shows it as unknown on the status pages that list it, and resolving a public incident shows it as resolved there. Pausing a site through it closes the site's open speed alerts, and measuring a site now uses a limited number of measurements shared with the rest of Bentokai. A comment your software adds is internal unless it says otherwise, and it shows the API key's name as its author. Unlike the connector described above, a key acts as the brand rather than as one of your users, and it can delete contacts. While an invoice or credit note that has been issued names a contact, that contact cannot be deleted on its own, whether with a key or in Bentokai itself; drafts do not prevent it. How the API works is described in the Documentation & API section of the Help center, and how we handle the data involved in the Privacy Policy (sections 2, 5, 6, 8 and 9).

Switching it on and creating keys. The API is off for each brand until whoever manages the brand in Bentokai switches it on for that brand's contacts directory, its web analytics, its uptime monitoring, its site-speed measurements, its projects, its site-search analytics, or several of them. Keys are created on the brand's page by whoever manages the brand, who is asked to confirm their identity each time; we create one only at your written request, and never without such a request. Together, switching the API on and creating a key are your instruction to answer the requests made with that key as this section describes. Each key gives, for each service, no access, read access or, for the contacts directory, the uptime monitoring, the site-speed measurements, the projects and the site-search analytics, read and change access, chosen when it is created; a key never gains access to a service it was not given. A key may also be given an expiry when it is created, after which it stops working; otherwise it works until it is revoked. Switching the API off for a service, or switching off that service for that brand, stops every key of that brand from reaching that service from its next request; the keys are kept, and they reach it again once the API is switched back on for it. A key belongs to the brand, not to the person who created it: it keeps working when that person leaves your organisation or loses their access to Bentokai. The brand's page shows who created each key and marks a key whose creator has been deactivated or deleted, or no longer belongs to your account; a creator who leaves your organisation but remains an active user of your account is not marked.

The data your software receives. What your software reads through a key, including the personal data of your contacts, leaves Bentokai for the systems that send the requests, which you choose and run, yourself or through your providers. Bentokai sends it only in answer to requests made with a key of yours, never on its own initiative. For that personal data you are the controller (section 12), and you are responsible for those systems and for what they do with it. For the web analytics, what your software reads is aggregate data about the visits to your website: counts and percentages by page, source, place and device, and the addresses of the links your visitors clicked, as their browsers reported them, which can be web addresses, email addresses (mailto: links) or phone numbers (tel: and sms: links). It identifies no visitor, although a page's title, or an address of your website or of a clicked link, can itself contain information about a person if your website puts it there. For the uptime monitoring, what your software reads is the names and targets of your monitors, their states, checks and uptime, your incidents with the notes your users wrote on them and the names of the staff who wrote them, acknowledged an incident or were assigned to one, and, where you allow changes, of the staff who could be assigned one, your maintenance windows and your status pages; those notes can contain personal data if your users put it there. For the site-speed measurements, what your software reads is the names and addresses of your sites, their scores and measurements, the suggestions to improve them, the figures your visitors' browsers report about how fast your pages load, your deploy markers and your speed alerts; it identifies no visitor, although an address of your website can itself contain information about a person if your website puts it there. For the projects, what your software reads is their names, codes, dates, status and descriptions, their tasks, their comments (including the names of clients who wrote through the client portal), their statuses, the names and roles of their team members, their roadmap, the hours logged on them and their budget summary; through the API the budget summary leaves out the invoiced and spent amounts. For the site-search analytics, what your software reads is the names of your search connections and of the indexes they track, the terms your visitors typed into your website's search and how many times each was searched, the indexes' sizes and your search server's performance and health; it identifies no visitor, although a search term can itself contain personal data if a visitor typed it.

Keeping keys safe. A key is a credential of yours: whoever holds it can do everything it allows, without signing in. It is shown only once, when it is created. Keep it secret, give it only to the people and systems that run your integration, keep it out of web pages, of apps you distribute, of public repositories and of web addresses, and revoke it at once on the brand's page if it may have been exposed or when someone who had it leaves. The API is served only over HTTPS: a request sent over plain HTTP is refused, and a key sent that way must be revoked. You are responsible for everything done with your keys as you are for your users' own activity (section 3). Every change made with a key is recorded in the activity log in the name of the person who created the key, marked with the key's name. What a key reads is not recorded there request by request; the brand's page shows when each key was last used and from which IP address.

Limits and changes. We apply rate limits to each key and limit the number of keys a brand can have, as the documentation describes, and we may suspend a key, or the API for a brand, to protect the service, your data or other customers, or if these terms are breached. We may change the API, or withdraw it, as described in section 14. We may add to it at any time, for example new fields or error codes, and your software must ignore what it does not recognise. For as long as we offer the API, a change that could break an existing integration will come as a new version, with the previous one kept running for a deprecation period announced in the documentation.

8. Invoicing and tax compliance

The invoicing, accounting and tax features are designed to help you meet the rules that apply to your business (including, where you activate it, the generation of verifiable billing records under Spanish regulations), but using them does not by itself make you compliant. You are the issuer of your invoices and the party responsible for your accounting and tax obligations: the correctness, completeness and timely filing of invoices, ledgers and tax returns remain your responsibility. Deadlines and calendar information shown in the platform are informational and may not reflect every rule that applies to your case; verify them against official sources or your advisor.

9. Automated processing and AI features

Some features process your documents or text automatically, for example extracting invoice fields from an imported PDF or translating catalog and help content, using third-party AI providers as described in the Privacy Policy. Automated output can be wrong or incomplete. It is always presented for your review, and you must check it before saving, issuing or otherwise relying on it. This section covers Bentokai's own features. An AI app that you or your users connect (section 7) is not one of them: the changes it makes are saved without first being presented for review, so check them afterwards.

10. Acceptable use

You agree not to misuse the service, and to make sure that your users do not. In particular, you must not:

11. Your data and privacy

Our handling of personal data is described in our Privacy Policy, which forms part of these terms. Where we process personal data on your behalf, section 12 applies.

12. Processing personal data on your behalf (data processing agreement)

This section is the contract required by Article 28 of the General Data Protection Regulation (GDPR) and Article 33 of Spanish Organic Law 3/2018. It applies wherever Umai Media processes personal data as a processor on behalf of the business customer that holds the Bentokai account ("you", as controller). In particular, it covers the personal data of other people that you and your users store in Bentokai, such as your contacts, the customers and suppliers in your invoices and other records, and the counterparties in the bank transactions you import; and the personal data of other people that reaches Bentokai through your connected social media profiles, such as the names and content in the comments, reviews and messages received in the inbox and the content of the posts whose statistics Bentokai shows; and the data about the people you serve through Bentokai: the visitors to your websites, the people who search on them, and the people who subscribe to your status pages or use your support and project portals, as described in section 2 of the Privacy Policy. The processing we carry out as controller is described in the Privacy Policy. For the processing covered here, this section prevails over any other provision of these terms.

13. Intellectual property

The Bentokai platform (its software, design and branding) is and remains the property of Umai Media, S.L. You retain ownership of the content and data you bring into the platform, and you grant us only the rights needed to host, process and display it in order to provide the service to you. When you or your users publish a post or send a reply through Bentokai, you also grant us the rights needed to reproduce it, adapt it technically to each platform's requirements (for example, by converting or resizing images and videos) and transmit it to the platforms you chose. Once content is on a platform, its use there is governed by that platform's terms, including the licence you grant the platform.

14. Availability and changes

We aim to keep the service available and reliable but do not guarantee uninterrupted access, and we may suspend the service for maintenance or security reasons. We may update, add or remove features, and may revise these terms; material changes will be posted here. Continued use after changes means you accept them.

15. Disclaimers

The service is provided "as is" and "as available", without warranties of any kind, express or implied, including fitness for a particular purpose. Nothing in Bentokai constitutes accounting, tax, legal or financial advice. Financial information shown in Bentokai is imported from third-party providers and your banks, may be delayed, incomplete or inaccurate, and is for informational purposes only. The same applies to social media statistics and other data provided by the platforms, and whether, when and how a post is published, shown or kept is decided by the platform concerned. Calculations, totals, reports, exports and generated documents are produced from the data you enter; verify important figures against your own records before using them.

16. Limitation of liability

To the maximum extent permitted by law, Umai Media, S.L. is not liable for indirect or consequential damages; loss of profits, business or data; penalties or surcharges imposed by tax or other authorities; or any loss arising from decisions you make based on information shown in the platform, from data you did not review as described in section 4, from the availability, accuracy or timeliness of data provided by banks or third-party providers, from the actions, decisions or outages of social media platforms (including rejected, delayed or removed posts, restricted or suspended profiles or accounts, changes to or withdrawal of their APIs, request limits, and data they provide late, incomplete or not at all), from what an AI app that you or your users connect does in Bentokai or with the data it receives, or from retrying a post, or sending a reply again, that Bentokai reported it could not confirm as published, without first checking the platform. To the same extent, Umai Media, S.L.'s total aggregate liability under these terms is limited to the amounts you paid for the service in the twelve months before the event giving rise to the claim. Nothing in these terms excludes liability that cannot be excluded under applicable law.

17. Termination

You may stop using the service and request deletion of your account at any time. We may suspend or terminate access if these terms are breached or where required to protect the service or comply with the law. When the service ends, the personal data we process on your behalf is returned or deleted as described in section 12.

18. Governing law and jurisdiction

These terms are governed by the laws of Spain. Any dispute arising from them is subject to the courts of the city of Madrid, without prejudice to any mandatory consumer or data-protection rights you may have under your local law.

19. Contact

Questions about these terms: legal@bentokai.com.