Last updated 11 October 2026
1. Introduction and definitions
1.1This Privacy Policy describes how US Global Consultancy FZE, trading as FinOps Robotics (“FinOps Robotics”, “we”, “us” or “our”), collects, uses, discloses, retains and protects personal data in connection with the Website and the Service. It also describes the rights available to the individuals concerned.
1.2In this Policy:
- “Agreement” means the agreement between us and a Client under which the Service is provided, including any engagement letter, subscription terms and data processing agreement (“DPA”).
- “App” means the FinOps Robotics web application at app.finopsrobotics.com and the FinOps Robotics mobile applications distributed through Google Play and the App Store.
- “Client” means a business or other organisation that has entered into an Agreement with us.
- “Client Data” means all data, including personal data, that a Client or its Users submit to the Service, or that the Service obtains from a Connected Service on the Client’s instructions, including documents, invoices, email messages and accounting records.
- “Connected Service” means a third-party service that a Client chooses to connect to the App, including accounting systems, banks and bank-data providers, e-commerce platforms, email accounts, calendars, cloud storage, e-invoicing service providers and professional networking accounts.
- “Data Protection Law” means UAE Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data (the “PDPL”) and, where applicable to the processing concerned, Regulation (EU) 2016/679 (the “GDPR”) and the GDPR as it forms part of the law of the United Kingdom (the “UK GDPR”).
- “Engagement” means professional services under which we design and build automation within a Client’s own systems.
- “Service” means the App, the automated agents (“bots”) made available through it and any Engagement.
- “Sub-processor” means a third party engaged by us to process personal data on our behalf in connection with the Website or the Service.
- “User” means an individual authorised by a Client to access the App.
- “Website” means finopsrobotics.com, including its translated versions, its booking form and its chat.
1.3The terms “personal data”, “processing”, “controller” and “processor” have the meanings given to them, or to their equivalents, in the Data Protection Law.
2. Who we are and our role
2.1FinOps Robotics is a venture of US Global Consultancy FZE, a company registered in the United Arab Emirates. Requests and questions concerning this Policy may be sent to [email protected], where each is read and answered by a member of our staff.
2.2Controller. We act as controller of the personal data that we process for our own purposes: data collected through the Website; enquiries and correspondence; User account and security data; and billing records.
2.3Processor. In respect of Client Data, the Client is the controller and we act as its processor. We process Client Data only on the Client’s documented instructions (as set out in the Agreement and as given through the settings of the App) and not for our own purposes. An individual whose personal data forms part of Client Data should address any request to the Client concerned; we will assist the Client in responding to it.
2.4Engagements. Where an Engagement is performed within the Client’s own systems, the Client’s accounting records, documents and master data remain in those systems, under access credentials that the Client issues and may revoke at any time without reference to us. Any processing step that cannot be performed within the Client’s environment is identified in the solution design (the “blueprint”) before the Client approves it, together with the data concerned, the reason and the duration. Processing under an Engagement is governed by the engagement letter and the DPA.
2.5The App. Where a Client uses the App, the bots process Client Data within the Service and post entries to the Client’s own accounting system. Certain Client Data is retained by us, to the extent determined by the document policy that the Client selects (section 5).
3. Personal data we process
3.1Website. Through the Website we collect only the following:
- Enquiry data: the information submitted through the booking form or the chat, namely name, work email address and company, the bot or accounting system of interest, the preferred time for contact and any information provided about the enquirer’s processes and workload.
- Correspondence: emails and instant messages sent to us and their attachments.
- Usage data: the pages viewed, the actions taken, the referring website, the approximate location (country, region and town) indicated by the visitor’s network and the type of device. This data is collected using Google Analytics 4 where you have given consent; analytics cookies are set only after you accept the cookie notice on your first visit.
3.2We do not use advertising pixels, do not purchase or enrich contact data, do not compile profiles of individuals from other sources and do not share Website data with any advertising network.
3.3The App: Users. In respect of Users we process:
- Account data: name, work email address and the workspace to which the User belongs; the password, stored only as a one-way hash from which it cannot be recovered; and the key used for two-step verification. Accounts are created only by invitation from the Client; there is no public registration.
- Security data: the IP address of each sign-in, held with the session it opens and, for fifteen minutes, in the control that limits repeated failed sign-in attempts. It is not used to determine the User’s location.
- Notification data, where the User enables notifications: a mobile telephone number for messaging notifications and the notification address of the User’s device.
- Billing data: billing name and email address, workspace identifier and subscription details. Payment card details are entered directly with our payment processor and are not received by us.
3.4The App: Client Data. In providing the App we process the following categories of Client Data:
- Credentials for each Connected Service, encrypted before they are stored.
- Prepared entries: for each bill that a bot prepares, the supplier, the lines, the amounts and tax, the dates, the reference and purchase order, the supplier’s bank details, the sender’s email address and the subject line, the checks applied, the file name and location of the document where it is filed, together with a record of who prepared, amended, approved or overrode the entry and when. Entries are not deleted on a schedule: they prevent an entry already recorded in the Client’s accounting system from being posted twice and they constitute the record of the actions taken by the Service.
- Operating data: a copy of the lists held in the Client’s accounting system (such as the chart of accounts, suppliers and customers), refreshed from that system, together with a summary of open items retained for two days; for each supplier, the supplier’s name and the layout of its invoices; patterns learned from the Client’s invoices (which do not identify suppliers) and any instruction a User gives a bot, in the form given; the most recent 300 messages of each chat with a bot; and a 30-day log of each bot’s activity.
- Mailbox data, where a mailbox is connected: for each message read, the information derived from it (its category and the reasons for it, dates, amounts and references, the sender’s address and the subject line); the association of sender addresses with suppliers (the most recent 500); the identifiers of messages awaiting a label; a log of the most recent 40 errors encountered in reading the mailbox; for a mailbox accessed by IMAP, a record of the folder into which each message was sorted; and the Client’s mailbox rules and category settings. Under the hosted policy the message as read is also retained (section 5.2). Disconnecting the mailbox deletes every message record.
- Calendar data: for each meeting or deadline identified in email, its date and time, its type, the sender’s name and address, the subject line, the sentence from which the date was read, the messages from which it came, its entry on the Service’s calendar and the reminders sent; and the most recent 500 senders whose meetings a User has accepted.
- Documents and readings, to the extent determined by the document policy (section 5).
3.5Mobile applications. The mobile applications provide the same Service and process the same data. In addition, a photograph of a document taken by a User is uploaded as a document; where notifications are enabled, the device’s notification address is retained; and where a User dictates in a chat, the device’s own speech service converts the speech to text and only the text is received by us. The mobile applications contain no advertising, analytics or crash-reporting components and do not collect location, contacts or browsing history.
4. Purposes and lawful bases
4.1We process personal data for the following purposes and on the following bases, as recognised by the Data Protection Law applicable to the processing:
4.2Submitting an enquiry does not subscribe the enquirer to any mailing list. Should we introduce marketing communications, we will obtain consent before sending them.
5. Client Data: document policies
5.1Each workspace in the App operates under one of two document policies, selected by the Client. Under either policy, entries are posted to the Client’s own accounting system. In the App, the Settings › Your data screen lists, policy by policy, every category of data retained.
5.2Hosted policy (the policy on which a workspace starts). Where the Client has not connected cloud storage of its own, we retain the documents processed by the Service, so as to provide the Client with a searchable record supported by the underlying documents. Under this policy:
- each document is retained for the period required by the tax law applicable to the Client: for a Client in the United Arab Emirates, seven years after the end of the tax period to which the document relates (Federal Decree-Law No. 47 of 2022, Article 56), after which it is deleted. Until the Client’s tax period is known, the period is measured from the date on which the document was filed, plus eighteen months, so that a document may be retained for up to eighteen months longer than the law requires but never for a shorter period. Where a longer statutory period applies to the Client and the Client so notifies us, the longer period is applied;
- where no retention period has yet been established for the Client’s jurisdiction, documents are retained until the Client requests their removal or deletes the workspace;
- the full reading of each invoice (the supplier, amounts, tax and line items), together with the sender, the subject line and the file name, is retained for 400 days;
- where a mailbox is connected, the message as read (the first 8,000 characters of its text, the sender’s name, the recipients named in the “To” line, the names of its attachments, of the copy line only the addresses on the Client’s own domain and the number of other addresses, plus five indicators drawn from its headers) is retained for 400 days after it was read; and
- the invoice register (one line for each invoice, recording its supplier, number, amounts, tax, the checks it passed, the posting made and the answers given by the Client’s personnel) is not deleted on a schedule.
5.3The Client’s own storage. Where the Client connects its own cloud storage, original documents are filed in that storage and are not retained by us. Under either policy, a document is accessible only to Users signed in to the Client’s workspace; no shareable link to a document is created.
5.4Documents-not-retained policy. Under this policy neither documents nor the stored readings of invoices are retained: each document is processed and then discarded; where the Client’s own storage is connected, the document is filed there in the course of processing. For each document we retain one register line and one processing marker, neither of which identifies a supplier or an amount; and of a mailbox message, only the information derived from it and never its text. The other data described in section 3.4 continue to be retained, as the Service cannot operate without them. Duplicate detection is more limited under this policy: an identical file received twice is identified, but a new invoice cannot be compared with invoices read previously. A change to this policy does not alter records made before the change; the App’s “Delete what is stored” function deletes the stored readings and the documents only.
6. Use of artificial intelligence
6.1The Service uses artificial intelligence to read documents and images and extract the information they contain, to classify documents and email messages, to suggest accounting treatment and to generate the bots’ responses in chat. Extracted information is subject to automated validation checks, including arithmetic checks. A reading that fails them is held for review. Entries are posted to the Client’s accounting system only on the approval of a User or under a standing approval that a User has given in the App’s settings for defined circumstances, which is disabled unless a User enables it.
6.2For these purposes, Client Data is transmitted to artificial-intelligence service providers engaged as Sub-processors, solely to obtain the result for the Client and under terms that prohibit the provider from using Client Data to train its models.
6.3We do not use Client Data to develop, improve or train generalised artificial-intelligence or machine-learning models. Information that the Service derives from a Client’s own documents and instructions, such as the layout of a supplier’s invoices and learned coding patterns, is held within that Client’s workspace and used only to provide the Service to that Client.
6.4The Service does not make decisions based solely on automated processing that produce legal effects concerning an individual or similarly significantly affect an individual.
7. Disclosure of personal data
7.1We do not sell personal data and do not disclose it to any third party for that party’s own purposes, including advertising.
7.2Personal data is disclosed only:
- to Sub-processors in the categories described in the Sub-processors schedule and only to the extent necessary for them to perform their services for us;
- to Connected Services, as instructed by the Client. A Connected Service is engaged by the Client under the Client’s own account and terms with its provider, receives only the data that the Client instructs the bots to send to it and is not our Sub-processor; and
- to a competent authority, where we are required to do so by a valid legal order. We do not disclose personal data in response to an informal request and, unless we are legally prohibited from doing so, we will inform the affected Client of the disclosure.
8. Google user data
8.1This section applies where a User connects a Google account to the App. The Service then accesses the following data through Google APIs, with the User’s authorisation:
- Gmail: the email address of the connected account; the messages in the connected mailbox, including their headers, body text and attachments; and the mailbox’s labels. The Service creates labels and applies them to messages in accordance with the Client’s mailbox rules. It does not send, delete or archive messages and does not remove labels.
- Google Drive: only the files that the Service itself creates in the User’s Drive, being the documents it files there, which it may open again to display them to Users. The Service has no access to any other file in the User’s Drive.
- Google Calendar: only a calendar that the Service creates, on which it creates, amends and removes entries for the meetings and deadlines identified in email. The Service has no access to any other calendar of the User.
8.2Google user data is used only to provide and improve the user-facing features of the Service that the User has chosen to use: identifying invoices and other documents received by email, extracting their contents and preparing entries; sorting and labelling the mailbox; filing documents in the User’s Drive; and recording meetings and deadlines on the Service’s calendar.
8.3FinOps Robotics’ use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular:
- we transfer Google user data to third parties only as necessary to provide or improve those features (including to the Sub-processors that host the Service and read documents), to comply with applicable law or for security purposes;
- we do not sell Google user data and do not use or transfer it to serve advertisements, including personalised, retargeted or interest-based advertisements, or to determine creditworthiness or for lending purposes;
- we do not allow any person to read Google user data unless (i) the User has given affirmative agreement for specific messages, files or other data, (ii) it is necessary for security purposes, such as investigating abuse, (iii) it is necessary to comply with applicable law or (iv) the data has been aggregated and anonymised and is used for our internal operations; and
- we do not use Google user data to develop, improve or train generalised artificial-intelligence or machine-learning models and do not permit our Sub-processors to use it for that purpose.
8.4Google user data is retained as described in sections 5 and 11. A User may disconnect the Google account in the App at any time, whereupon the stored credentials are deleted and, in the case of a mailbox, every message record is deleted. Access may also be revoked at any time from the permissions page of the User’s Google Account.
9. International transfers
9.1We are established in the United Arab Emirates and serve Clients in other jurisdictions. Our Sub-processors operate infrastructure in several countries and the processing of personal data is not confined to a particular country. Personal data may therefore be processed in countries other than the one in which it was collected, including countries outside the United Arab Emirates, the European Economic Area and the United Kingdom.
9.2Where personal data is transferred across borders, we rely on the transfer mechanisms permitted by the Data Protection Law. For personal data subject to the GDPR or the UK GDPR, transfers are made subject to appropriate safeguards under Article 46 of the GDPR or the corresponding provision of the UK GDPR, which, for Clients, are specified in the DPA.
10. Security
10.1We implement technical and organisational measures appropriate to the risk of the processing. These include two-step verification for every App account; storage of passwords in hashed form only; encryption of the credentials for Connected Services; logical separation of each Client’s data; access to documents only by Users signed in to the workspace concerned; and, within our organisation, multi-factor authentication, credentials held in a managed vault rather than in email, encrypted devices, no Client Data on personal devices and access limited to what each task requires.
10.2If we become aware of a personal data breach affecting Client Data, we will notify the affected Client without undue delay and in any event within 72 hours of becoming aware of it, stating the data affected and the measures taken.
11. Retention and deletion
11.1Website data. Enquiry data is retained for 24 months, so that a returning enquirer can be recognised. It is then deleted. On request we will delete it sooner (within 30 days) and confirm the deletion. Records of an Engagement are retained for the period specified in the engagement letter and for any statutory retention period that applies to them.
11.2App data. Data in the App is retained for the following periods:
11.3Deletion of an App account. A User may delete an account in the App under Account › Delete account. Instructions for requesting deletion without the App are published at app.finopsrobotics.com/delete-account; a request may also be sent to [email protected] from the address registered to the account and will be completed within 30 days. Deletion requires the User’s password and a two-step verification code and, before it proceeds, the invoice register and the documents held by us are offered for download. In the United Arab Emirates a business must keep its tax records for seven years after the end of the tax period to which they relate; that obligation rests with the Client.
- Where other Users remain in the workspace, only the departing User’s sign-in, open sessions and device notifications are deleted. The User’s name remains on the actions recorded in the workspace, so that the audit trail remains complete.
- Where the User is the last User in the workspace, the workspace is deleted with the account. Immediately: every sign-in, session and pending invitation, every credential for a Connected Service, the device notifications and the Client’s subscriptions, which are cancelled through our payment processor so that none renews. No refund or credit is given for the unused part of a period already paid. After 24 hours: all other data in the workspace, including documents, the invoice register, prepared entries, mailbox and calendar records, settings, chats, history and learned data; the interval allows the payment processor to confirm the cancellation. Deletion is completed within 48 hours of the request.
- Retained after deletion: entries already posted to the Client’s accounting system and files in the Client’s own storage, which are held in the Client’s own systems; the invoices we issued and the payments made against them, held by our payment processor, which we are required by tax law to retain; and, for 90 days, a record that the workspace was deleted, comprising its identifier and the relevant dates only.
12. Your rights
12.1Subject to the conditions and exceptions set out in the Data Protection Law, an individual has the right to obtain information about the personal data we hold about them and a copy of it; to have inaccurate personal data corrected; to have personal data erased; to restrict processing; to object to processing; to receive personal data in a structured, machine-readable format and have it transmitted to another controller; to object to decisions based solely on automated processing; and to withdraw consent at any time, without affecting the lawfulness of processing carried out before its withdrawal.
12.2These rights arise under the PDPL and, where applicable, the GDPR and the UK GDPR. Requests may be sent to [email protected] and will be answered within 30 days, free of charge. We may need to verify the identity of the person making a request. Requests concerning Client Data are handled as described in section 2.3.
12.3An individual who is dissatisfied with our response may lodge a complaint with the competent supervisory authority, including the UAE Data Office, the Information Commissioner’s Office in the United Kingdom or the supervisory authority of the individual’s place of residence or work in the European Economic Area.
13. Cookies and similar technologies
13.1Website. The Website stores in the visitor’s browser the
visitor’s choice of language, their cookie consent decision and, for the duration of the browser
session, whether a prompt has been dismissed. Where you have given consent, the Website also sets
Google Analytics cookies (_ga, _ga_64DZ9JEQBM) that persist for up to
13 months and are used to measure aggregate Website use. You may withdraw consent at any time by
clearing your browser cookies or using your browser’s cookie controls; analytics cookies will
not be re-set until you give consent again.
13.2App. The App uses only cookies that are strictly necessary to provide the Service: to maintain a signed-in session, to complete two-step sign-in and to allow a device to retrieve a notification. It also stores interface preferences, such as the display theme, in the User’s browser. The App uses no advertising or analytics cookies.
14. Children
14.1The Website and the Service are intended for businesses and their personnel and are not directed at individuals under the age of 18. We do not knowingly collect personal data from children and will delete any such data of which we become aware.
15. Changes to this Policy
15.1We may amend this Policy from time to time. The amended Policy will be published on this page with a revised date. Where an amendment is material, we will inform by email each person whose enquiry we hold and will inform Clients in accordance with the Agreement.
16. Contact
16.1US Global Consultancy FZE, trading as FinOps Robotics, United Arab Emirates. Email: [email protected].