Privacy Policy

DeepRevise - Privacy Policy Hudraq Technologies LLC 1. Introduction This Privacy Policy explains how Hudraq Technologies LLC, a Wyoming limited liability company with its registered office at 5830 E 2nd St, Ste 7000 #37629, Casper, Wyoming 82609, United States ("Hudraq", "we", "us", "our"), collects, uses, discloses, transfers, retains and protects personal data in connection with the DeepRevise service, our website at www.deeprevise.com, and related communications (together, the "Service"). DeepRevise is a product of Hudraq Technologies LLC, operated at www.deeprevise.com. Further information about the company is available at www.hudraq.com. DeepRevise is a business-to-business document assembly platform. Companies use it to store a library of technical and company documents and to compile them into formatted submittal packages. It is not intended for personal, family or household use. This Policy forms part of, and should be read together with, our Terms of Service. Summary of the key points: We do not sell personal data, and we do not share it for advertising. We do not use artificial intelligence or optical character recognition to read or interpret your documents. Accounts are individual. Nobody else can see your documents unless you choose to share them. We use third-party providers for hosting, payments, email delivery and error monitoring; they are listed in clause 6. You have rights over your data, described in clause 11. 2. Our roles Our responsibilities differ depending on the data involved. 2.1 Data we hold about you as a customer We act as controller (or the equivalent role under applicable law) for the personal data we collect to run our business and operate the Service: account registration data, billing and subscription records, support correspondence, website visitor data, and technical and usage logs. For this data we decide the purposes and means of processing, and this Policy describes what we do. 2.2 Documents you upload Accounts on DeepRevise are individual. There is no organisation account and no administrator who controls other people's content. Each account holder decides what to upload, what to keep, what to share and what to delete. Where documents you upload contain personal data - for example names and signatures on authorisation letters, certificates, transmittals and test reports - you decide what goes in and why. We store and assemble that material on your instruction and do not use it for any purpose of our own. Where applicable data protection law treats this as a controller-processor relationship, you are the controller and we are the processor. If you require a written data processing agreement to meet an obligation under applicable data protection law, contact us at info@deeprevise.com. If you use the Service on behalf of your employer, the arrangements between you and your employer are a matter for you and them; we contract with the account holder. If you are an individual whose personal data appears in a document held in someone else's account, we usually have no way to identify you or to know which account holds that document. Contact the person or business that uploaded it. If you contact us, we will help where we reasonably can, but we cannot search customer accounts on request without a lawful basis for doing so. 2.3 Payment data Hudraq is the seller of record for subscriptions. Payments are processed by Stripe, Inc., which handles your card details directly - we never receive or store them. Stripe processes payment data on our behalf for the purpose of taking payment, and also as a controller in its own right for its own fraud prevention, anti-money-laundering and regulatory compliance purposes, under its own privacy policy. We receive from Stripe only the subscription and payment status information described in clause 3.3. 3. Personal data we collect 3.1 Data you provide Category: Account data | Examples: Full name, business email address, and password (stored only as a salted cryptographic hash) | Our role: Controller Category: Company details | Examples: Company name, address, country, company logo and tax details, where you supply them for use on your documents or for billing | Our role: Controller Category: Subscription and billing records | Examples: Plan, term, quota consumption, subscription status, renewal and cancellation dates, billing address, tax registration or VAT number where supplied, invoices we issue, and the partial payment identifiers reported to us by the payment processor (such as card brand and last four digits) | Our role: Controller Category: Sharing data | Examples: The accounts you share documents or folders with, the contacts you add, and the status of those shares | Our role: Controller Category: Acceptance records | Examples: The version of the Terms of Service and Privacy Policy you accepted, the date and time you accepted them, and the IP address and browser user-agent recorded at that moment | Our role: Controller Category: Support and communications data | Examples: Messages, attachments, screenshots, bug reports and correspondence you send to our support, sales or legal channels | Our role: Controller Category: Marketing data | Examples: Email address and preferences where you subscribe to updates, and your consent status | Our role: Controller Category: Customer Content | Examples: Documents, datasheets, certificates, authorisation letters, warranties, test reports, company documents, spreadsheets, bills of quantities, specification documents, project names, consultant and contractor names, and any personal data they happen to contain | Our role: Processor We do not collect or store full payment card numbers, security codes or bank credentials. Those are collected and processed directly by the payment provider. 3.2 Data collected automatically Category: Technical data | Examples: IP address, browser type and version, operating system, device type, screen characteristics, language settings, time zone | Our role: Controller Category: Usage data | Examples: Pages and screens requested, actions taken, dates and times, referring page, and search terms entered within the Service, as recorded in ordinary server access logs | Our role: Controller Category: Operational and audit logs | Examples: Authentication events, sign-in and sign-out, sharing changes, upload and generation events, job identifiers, processing durations, quota consumption, error traces and stack traces | Our role: Controller Category: Cookie and similar data | Examples: Session identifiers, authentication tokens, preference settings - see clause 10 | Our role: Controller 3.3 Data from third parties We may receive data from: the payment processor (subscription, renewal, refund and payment status, billing country, and the partial card identifiers described above); identity or single sign-on providers where you choose to use them (your name, email address and authentication confirmation); other account holders (when they share a document or folder with you); our email delivery provider (delivery, bounce and complaint status); and publicly available business sources for sales and verification purposes. 3.4 Data we ask you not to submit The Service is not designed for, and must not be used to store, special category or sensitive personal data - including data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic or biometric data, health data, or data concerning sex life or sexual orientation - nor government identifier numbers, financial account numbers, or payment card data. You must not upload such data to the Service. If you do so, you do it at your own risk, contrary to our Terms of Service, and you remain solely responsible for it. 4. Why we use personal data, and our legal bases Where the EU or UK General Data Protection Regulation, or a comparable law, applies, we rely on the following legal bases. Purpose: Create and administer your account; authenticate you | Data used: Account, company details, technical | Legal basis: Performance of a contract Purpose: Provide the Service: store your library, assemble packages, retain generation records | Data used: Account, company details, Customer Content | Legal basis: Performance of a contract; for Customer Content, processed on your instructions Purpose: Operate document and folder sharing between accounts | Data used: Sharing, account | Legal basis: Performance of a contract Purpose: Take payment, issue invoices, manage subscriptions, enforce quotas, determine and account for applicable taxes, and handle billing queries | Data used: Subscription, billing, account, usage | Legal basis: Performance of a contract; compliance with a legal obligation (tax and accounting) Purpose: Provide support and respond to your enquiries | Data used: Support, account, technical, usage | Legal basis: Performance of a contract; legitimate interests in supporting our customers Purpose: Send service and transactional messages: security alerts, billing notices, changes to terms, outage and maintenance notices | Data used: Account, subscription | Legal basis: Performance of a contract; legitimate interests in keeping you informed; compliance with a legal obligation Purpose: Monitor, secure, debug, maintain and improve the Service; detect and prevent fraud, abuse and unauthorised access | Data used: Technical, usage, logs | Legal basis: Legitimate interests in securing and improving our Service; compliance with a legal obligation Purpose: Produce aggregated and de-identified statistics about Service use | Data used: Technical, usage, logs | Legal basis: Legitimate interests in understanding and improving our product Purpose: Send marketing communications about our products | Data used: Marketing, account | Legal basis: Consent, where required; otherwise legitimate interests in promoting our business to business contacts Purpose: Record and evidence your acceptance of our Terms of Service and Privacy Policy, including which version you agreed to and when | Data used: Acceptance records, account | Legal basis: Compliance with a legal obligation; legitimate interests in being able to evidence the terms on which the Service was supplied Purpose: Establish, exercise or defend legal claims; comply with law, regulation, court orders and lawful requests | Data used: Any category as necessary | Legal basis: Compliance with a legal obligation; legitimate interests in protecting our rights Purpose: Effect a merger, acquisition, financing or sale of assets | Data used: Any category as necessary | Legal basis: Legitimate interests in conducting corporate transactions Where we rely on legitimate interests, we have assessed that those interests are not overridden by your rights and freedoms. You may object as described in clause 11, and you may ask us for details of the assessment. Where we rely on consent, you may withdraw it at any time. Withdrawal does not affect the lawfulness of processing before withdrawal. 5. Automated processing The Service uses automated processing to deliver its core function. We want to be explicit about this. 5.1 What happens When documents are uploaded or a package is generated, content may be rendered, converted, split, merged, compressed, paginated and bookmarked, and indexed so that it can be searched by filename and by the details you record against it. 5.2 What does not happen The Service does not currently use artificial intelligence, machine learning or optical character recognition. We do not read, interpret, extract data from, classify or analyse the content inside your documents, and no document content is sent to any artificial intelligence or optical character recognition provider. We do not use Customer Content to train artificial intelligence or machine learning models. We do not sell personal data, and we do not share it for cross-context behavioural advertising. If we introduce features of this kind in future, we will update this Policy and give notice in accordance with clause 14 before doing so. 5.3 No automated decisions with legal effect We do not use automated processing to make decisions producing legal effects concerning you, or similarly significantly affecting you. 6. Who we share personal data with We do not sell personal data. We share it only as described below. 6.1 With other account holders you share with Accounts are individual, and no other customer can see your documents unless you share them. Where you share a document or folder with another account, or add a trusted contact, the recipient can view that content and any personal data it contains. Sharing is your decision, not ours. You should review and remove shares that are no longer needed. 6.2 Service providers and sub-processors We engage third parties to provide the infrastructure and functions the Service depends on. Each processes data for the purposes described below and is subject to the data protection terms it offers to its customers. The payment processor additionally acts as a controller for its own compliance purposes, as described in clause 2.3. Provider category: Cloud database, authentication and object storage | Function: Hosting the application database, user authentication, and storage of uploaded documents and generated packages | Data involved: Account, company details, usage, Customer Content Provider category: Application and compute hosting | Function: Running the web application and the document processing engine | Data involved: Technical, usage, Customer Content in transit and in temporary processing Provider category: Payment processing | Function: Checkout, card processing, recurring charges, refunds, the billing portal, and sending receipts and invoices | Data involved: Card and payment data (handled directly by the processor), billing address, account reference Provider category: Transactional email delivery | Function: Sending account verification, password reset and security emails | Data involved: Account Provider category: Error monitoring and application performance | Function: Diagnosing faults and maintaining reliability across the web application and the processing engine | Data involved: Technical and usage data, error traces, and your account identifier. Email addresses, share identifiers, authentication tokens, document filenames, cookies and authorisation headers are removed before transmission Provider category: Professional advisers | Function: Legal, accounting, audit and insurance services | Data involved: As necessary The providers we currently use are: Supabase (database, file storage and authentication), Vercel (web application hosting), Railway (the document processing engine), Stripe (payments), Sentry (error monitoring), and an email delivery provider for transactional messages. Support is handled by email; we do not use a third-party support platform or a product analytics provider. Contact us at info@deeprevise.com for the current list at any time. Changes to this list. We will give at least thirty (30) days' notice, by email or by notice within the Service, before adding or replacing a provider that processes personal data on your behalf. If you object on reasonable data protection grounds within that period, contact us at info@deeprevise.com and we will discuss it in good faith; if it cannot be resolved and we cannot reasonably provide the Service without that provider, you may terminate the affected subscription and we will refund fees prepaid for the unexpired portion of the then-current billing period. Planned additions. We intend to introduce a bot-detection or CAPTCHA provider to protect sign-up, sign-in and password reset against automated abuse. Such a provider would receive technical data such as IP address, browser characteristics and interaction signals, and would not receive the contents of your documents. It is not in use at the date of this Policy. We will add it to the list above and give notice as described before it goes into service. We are also putting in place our own backup arrangement, using a third-party object storage provider to hold encrypted copies of the database and stored files, and a third-party scheduling service to run it. That scheduling service would hold access to our database in order to do so. Neither is in use at the date of this Policy - see clause 8.3. We will add both to the list above and give notice as described before they go into service. 6.3 Legal and protective disclosures We may disclose personal data where we believe in good faith that disclosure is necessary to: comply with applicable law, regulation, legal process, court order, subpoena or governmental request; enforce our Terms of Service, including investigating potential violations; detect, prevent or address fraud, security incidents or technical problems; or protect the rights, property or safety of Hudraq, our customers, our users or the public. Where lawfully permitted, we will notify you before disclosing your documents, and will seek to redirect the request to you where you are the appropriate recipient. 6.4 Corporate transactions If Hudraq is involved in a merger, acquisition, financing, reorganisation, insolvency or sale of all or part of its assets, personal data may be transferred as part of that transaction, subject to the acquirer honouring commitments materially consistent with this Policy. We will notify you. 7. International transfers We operate globally, and our customers are located worldwide. Your documents and the database are held in India. At the date of this Policy, the database and file storage operate in India (Mumbai), the web application operates in India (Mumbai), and the document processing engine operates in Singapore. Error monitoring operates in the European Union, and payment processing operates in the United States and other regions determined by our payment processor. We do not currently operate a backup arrangement of our own; where we introduce one, we will state the region of the storage provider in the sub-processor list in clause 6.2 before it goes into service. Personal data may therefore be stored and processed in India, Singapore, the European Union, the United States and other countries where we or our service providers operate. These countries may have data protection laws that differ from those of your country. Where we transfer personal data from the European Economic Area, the United Kingdom, Switzerland, or another jurisdiction with transfer restrictions, to a country not recognised as providing an adequate level of protection, we rely on appropriate safeguards, which may include: the Standard Contractual Clauses approved by the European Commission, together with the UK International Data Transfer Agreement or Addendum, as applicable; an adequacy decision covering the recipient country; certification under an approved framework; or another lawful transfer mechanism recognised under applicable law. We conduct transfer impact assessments where required and apply supplementary technical measures, including encryption in transit and at rest. You may request a copy of the relevant safeguards by contacting info@deeprevise.com. Different components of the Service are hosted in different regions, and your data is therefore not processed in a single jurisdiction. The database and file storage, the web application, the document processing engine and the error monitoring service each operate in their own region, and these are fixed by us rather than chosen per account. We do not currently offer data residency in a region of your choosing. Contact us at info@deeprevise.com if you require the current region of any specific component. 8. How long we keep personal data We retain personal data for as long as necessary to fulfil the purposes described in this Policy, unless a longer period is required or permitted by law. Account and company details: For the life of the account. Where the account has no active subscription, the retention period in clause 8.1 applies, after which the data may be deleted or anonymised, subject to the exceptions below Uploaded documents: For the life of the account, or until you delete them. Where the subscription ends, the retention period in clause 8.1 applies Generated package files: Removed from storage a short period after the package is built - measured in minutes, not days. You are expected to download each package when it is generated Generation records: The record of a package generation event is retained for the life of the account. It does not include the assembled file - see clause 8.2 Subscription, invoice and tax records: 7 years from the date of the transaction, to meet tax, accounting and audit obligations Security, audit and access logs: Retained for the period provided by our infrastructure providers under our current plans, which is short - presently measured in days rather than months. We do not currently operate long-term log archiving Application error and performance data: Typically 90 days Support correspondence: 3 years from the close of the request Marketing data and consent records: Until you unsubscribe or object, plus a record of that objection retained so that we can honour it Acceptance records: Retained for the life of the account and kept after the account is deleted - see clause 8.4 Data subject to legal hold, dispute or regulatory requirement: For as long as necessary, notwithstanding the periods above 8.1 Retention after a subscription ends Where an account has no active subscription - because it was cancelled, expired, lapsed for non-payment, was terminated, or was never purchased - a retention period of three (3) months applies, running from the date the subscription ceased to be active or, for an account that has never held a subscription, from the date the account was created. When the subscription ends, metered features stop immediately - you can still view, download and delete what is stored, but you cannot upload or generate anything new. On expiry of that period we may permanently delete the account and everything in it, including all documents and generation records, without further notice. Deletion is irreversible. This is a right we hold, not an obligation we owe. We may delete data at the end of the retention period, later, or not at all, at our discretion. You should not rely on data remaining available after the retention period, and if you need deletion by a particular date you must request it. The corresponding contractual provision is clause 12.5 of the Terms of Service. Longer retention applies where required by law, tax or audit obligation, where data is subject to a legal hold, dispute or regulatory request, or where it is necessary to establish, exercise or defend a legal claim. This period is an outer limit set by us. Within it, you decide what to keep and what to delete. 8.2 Generation records and deletion requests A generation record notes that a package was produced and what went into it. It does not contain the assembled package file, which is removed from storage within minutes of the package being built. The record itself is updated when the file is removed. Generation records are deleted when the account containing them is deleted. You can delete a generation record yourself, by deleting the submittal it belongs to; the record and the stored package objects go with it. If you ask us to delete a specific record instead - including to satisfy an erasure request from an individual - we will delete it in its entirety. We do not redact or partially amend records. Deletion is permanent and we will confirm it in writing. Send requests to info@deeprevise.com from the email address on the account. 8.3 Backups Our infrastructure providers maintain their own backups under their standard plans. Residual copies may therefore persist for a limited period after deletion from live systems and are overwritten on those providers' ordinary rotation cycles. We do not currently operate a backup schedule of our own. We are putting one in place: encrypted copies of the database and of stored files, taken daily to a third-party object storage provider and run by a third-party scheduling service, with database copies retained for thirty (30) days and file copies for seven (7) days before being overwritten. It is not in operation at the date of this Policy, and we will update this clause and the sub-processor list in clause 6.2 before it goes into service. Once it is running, a document you delete may persist in a backup copy for up to seven days, and database records for up to thirty days, after they have been removed from the live system. Backups are not used to restore individually deleted records. We may retain aggregated and de-identified data, which no longer identifies any individual and which we do not attempt to re-identify, indefinitely. 8.4 Acceptance records survive account deletion When you accept our Terms of Service and Privacy Policy, we record which version you accepted, the date and time, and the IP address and browser user-agent captured at that moment. This is how we can show, later, the terms on which the Service was supplied to you. This record is treated differently from the rest of your data. When an account is deleted - whether by you, by us, or under clause 8.1 - the acceptance record is not deleted with it. It is copied to a separate archive, together with the name, email address and company name held at the moment of deletion, so that the record remains meaningful once the account itself is gone. We keep archived acceptance records for as long as they may be needed to evidence the agreement and to establish, exercise or defend a legal claim. There is currently no fixed expiry period for this archive. The archive is append-only by design: ordinary deletion of an archived record is blocked, so that a record cannot be changed or lost in the course of normal operation. If you want an archived acceptance record erased, write to info@deeprevise.com from the email address that held the account. Removing an archived record, or amending one so that it can be reduced or anonymised, requires a deliberate manual procedure in either case. We will weigh your request against our need to keep the record - retaining it is necessary for the establishment, exercise and defence of legal claims, which is a recognised ground under data protection law for continuing to hold personal data despite a request for erasure - and we will consider whether it can instead be reduced or anonymised. Where we act on the request, we will confirm the erasure in writing. 9. Security We maintain technical and organisational measures designed to protect personal data against unauthorised access, alteration, disclosure, loss and destruction. These include: Account isolation - every record is scoped to its owning account and protected by database-level row security policies that prevent access across accounts; Encryption - data is encrypted in transit using industry-standard transport encryption, and at rest by our infrastructure providers; Access control - role-based permissions within the Service, enforced at the database layer; Credential handling - passwords are never stored in plain text; authentication is token-based with defined expiry; Controlled file access - stored documents are not publicly addressable and are served only through short-lived signed links; raw storage paths are never exposed to clients; Controlled processing engine - the document processing engine takes its work from an internal queue rather than from requests made to it, and does not accept document submissions over the public internet; Logging - authentication and access events are recorded, and application errors are reported to our error monitoring provider; Confidentiality - personnel are bound by confidentiality obligations, and access to production data is limited to those who need it; Vendor terms - we use established infrastructure providers and rely on the data protection terms they offer. No system is perfectly secure. We cannot guarantee absolute security, and you transmit data to us at your own risk. You are responsible for maintaining the confidentiality of your credentials, for using strong and unique passwords, for deciding who you share documents with, and for enabling any additional authentication measures we make available. Where we become aware of a personal data breach affecting documents you have uploaded, we will notify you without undue delay and provide the information reasonably necessary for you to meet your own notification obligations. Where we are the controller, we will notify supervisory authorities and affected individuals where required by law. To report a suspected vulnerability, contact info@deeprevise.com. Please do not test the Service without our prior written authorisation. 10. Cookies and similar technologies We use only the cookies and similar storage necessary to make the Service work: authentication, session management, security, and remembering your display preferences. We do not use advertising, cross-site tracking or analytics cookies, and we do not permit any third party to use our Service for behavioural advertising. There is no analytics provider in the Service. Because these cookies are strictly necessary, there is no cookie consent banner or cookie settings screen - there is nothing optional to switch off. You can block or delete cookies through your browser settings, but doing so will prevent you from signing in. Some browsers transmit a "Do Not Track" or Global Privacy Control signal. We do not track you across sites, so there is no tracking for such a signal to stop. 11. Your rights Depending on where you are located, you may have some or all of the following rights in relation to personal data for which we are the controller. Access / know: Obtain confirmation of whether we process your personal data, receive a copy, and be told the categories collected, the sources, the purposes, and the categories of recipients Rectification / correction: Have inaccurate personal data corrected and incomplete data completed Erasure / deletion: Have personal data deleted, where a ground set out in applicable law applies Restriction: Have processing restricted in defined circumstances, for example while accuracy is being verified Portability: Receive personal data you provided in a structured, commonly used, machine-readable format, and have it transmitted to another controller where technically feasible Objection: Object to processing based on legitimate interests, and to processing for direct marketing at any time Withdraw consent: Withdraw consent where processing is based on it, without affecting prior lawful processing Non-discrimination: Not receive discriminatory treatment or degraded service for exercising your privacy rights Opt out of sale, sharing or targeted advertising: We do not sell or share personal data and do not use it for targeted advertising, so there is nothing to opt out of Limit use of sensitive personal information: We do not collect sensitive personal information for purposes that would trigger this right Appeal: Where we decline a request, appeal that decision - see clause 11.4 Complain: Lodge a complaint with your local supervisory or data protection authority Authorised agent: Use an authorised agent to submit a request on your behalf, subject to verification of their authority 11.1 How to exercise your rights Contact us at info@deeprevise.com. We will respond within the period required by applicable law - generally one month under the GDPR and forty-five days under United States state privacy laws - and we may extend that period where permitted, in which case we will tell you. We will take reasonable steps to verify your identity before acting on a request, which may include asking you to confirm information already associated with your account. We may decline a request where an exemption applies, where it is manifestly unfounded or excessive, or where complying would adversely affect the rights of others; we will explain our reasons. 11.2 Requests concerning documents held in someone else's account If your request concerns personal data inside a document that another account holder uploaded, contact that person or business directly - they decide what is stored and for how long. We generally cannot identify which account holds a given document, and we do not search customer accounts on request without a lawful basis. Where we can identify the account holder, we will pass your request to them. 11.3 Requests concerning payment data We hold your billing and subscription records and will action requests concerning them. Card data is held only by our payment processor and never by us; requests concerning card data, or concerning the processor's own fraud and compliance processing, should be directed to that processor. 11.4 Appeals If we decline a request, you may appeal by replying to our decision with the word "Appeal" in the subject line, or by writing to info@deeprevise.com. We will review the appeal and respond within the period required by applicable law, explaining our reasoning. If the appeal is denied, you may contact your state attorney general or supervisory authority. 11.5 European and United Kingdom users You may lodge a complaint with the supervisory authority in your country of residence, place of work or the place of the alleged infringement. In the United Kingdom, this is the Information Commissioner's Office. We would appreciate the opportunity to address your concerns first. 11.6 Statement regarding sale and sharing In the preceding twelve months, Hudraq has not sold personal data, has not shared personal data for cross-context behavioural advertising, and has not knowingly sold or shared the personal data of any person under 16 years of age. We disclose personal data to service providers for the business purposes described in clause 6. 12. Children The Service is a business tool and is not directed at children. We do not knowingly collect personal data from anyone under the age of 18. If we become aware that we have collected such data, we will delete it. If you believe a child has provided us with personal data, contact info@deeprevise.com. 13. Third-party sites and services The Service and our website may contain links to third-party websites, products or services, and Customer Content may itself contain links. We are not responsible for the privacy practices of any third party, and this Policy does not apply to them. Review the privacy policy of any third party before providing it with your data. 14. Changes to this Policy We may update this Policy from time to time to reflect changes in our practices, technology, legal requirements or business. Where a new version requires your acceptance, it is presented to you when you next sign in, and you must accept it to continue using the Service. Other changes take effect on posting. Where required by law, we will obtain your consent. If you do not wish to accept a version that requires acceptance, you may stop using the Service and ask us to cancel your subscription by writing to info@deeprevise.com. Previous versions are available on request at info@deeprevise.com. 15. Contact us Hudraq Technologies LLC 5830 E 2nd St, Ste 7000 #37629, Casper, Wyoming 82609, United States All enquiries, including privacy requests, data subject requests, security reports, legal notices and general support: info@deeprevise.com