Terms

Terms of service.

Effective date: 6 October 2026

1 Agreement and operator

These Terms govern hinky.dev and its browser-based development services (the “Service”), provided by More On Off Switches LLC, doing business as hinky.dev (“we,” “us,” or “our”), operating from Texas, United States.

You accept these Terms by using the Service. Our sign-in screen states that continuing means accepting them and that you are at least 13, and links to them and to our Privacy Policy, so that you can read both before you start. If you register directly with our identity provider you may not pass that screen; these Terms and the representations in them apply to your use of the Service either way. If you do not agree, do not use the Service. If you accept on behalf of an organization, you represent that you have authority to bind it. Our Privacy Policy explains personal-information processing; acceptance of these Terms does not replace separately required consent.

Contact: support@hinky.dev. Mailing address: 5900 Balcones Drive, Suite #7984, Austin, TX 78731.

2 Age and international access

You must be at least 13 years old to use the Service. By using it you represent that you are, and that representation is the whole of the check: we do not verify age and we collect no information about it. If we learn you are under 13 we will close the account and delete its contents, as our Privacy Policy describes.

Where applicable law requires a parent or guardian to authorize use or accept a contract on your behalf, that requirement must be satisfied. We have not built a parental-consent process, so the Service is not available where verified consent is legally required.

We intend to make the Service available internationally, subject to applicable laws, including sanctions and export restrictions. We may restrict access where providing the Service would be unlawful or legally required safeguards are unavailable. These Terms do not establish that the Service or a connected third-party service is legally available to every person in every country.

3 Features and access levels

The Service provides source-code editing, building, compiling and running code, and recording execution traces. Everything it currently offers is free of charge.

What an unregistered session can do. Edit, build, run and record traces. Those sessions are confined: a session's network reaches only an allow-list of package registries and source hosts needed to resolve build dependencies, and nothing else; nothing about the session is reachable from outside, so there is no terminal, no remote desktop and no served port; and a session stops after five minutes. Work is kept for seven days.

What a registered account adds. A terminal, a remote desktop, a served port on which you can reach something you are running, longer sessions, and work that is kept while the account is in use.

What we may limit. Resources are finite and shared. We publish the current limits in the Service, we may stop a job that exceeds them or threatens the Service, and we may change them. Availability of a feature today is not a commitment to its permanent availability or to unlimited capacity.

Permitted build steps may run approved tools within the environment. You may not use build scripts, compiler features, dependency installation, or other mechanisms to bypass the limits of your access level.

Supported languages, toolchains, storage and networking are described in the Service or its documentation.

4 Accounts and your responsibilities

Provide accurate information, protect your credentials and devices, and promptly report suspected unauthorized access to security@hinky.dev. You are responsible for activity you authorize and for taking reasonable steps to secure your account.

Do not impersonate others, use another person’s credentials without authorization, or create accounts or sessions to evade restrictions. Keep independent backups of important work and review dependencies and outputs before relying on them.

5 Your Content and limited processing rights

“Your Content” means code, files, configurations, inputs, and other materials you submit. You retain your rights in Your Content. We do not acquire ownership merely because you use the Service.

You grant us a nonexclusive license to host, store, copy, process, transmit, display back to you and anyone you authorize, build, compile, and technically adapt Your Content as necessary to provide requested features, operate and secure the Service, investigate abuse, enforce these Terms, and comply with law.

Because the Service records your edits as they happen in order to synchronize them across your browsers and preserve your work, this license expressly includes retaining and reproducing the editing history of Your Content, and displaying earlier states of a file to you. That history is Your Content for every purpose in these Terms: you own it, the same purpose limits apply to it, and the restrictions in the next paragraph apply to it. Execution is included to the extent the feature and your access level allow it. Our providers may exercise this license only to perform those functions for us.

The license lasts while the relevant content remains on our systems, including any copy retained under a documented legal hold, and is limited to the purposes supporting that retention. It does not authorize unrelated publication, sale, or training of general-purpose AI models on private projects.

You must have the rights and permissions needed for this processing. Third-party code, dependencies, and outputs remain subject to applicable licenses. We do not claim ownership of your build outputs merely because the Service generated them.

6 Private projects and operator review

Your sessions and projects are private from other users. They are not made public simply by submission. However, we and authorized providers may access and analyze code, files, artifacts, and logs for the operational, troubleshooting, security, abuse-investigation, enforcement, and legal purposes described in the Privacy Policy.

Review may be automated or manual and may occur without a separate permission request for each inspection. We limit access to an operational need and appropriate confidentiality obligations. We do not promise that content is inaccessible to the operator or that every project is inspected.

We disclose nonpublic content only as described in the Privacy Policy, as you direct, or as law permits or requires. Nothing here waives nonwaivable privacy rights.

7 Acceptable use

You must not:

Violate law or another person’s intellectual-property, privacy, or other rights.
Attempt sandbox escapes, privilege escalation, host access, or access to another user’s data.
Bypass authentication, capability restrictions, payment requirements, or resource limits.
Exploit compilation or build mechanisms to obtain unauthorized execution or network access.
Conduct unauthorized scanning, exploitation, denial-of-service attacks, credential theft, spam, or malicious-code deployment.
Use the Service for cryptocurrency mining, botnets, or deliberately excessive workloads that disrupt others.
Submit content you are not authorized to disclose or process through the Service.

Security testing directed at hinky.dev infrastructure requires prior written authorization. Report vulnerabilities to security@hinky.dev. These restrictions do not prohibit ordinary authorized development or testing within your permitted environment.

8 Third-party services and AI keys

Compilers, libraries, packages, and integrations may be subject to third-party terms and licenses. You are responsible for reviewing them and for having authority to send information to services you select.

hinky.dev does not supply native AI tools or an included AI subscription. Any supported third-party AI use is bring-your-own-key. Your key is stored only in your browser and is never saved to our databases or written to persistent storage on our servers; when you use an AI feature it is transmitted through our infrastructure to the build environment that runs the feature, where it is supplied as a configuration value and is present on the machine running the session for that session's life only. Prompts, project content, and responses travel the same path. Our Privacy Policy describes it in section 6. You are responsible for safeguarding your key, meeting provider age and eligibility requirements, and paying provider charges.

We do not control an independent provider’s availability, outputs, retention, or model-training practices. Successful compilation or an AI response does not establish correctness, security, or suitability.

9 Current fees and future paid plans

We do not currently accept payments or offer paid subscriptions. Available launch features are provided without charge.

We may introduce paid plans later, for larger resources or features we do not yet offer. If we do, we will disclose prices, billing periods, included resources, usage charges, renewal terms, cancellation methods, and refund rules before purchase, and nothing you use free of charge today will start costing money without your agreement. Charges will require your affirmative agreement. Earlier free use or account creation will not automatically enroll you in a paid plan.

Future-feature announcements do not guarantee a release date. These Terms do not establish a current automatic-renewal arrangement.

10 Storage and deletion

Saved source code can survive browser exits, but persistence is not a guarantee of permanent retention, uninterrupted access, or recovery. Closing your browser does not itself delete server copies.

The Privacy Policy’s retention schedule governs server data. Under the recommended launch schedule, temporary build files expire within 24 hours; anonymous server-saved projects, if supported, expire after 30 days of inactivity; routine logs expire within 30 days; and security logs ordinarily expire within 90 days. Account or project deletion removes applicable content from active systems within 30 days, subject to documented lawful exceptions and shorter applicable legal deadlines.

We may delete registered accounts after 12 months of inactivity only after providing 30 days’ notice to the account email. Signing in during that notice period cancels inactivity deletion.

We do not keep backups and cannot restore lost or deleted work. There is no archival copy of your projects and no recovery mechanism, so deletion is permanent whether you requested it or it resulted from a fault on our side. We are not a system of record for your source code.

Keep your own copy of anything that matters. A registered account can export one project or all of them as a downloadable archive, which requires a build environment to be running because the archive is assembled there. An unregistered session cannot currently export, and its only copy outside our systems is the one held by your browser on your device. You may also connect a repository you control.

Request account closure or server-side deletion at privacy@hinky.dev. Browser-stored copies require separate removal through browser or available app controls.

11 Availability and changes to the Service

We use reasonable care and skill in providing the Service. Maintenance, outages, security events, resource constraints, and provider failures may affect availability. No uptime commitment or service-level agreement is included in this free launch.

We may add, change, or discontinue features. Where practicable, we will give at least 30 days’ notice before discontinuing a material storage feature or the Service so you can retrieve your work. Urgent legal or security circumstances may require earlier action. Mandatory legal remedies remain available.

12 Suspension and termination

You may stop using the Service at any time and request account closure. We may restrict jobs, suspend access, or terminate access for a material breach, security threat, legal requirement, or unlawful activity.

Where practicable, we will explain the reason and give you a reasonable opportunity to resolve the issue. Immediate action may be necessary to protect users or infrastructure. You may request review at support@hinky.dev.

When reasonably safe and lawful, we will allow 30 days after an account-termination notice to retrieve saved projects, including through support where account access is restricted. This does not extend anonymous-session expiry or require preservation of malicious material. Retention and lawful deletion requests remain governed by the Privacy Policy.

Provisions intended to continue, including ownership, permitted retention, liability, and dispute provisions, survive termination.

13 Our intellectual property

We and our licensors retain rights in the Service, interface, branding, and underlying software, excluding Your Content and third-party materials. We grant you a limited, nonexclusive, nontransferable right to use the Service while your access is authorized and consistent with these Terms. Open-source components remain governed by their own licenses.

14 Warranties and responsibility for outputs

Except for express commitments in these Terms and rights that cannot legally be excluded, the Service is provided “as is” and “as available.” To the extent permitted by law, we disclaim implied warranties of merchantability, fitness for a particular purpose, and noninfringement.

We do not guarantee uninterrupted operation, error-free compilation, compatibility with every dependency, or secure and correct outputs. Test and review outputs before deployment. Do not rely on the Service for safety-critical operation where failure could reasonably cause death, personal injury, or substantial environmental harm without a separate written agreement.

Nothing in these Terms excludes mandatory consumer guarantees.

15 Limitation of liability

To the extent permitted by law, neither party is liable to the other for indirect, incidental, special, or consequential damages arising from the Service. For clarity, and without limiting that exclusion, this includes lost profits, lost business or opportunity, loss of goodwill, and — because they are the losses this Service is most likely to occasion — loss or corruption of Your Content or its editing history, loss of development time, and the cost of recreating work. Section 10 describes why you should not rely on us as the only copy of anything you cannot afford to lose.

Subject to the exceptions below, each party’s aggregate liability arising from or relating to the Service is limited to the greater of US $100 or the amount you paid us for the Service during the 12 months before the event giving rise to the claim.

These exclusions and limits do not apply to fraud, willful misconduct, gross negligence, death or personal injury caused by negligence, or any liability that applicable law prohibits excluding or limiting. They do not eliminate properly incurred payment obligations under a future separate purchase arrangement. Mandatory consumer remedies remain unaffected.

16 Governing law and disputes

Texas law and applicable United States federal law govern these Terms, without regard to conflict-of-laws principles. Consumers retain mandatory protections available under applicable law in their place of residence.

Subject to mandatory jurisdiction rules, disputes may be brought in a court with lawful jurisdiction in Texas. This clause does not prevent a consumer from using a court available under nonwaivable local law. No mandatory arbitration or class-action waiver is imposed by these Terms.

Contact legal@hinky.dev if you would like to seek an informal resolution. This does not prevent timely court action or a regulator complaint.

17 Changes to these Terms

We will provide at least 30 days’ advance notice of material changes through the Service and, where available, the account email. Changes required urgently for legal or security reasons may take effect sooner where permitted by law. We will request renewed acceptance where required.

Changes will not retroactively alter accrued rights or existing disputes. If you do not accept revised Terms, stop using the Service and request closure or retrieve your content under the applicable retention rules.

18 General provisions and contact

These Terms and any separately signed agreement govern use of the Service. A signed agreement controls a conflict to the extent it addresses that conflict. The Privacy Policy explains data practices and does not supply blanket consent to processing.

If a provision is unenforceable, the remainder remains effective. Failure to enforce a provision does not waive later enforcement. We may transfer the agreement as part of a genuine reorganization or business transfer, subject to applicable law, appropriate notice, and preservation of your mandatory rights.