Legal
Privacy Policy
This Privacy Policy (this "Policy") explains how Auxfield Labs, Inc. ("ALI," "we," "us," or "our") collects, uses, discloses, and protects personal data. It covers our website at auxfield.com, the Qiviut service at qiviut.auxfield.com (the "Service"), our mailing lists, our partner and collaboration systems, and our email and telephone correspondence. It is referred to in, but is not incorporated into, the Qiviut Terms of Service (the "Terms"). Capitalized terms used but not defined in this Policy have the meanings given in the Terms.
This Policy is organized by how you deal with us. Sections 2 through 6 describe each group of people and the data we hold about them. Sections 7 through 14 apply to everyone.
The Service is offered to business, academic, governmental, and other research organizations and to individuals acting for business or professional research purposes. It is not offered to consumers for personal, family, or household purposes, and it is not directed to children.
1. WHO WE ARE AND HOW TO CONTACT US
1.1 Controller. ALI is a Wyoming corporation at 1720 Carey Ave., Suite 200, Cheyenne, WY 82001, United States. For the personal data described in this Policy, ALI acts as the controller, except as stated in Sections 1.4 and 8.1.
1.2 Contact. Questions about this Policy, and requests to exercise the rights described in Section 12, may be sent to ALI at hello@auxfield.com. Formal legal notices may be sent to legal@auxfield.com or to the postal address above.
1.3 Which Sections Apply to You. Section 2 applies to visitors to our pages. Section 3 applies to Qiviut customers. Section 4 applies to subscribers to our news list and our waitlist. Section 5 applies to business partners, their staff, and our business contacts. Section 6 applies to anyone who emails or telephones us. More than one may apply to you. Sections 7 through 14 apply in every case.
1.4 Inputs and Outputs. Inputs and Outputs submitted to and produced by the Service are governed by Sections 5, 10, and 11 of the Terms, not by this Policy. Section 5.4 of the Terms prohibits the submission of personally identifiable human genetic or genomic data, protected health information, and other data identifying an individual, and Section 5.5 of the Terms describes the transmission of Inputs to public scientific database services outside ALI’s control. Where a Customer nonetheless submits personal data as an Input in breach of the Terms, that Customer is the controller of that data and ALI processes it only as a processor on the Customer’s behalf, for the limited purposes in Section 10.4 of the Terms and subject to the processor terms in Section 10.10 of the Terms.
2. VISITORS TO OUR PAGES
2.1 Counting Visits. We measure use of our pages with analytics software that we run ourselves, on our own server. We use no third-party analytics provider, and the data is not sent to anyone. A visit records the address of the page with any query string and fragment removed, the page title, the page that referred you, and your browser, operating system, and device type, each of which your browser sends to any website it requests a page from. We derive the country the visit came from using your Internet Protocol address at the moment of the visit and do not store the address, and we discard city-level information. We count visitors using an identifier produced by a one-way function that changes daily, so visits cannot be linked across days or across sites. We do not record your screen size or your language.
2.2 What We Do Not Measure. On Qiviut, only signed-out visitors are counted. Customers using the Account interface are not counted, and pages that carry a job identifier are never measured. Because an identifier can appear in the path of an address as well as in a query string, we exclude those pages from measurement entirely.
2.3 What Is Stored on Your Device. Our visit counting stores nothing on your device and reads nothing from it, except that if you turn counting off under Section 2.4 we store that choice in your browser so that we can honor it on later visits. That record is written only if you turn counting off, and it is never sent to us. Separately, our sign-in system sets a session cookie to keep you signed in, and we store your light or dark appearance preference in your browser’s local storage. When you buy Credits, Paddle sets its own cookies during checkout under its own policies. We use no advertising, tracking, or third-party analytics cookies, and our pages load no fonts, scripts, or other resources from third parties, except that the checkout loads Paddle’s own components when you buy Credits and the sign-in page directs you to Google or GitHub if you choose to sign in that way. Because we set no non-essential cookies, we do not present a cookie consent banner.
2.4 Your Choices. A link marked "Choices" appears in the footer of every page on auxfield.com and on Qiviut. It opens a switch marked "Count my visits." Turning it off stops counting in that browser at once, including on the page you are reading, and on every later visit from that browser. We also do not count your visit where your browser sends a Global Privacy Control or Do Not Track signal. Because the counting holds no identifier that persists beyond a day and no link to any Account, we cannot identify or exclude a particular person’s past visits on request; the switch is the means of objecting, and Section 12 describes how to raise anything it does not address.
2.5 Server Logs. We keep no access log for auxfield.com. Errors are written to the server’s system log, which records the path requested and never the query string, because a query string can carry an email address or scientific data. That log is kept for thirty (30) days.
3. QIVIUT CUSTOMERS
3.1 Account Data. When an Account is registered by email, we collect the email address, which also serves as the username, and a password, which we store only as a cryptographic hash. We also record the version of the Terms and the Acceptable Use Policy accepted, the date and time of acceptance, and the method of acceptance, each time acceptance is given. We do not collect an organization name, country, or job role at registration.
3.2 Sign-in with Google or GitHub. You may register and sign in using a Google or GitHub account. Where you do, we receive from that provider only your name, your email address, and your account identifier with that provider, and we accept only an email address that the provider has verified. We use that information solely to create and authenticate your Account and to operate the Service. We do not use it for advertising, and we disclose it only as described in Section 8. Google and GitHub handle your authentication under their own privacy policies and terms, to which you agree with them directly.
3.3 Billing Data. Purchases of Credits are processed by Paddle as Merchant of Record. Paddle collects the payment method, billing name, billing address, and tax identification information directly from the purchaser. From Paddle we receive and store only the Paddle customer identifier and email address and, for each purchase, the transaction identifier, the price identifier, the time, the number of Credits, and the pack’s list price. We do not receive or store payment card numbers or any part of them, bank account numbers, the transaction currency, or the tax jurisdiction. Our back office reads sales and refund totals from Paddle on request using a read-only credential and does not retain them.
3.4 Usage and Technical Data. When the Service is used, we collect Request metadata: timestamps, request size, computational resource consumption, Credit movements, error and status codes, Internet Protocol address, API Key identifier, service version, and client identifier. We collect Request metadata for every Request. We also keep sign-in and security events, recording the account name, Internet Protocol address, time, and outcome.
3.5 Service Messages. When a Computation completes we send a message to the address on the Account. That message gives the name of the job, the chain types and lengths, the Credits charged, and a link to the result in the Account interface. It carries no sequences, no structures, and no attachments. As described in Section 11.6 of the Terms, that message forms part of the Service and is always sent. We also send notices of suspension, closure, reinstatement, and changes to these documents. Marketing and newsletter messages are separate and are described in Section 4.
3.6 Country of Registration. To comply with United States export control and sanctions law, we determine the country from which an Account is registered and decline registrations from countries and territories subject to comprehensive United States sanctions, and from Syria as a matter of our own business policy, as described in Section 3 of the Acceptable Use Policy. Determining a country of registration is not restricted party screening. We do not engage a third-party screening provider, and we do not screen the name of the holder of an Account that makes no purchase. Paddle screens the purchaser of any Credit pack as part of its own processes.
3.7 Inputs and Outputs. Section 5.4 of the Terms prohibits the submission of data that identifies or can reasonably be used to identify an individual, and we therefore do not expect the scientific content of Inputs and Outputs to constitute personal data. Where it nonetheless does, because it relates to an identifiable person, it is personal data and we handle it under Sections 10 and 11 of the Terms and Section 1.4 of this Policy.
3.8 No Special Categories. We do not intentionally collect special categories of personal data, including data concerning health, genetic data, or biometric data, in connection with Account registration, billing, usage, our mailing lists, or our analytics.
4. SUBSCRIBERS TO OUR NEWS LIST AND WAITLIST
4.1 How We Run Our Lists. We run our mailing lists on our own server and send from our own mail server. No third party operates them, and we do not disclose the lists to anyone.
4.2 News List. If you join our news list we collect your email address, the list you joined, and the times you signed up and confirmed. We do not record the Internet Protocol address you signed up from. You confirm your subscription by clicking a link we email to you, and we send nothing until you do. We rely on your consent.
4.3 Waitlist. If you ask to be told when Qiviut opens for registration, we collect your email address and the times you signed up and confirmed, on the same confirmed basis as Section 4.2. We delete your entry thirty (30) days after we email you that registration is open, or sooner if you create an Account or unsubscribe, and we email you when either happens.
4.4 No Tracking in Our Emails. Our list messages contain no tracking pixel and no tracked links. We do not record whether you opened a message or which links you followed.
4.5 Unsubscribing. Every message contains an unsubscribe link and our postal address, and you may unsubscribe at any time. Withdrawing consent is as easy as giving it. A sign-up that is never confirmed is deleted after thirty (30) days. When you unsubscribe we keep your email address alone, on a list recording only that you are not to be emailed, so that you are not added again by a later sign-up. We do not use that record for any other purpose.
5. BUSINESS PARTNERS AND CONTACTS
5.1 Partner Onboarding and Agreement Signing. When we invite a person at another organization to sign a non-disclosure agreement, we collect that person’s name, email address, and company, the name of the person at ALI who invited them, the agreement template used, the invitation link, the signed agreement, and the signing system’s record of who signed and when. We rely on the performance of our contract with that organization, and on our legitimate interests in dealing with the individual who acts for it. An invitation that is never signed is deleted after ninety (90) days.
5.2 Business Contacts. We keep a record of the organizations we deal with and the people we deal with there, including name, email address, and role, together with the opportunities we are discussing and notes of our dealings and correspondence. We rely on our legitimate interests in managing our business relationships.
5.3 Collaboration Accounts. A partner who has signed a non-disclosure agreement may be given an account to reach our partner portal, shared folders, a chat room, and our code repositories. For that account we hold a name, email address, and username, and we log sign-in events. A non-disclosure agreement does not by itself give access to Qiviut: a partner that wants to use Qiviut does so as a customer, under the Terms, and accepts them as described in Section 1.2 of the Terms.
5.4 Files, Messages, and Meetings. Our shared workspace holds documents partners send us or that we share with them, chat messages and calls, meeting invitations, and contact cards. Document editing, the whiteboard, and call relay all run on our own server. We do not record calls.
5.5 Code Repositories. Our code repositories hold an account name and email address for each person with access, together with the repositories, issues, and commits they create. The history of a repository records the name and email address of the author of each commit, and keeps them for as long as the repository exists. That information is part of the history itself and cannot be removed without rewriting the history of the repository, which would break every copy of it that anyone else holds. If you ask us to erase your data and you have authored commits, we will tell you what the history contains, remove your account and everything else we hold about you, and explain what we can and cannot change in the history and on what terms. Section 12.4 describes this further.
5.6 Direct Invoicing. Where we invoice an organization directly, rather than through Paddle, we hold the organization’s name, the contact’s name and email address, the billing address, and the invoices, quotations, credits, and purchase orders themselves, with copies kept in our own document store. We rely on the performance of our contract and on our legal obligation to keep tax records. Qiviut’s self-serve purchases are handled by Paddle and are described in Section 3.3.
6. PEOPLE WHO EMAIL OR TELEPHONE US
6.1 Email. We hold mailboxes for our staff and for our shared addresses, including hello@, legal@, and billing@, and an automated address from which Qiviut’s service messages are sent. These hold whatever you write to us and whatever we write in reply. We rely on our legitimate interests in answering correspondence and keeping a record of it, and on the performance of a contract where the correspondence concerns one. A message you send us asking for support or giving us feedback is forwarded to our shared address and contains what you wrote.
6.2 Our Automated Sender. The address that sends Qiviut’s service messages keeps a copy of what it sends for ninety (90) days. Copies of customer result messages contain the information described in Section 3.5 and no scientific data. Copies of messages submitting predictions to a public benchmarking experiment do contain predicted structures, because that is the form the experiment requires; those are predictions for the experiment’s own public targets and are not customer data.
6.3 Telephone. Our telephone line records the calling and called numbers and the time of each call. Our telephone server’s log holds the same information, together with the addresses of automated systems attempting to break into it. Voicemail is available and is not emailed. We do not record calls. Our carrier, Telnyx, carries the calls and keeps its own records of them under its own policy.
7. HOW WE USE PERSONAL DATA AND OUR LEGAL BASES
We use personal data to:
- (a) create, authenticate, administer, and secure accounts and API Keys;
- (b) provide, operate, maintain, monitor, and support the Service and our other systems, including sending service messages;
- (c) meter usage, administer Credits, process purchases and refunds, and maintain billing and tax records;
- (d) detect, investigate, and prevent fraud, abuse, security incidents, and violations of the Terms or the Acceptable Use Policy;
- (e) comply with applicable law, including tax, accounting, export control, and sanctions obligations, and respond to lawful requests from authorities;
- (f) communicate with you, including about security, billing, and changes to these documents;
- (g) manage our relationships with partners, contributors, and business contacts, and perform our agreements with them;
- (h) measure and improve the performance, reliability, and security of our pages and the Service, using the counting described in Section 2 and the aggregated and de-identified operational statistics described in Section 10.6 of the Terms;
- (i) send news messages where you have asked to receive them; and
- (j) establish, exercise, or defend legal claims.
We do not sell personal data, and we do not share personal data for cross-context behavioral advertising or targeted advertising. We do not use personal data for automated decision-making that produces legal effects concerning you.
Where the EU or UK General Data Protection Regulation applies, we rely on the following legal bases:
- (a) Performance of a contract — to register and administer Accounts, provide the Service, send service messages, process purchases and refunds, provide support, and perform our agreements with partners and contributors.
- (b) Legal obligation — to comply with tax, accounting, and records retention requirements, and to respond to lawful requests.
- (c) Legitimate interests — to secure and improve our systems, prevent fraud and abuse, enforce the Terms and the Acceptable Use Policy, determine the country from which an Account is registered so as to comply with United States export control and sanctions law, count visits to our pages as described in Section 2, manage our business relationships and correspondence, and establish, exercise, or defend legal claims. We have assessed each of these interests against your rights and freedoms and keep a written record of that assessment, which is available on request at the address in Section 1.2. You may object as described in Sections 2.4 and 12.
- (d) Consent — for our news list and our waitlist. Consent may be withdrawn at any time, and withdrawing it is as easy as giving it.
For the purposes of United States state privacy laws, the categories of personal data we collect are those described in Sections 2 through 6; the sources are you, your organization, your device, Google or GitHub where you sign in with one of them, and Paddle; the business purposes for which we collect and disclose each category are those listed above; the categories of recipients are described in Section 8; and the retention period for each category is described in Section 10. We do not collect sensitive personal information for the purpose of inferring characteristics about you.
8. WHO WE DISCLOSE PERSONAL DATA TO
8.1 Paddle as an Independent Controller. Paddle.com Inc., Paddle.com (Canada) Ltd, and Paddle.com Market Limited act as our authorized reseller and Merchant of Record and process purchase, billing, and tax data. Paddle determines the purposes and means of that processing for its own role in the transaction and acts as an independent controller, not as our processor. Paddle’s privacy notice is available at paddle.com/legal. Funds remitted by Paddle are received into ALI’s accounts at its banking provider, which receives transaction and settlement information and not account credentials.
8.2 Service Providers. We disclose personal data to service providers that process it on our behalf under written agreements limiting their use of the data to the purposes we specify. These are Contabo, which provides the server, located in France, on which our website, mailing lists, sign-in system, email, partner systems, code repositories, and shared workspace run; Amazon Web Services, which provides compute and object storage located in the United States for Qiviut only; and Telnyx, which is our telephone carrier and is located in the United States. We expect to move further components of the Service to Amazon Web Services; this Policy applies in either configuration, and the current list is published as stated in Section 8.4. Our mailing lists, our email delivery, our sign-in system, and our visit counting run on our own server and involve no third-party provider. Where you choose to sign in with Google or GitHub, that provider authenticates you under its own terms, as described in Section 3.2.
8.3 Professional Advisors. We disclose personal data to our legal, accounting, tax, and insurance advisors where necessary for them to advise us, and to tax authorities where we are required to.
8.4 Current List. A current list of our subprocessors, and of the public scientific database services to which the Service transmits Inputs under Section 5.5 of the Terms, is published at qiviut.auxfield.com/legal/services. Where ALI acts as a processor under Section 10.10 of the Terms, the notice and objection rights in that Section apply.
8.5 Legal and Safety. We disclose personal data where required by law, regulation, subpoena, or court order, or where we reasonably determine disclosure is necessary to investigate or prevent fraud, a security incident, a violation of the Acceptable Use Policy, or a threat to the safety of any person. Where a disclosure would include Inputs or Outputs, Sections 10.7 and 10.8 of the Terms apply.
8.6 Corporate Transactions. If ALI is involved in a merger, acquisition, financing, reorganization, or sale of assets, personal data may be disclosed to the counterparty and its advisors subject to confidentiality obligations, and may be transferred as part of that transaction. We will give notice before personal data becomes subject to a materially different privacy policy.
9. INTERNATIONAL TRANSFERS
9.1 Where We Process. ALI is established in the United States. Our principal server is located in France. Qiviut’s compute and object storage are located in the United States, our telephone carrier is located in the United States, and an encrypted copy of our nightly backups is held on storage we control in the United States. Personal data is therefore processed in both France and the United States, including personal data that reaches us only through our website, our mailing lists, or our partner systems.
9.2 Transfer Mechanisms. Personal data that you provide to us directly is collected by us as a controller and is not a restricted transfer by another party. Where personal data is transferred from the European Economic Area, the United Kingdom, or Switzerland to a country that has not received an adequacy decision, including transfers to our providers and the backup copy described in Section 9.1, we rely on the data processing terms we have in place with those providers, which incorporate the European Commission’s Standard Contractual Clauses together with the United Kingdom International Data Transfer Addendum or the Swiss addendum as applicable. A copy of the relevant terms is available on request at the address in Section 1.2.
10. HOW LONG WE KEEP PERSONAL DATA
10.1 Inputs and Outputs. Inputs and Outputs are retained for thirty (30) days following delivery of the applicable Output or, where no Output is delivered, thirty (30) days following the failure, cancellation, or expiry of the Computation, and are then deleted from active systems, as provided in Section 11.3 of the Terms. They are deleted earlier on request under Section 11.4 of the Terms, which we complete within ten (10) days, and immediately where ALI terminates an Account for cause under Section 15.3 of the Terms.
10.2 Accounts. Account data is retained for the life of the Account and for twelve (12) months after closure, after which it is deleted or de-identified, except as stated in Section 10.6. A collaboration account is retained while the partnership is active and for twelve (12) months after it ends.
10.3 Logs and Visit Counting. Sign-in and security event logs are retained for twelve (12) months. Operational logs produced by our compute environment are retained for three (3) days, and our provider removes expired logs within a further seventy-two (72) hours. The raw log of incoming requests is cleared on the same thirty (30) day schedule as Inputs and Outputs. The server’s system log is retained for thirty (30) days. Visit counting data under Section 2 is retained for ninety (90) days. Aggregated and de-identified operational statistics may be retained indefinitely.
10.4 Lists and Correspondence. A news list subscription is retained until you unsubscribe, and an unconfirmed sign-up is deleted after thirty (30) days; after you unsubscribe we keep only the record described in Section 4.5. A waitlist entry is deleted as described in Section 4.3. Our shared mailboxes are retained for three (3) years and then reviewed. Copies held by our automated sender are retained for ninety (90) days. Voicemail is retained for ninety (90) days, and our telephone server’s log for thirty (30) days.
10.5 Partners and Business Contacts. A signed agreement and its signing record are retained for the term of the agreement and six (6) years afterwards, which is the period in which a claim may be brought. An unsigned invitation is deleted after ninety (90) days. Business contact records are retained for twenty-four (24) months after our last contact, unless an agreement with that organization is in force. Chat messages are retained for twelve (12) months. Files shared with us are retained for the life of the relationship and twelve (12) months afterwards, and we review them each year. Deleted files remain recoverable from the trash for thirty (30) days. The name and email address recorded in the history of a code repository are retained for the life of the repository, as described in Section 5.5.
10.6 Records We Must Keep. Billing, tax, transaction, acceptance, consent, and compliance records are retained for the periods required by applicable tax, accounting, export control, and limitations laws. Invoices we issue directly are retained for seven (7) years. Data may also persist in our nightly encrypted backups until those backups expire in the ordinary course, which is not more than ninety (90) days from the date of the backup.
11. SECURITY
We maintain administrative, technical, and physical safeguards designed to protect personal data against unauthorized access, use, disclosure, alteration, and destruction. These include encryption of data in transit, with all of our public addresses served over HTTPS only and with strict transport security; access controls on a need-to-know basis; a requirement that a member of our staff record a reason before opening a Customer’s Inputs, Outputs, or result messages, with each access logged; authenticated email; encrypted backups readable only by the account that creates them; and monitoring, logging, and a daily automated review of our controls. No method of transmission or storage is completely secure, and we cannot guarantee absolute security. We will notify affected individuals and authorities of a personal data breach where required by applicable law, which under the EU and UK General Data Protection Regulation means notifying the competent supervisory authority without undue delay and, where feasible, within seventy-two (72) hours of becoming aware of it. We will notify Customers of incidents affecting Inputs or Outputs as provided in Section 11.2 of the Terms.
12. YOUR RIGHTS
12.1 Rights. Subject to applicable law, you may have the right to request access to the personal data we hold about you; correction of inaccurate data; deletion of your data; restriction of or objection to processing; a portable copy of data you provided to us; and withdrawal of consent where processing is based on consent. Where the EU or UK General Data Protection Regulation applies, these rights arise under Articles 15 through 22.
12.2 How to Exercise Them. Submit a request to hello@auxfield.com. We will verify your identity before responding, and will respond within the period required by applicable law, generally one (1) month under the EU and UK General Data Protection Regulation and forty-five (45) days under applicable United States state privacy laws, in each case subject to any permitted extension of which we will notify you. We record each request and its outcome.
12.3 What Deletion Means. When we erase an account on request we remove the sign-in credentials, mailing list entries, job files and their copies in our object storage, API Keys, and the other records we hold about you, and we replace the name and email address in our billing records with a pseudonym while retaining the amounts and dates we are required to keep under Section 10.6. Data already removed from active systems may persist in our backups until they expire as described in Section 10.6, and is not accessible for operational use in the meantime.
12.4 A Limit on Erasure. As described in Section 5.5, the history of a code repository records the name and email address of the author of each commit and cannot be changed without rewriting that history. If you ask us to erase your data and you have authored commits, we will erase everything else we hold about you, tell you what remains in the history, and discuss with you whether rewriting the affected repository is possible. We cannot change a copy of a repository held by anyone else.
12.5 Objecting to Visit Counting. The switch described in Section 2.4 stops your visits being counted immediately and without a request to us. Because the counting holds no identifier that persists beyond a day, we cannot find or remove a particular person’s past visits, and a written objection is answered by directing you to that switch.
12.6 Appeals. If we decline your request, our response will explain why. Where applicable law provides a right of appeal, you may appeal within a reasonable period by replying to our response or by writing to the address in Section 1.2 with the word "Appeal" in the subject line. We will respond to an appeal within the period required by applicable law, and will tell you how to contact the relevant attorney general or supervisory authority if the appeal is denied.
12.7 No Discrimination. We will not deny the Service, charge a different price, or provide a different level of service because you exercised a privacy right. Giving effect to a request is not discrimination: if you ask us to delete the credentials and data needed to operate your Account, we will close the Account, and we will tell you before we do.
12.8 Authorized Agents. An authorized agent may submit a request on your behalf where permitted by applicable law, with proof of authorization.
12.9 Complaints. If you are in the European Economic Area, the United Kingdom, or Switzerland, you may lodge a complaint with your local supervisory authority. We ask that you contact us first so that we can address your concern.
12.10 Requests Relating to Inputs. Where a request concerns personal data contained in an Input, the Customer that submitted the Input is the controller of that data. We will refer the request to that Customer and will assist it in responding as its processor, as provided in Section 10.10 of the Terms.
12.11 Data Processing Agreements. ALI does not offer a separate data processing agreement by default; the processor terms in Section 10.10 of the Terms apply where ALI acts as a processor. A business customer that requires a separate agreement may contact us at hello@auxfield.com.
13. CHILDREN
Our services are not directed to children, and we do not knowingly collect personal data from anyone under eighteen (18) years of age. Section 1.3 of the Terms requires the individual accepting the Terms to be at least eighteen (18) years of age. If we learn that we have collected personal data from a child, we will delete it. Please contact us at the address in Section 1.2 if you believe we have done so.
14. CHANGES TO THIS POLICY
We may update this Policy from time to time by posting an updated version with a new version number and effective date, and we keep a register of versions. For a material change, we will give notice by email to the address on your Account, or by notice on the page where this Policy is posted where we hold no address for you, at least thirty (30) days before the change takes effect. Continued use after a change takes effect constitutes acknowledgment of the updated Policy, and where applicable law requires consent to a change, we will obtain it.