Automata.

    Version 2026-09-27

    Mutual NDA

    When you book a call or an engagement with us, you can accept this agreement with one checkbox. It protects both sides, so you can share your code and plans without sending a separate NDA back and forth.

    In plain English

    • Your code, data, credentials, and business plans stay confidential. So do our tools and methods.
    • We only use what you share to talk through your project and do any work you hire us for.
    • Only people working with you see your materials, and they're bound by the same terms.
    • You can revoke our access at any time. We delete copies and credentials when the work is done.
    • You own your code. Any report or plan we deliver is yours to use however you like.
    • Checking the box at booking is your signature, so neither of us needs to sign a separate NDA.

    1. Parties and purpose

    This Mutual Non-Disclosure Agreement ("Agreement") is between Automata Studio LLC ("Automata") and the person or company who accepts it when booking a call, code audit, or other engagement with Automata ("Client"). Each is a "Party" and may act as a "Discloser" or a "Recipient."

    The Parties want to share information so they can discuss Client's product, software, and business, evaluate a possible engagement, and carry out any work Client engages Automata for, such as a code audit, a new build, or launching an existing app (the "Purpose").

    2. Confidential information

    "Confidential Information" means non-public information a Discloser shares with a Recipient in connection with the Purpose, in any form, including source code, repositories, credentials and API keys, databases and user data, product plans, designs, business and financial information, and, for Automata, its analysis tools, methods, templates, and pricing.

    Information is Confidential Information whether or not it is marked as confidential, if a reasonable person would understand it to be confidential.

    3. Exclusions

    Confidential Information does not include information that (a) is or becomes public through no fault of the Recipient, (b) the Recipient already knew without a duty of confidentiality, (c) the Recipient receives lawfully from a third party without a duty of confidentiality, or (d) the Recipient develops independently without using the Discloser's Confidential Information.

    4. Obligations

    The Recipient will use Confidential Information only for the Purpose, protect it with at least reasonable care, and share it only with its employees and contractors who need it for the Purpose and are bound by confidentiality obligations at least as protective as these.

    The Recipient will not reverse engineer, copy beyond what the Purpose requires, or disclose the Discloser's Confidential Information to anyone else.

    5. Code access and credentials

    Automata will use any access Client grants (for example, read access to a code repository or hosting account) only for the Purpose. Client may revoke access at any time.

    When the Purpose is complete, or earlier if Client asks, Automata will delete local copies of Client's code, data, and credentials within 30 days, except for work delivered to Client and records Automata must keep by law.

    6. Required disclosure

    If a Recipient is legally required to disclose Confidential Information, it will give the Discloser prompt notice where the law allows, cooperate with reasonable efforts to limit the disclosure, and disclose only what is required.

    7. Ownership

    Each Party keeps all rights in its own Confidential Information. Nothing in this Agreement grants a license to the other Party's intellectual property.

    Client owns its code. Client may use any report or plan Automata delivers for any purpose. Automata keeps ownership of its tools, methods, and general know-how. Ownership of anything Automata builds for Client is governed by the Parties' separate engagement terms.

    8. Term

    This Agreement starts when Client accepts it and covers information shared for two years after that. Confidentiality obligations last for two years after disclosure, and for as long as the information remains a trade secret, including source code.

    9. Remedies

    Unauthorized use or disclosure may cause harm that money alone cannot fix, so the Discloser may seek injunctive relief in addition to any other remedies.

    10. General

    This Agreement is governed by the laws of the Commonwealth of Massachusetts. Neither Party is obligated to pursue any further business relationship. If the Parties sign a separate written confidentiality agreement, that agreement controls where the two conflict.

    Client accepts this Agreement electronically by checking the box at booking, and that acceptance has the same effect as a signature. Automata accepts it by holding the booked call or providing the booked service.

    Want a signed copy or have a question? Email hello@meetautomata.com.