Privacy and terms

What Gnarled Helix LLC records when you use Tauric Studio, what it does not, and the terms that apply when you share a session with somebody else. This is the whole document — the same one the app asks you to accept before you collaborate, published so it can be read first.

Version 14 · Effective August 19, 2026 · Questions to info@gnarledhelix.com

You must be at least 18 years old to use Tauric Studio. If you are under 18, do not accept these terms and do not use the prototype.

1. What this is

Tauric Studio is an unreleased prototype provided by Gnarled Helix LLC ("we", "us") for evaluation. It is made available free of charge, on an as-is basis, and may change, break, or be withdrawn at any time without notice.

These terms apply when you host or join a shared session, including when you open a preview link somebody has sent you — following one puts you in a live session with other people and connects you to our relay. Editing on your own is not covered by them, because it involves no one else and no service of ours.

A preview link is a limited kind of participation. You can see the map as it is being worked on, and you can place the marker or comment objects the project allows; you cannot otherwise change the map, and you cannot save or export it from the preview. The person who sent you the link decides which objects those are, and can end the session at any time, which ends your access to it.

Do not rely on it for work that matters. Documents, projects, and collaboration sessions may be lost, corrupted, or deleted at any time, and we keep no backups on your behalf. Keep your own copies of anything you care about.

2. Access

There are no accounts and no password: anyone who reaches the prototype can use it. Do not attempt to reach the collaboration relay by any means other than the prototype itself, and do not attempt to interfere with it or with other participants' use of it.

You are responsible for everything done through your connection.

3. Collaboration rooms are not private

Collaboration sessions are identified by a code. There are no accounts and no identity checks: we do not know who anyone is, and anyone who has a session's code can use it. A session has two kinds of code — an invite code, which allows editing, and a preview link, which allows watching and leaving the objects described in section 1. A preview link cannot be used to obtain an invite code, but it is still a shared secret: whoever holds it, or is given it, can watch that session.

Sharing a code is granting access, and there is no way to take it back apart from ending the session and starting a new one. We do not verify who receives a code you send, and neither code expires while the session is running.

Treat a room as a public space. Do not place confidential, personal, regulated, or otherwise sensitive information in a collaboration session, and do not use the prototype to process anyone else's personal data.

4. What we record

You tell the prototype a display name when it loads. That name is not verified, and anyone can enter anything.

While you are connected to a collaboration session we record, for each connection: the name you stated, a session identifier generated for that sitting, your IP address, which room you were in, whether you were editing or watching a preview, and when you joined and left. We do not record the code you used to get in. The relay stores no documents: nothing you edit is saved on our servers as a file, and no copy of your project is kept there after a session ends.

Objects you create in a map are labelled with that session identifier, so other participants can see which name added or last changed an object, and so that content can be traced back to a connection if someone reports it. Those labels travel inside the map file when you save or export it.

We reserve the right to retain operational logs and audit logs of all traffic through the collaboration relay. Operational logs cover the running of the service — connections, room names, timings, message counts and sizes, errors, and rate-limit events. Audit logs may in addition capture the content of the data relayed between participants in a room. We may keep either or both for as long as we consider necessary to operate, secure, and debug the prototype, to investigate abuse or a copyright notice, and to establish, exercise, or defend legal claims — including after you disconnect, after the prototype ends, and after a deletion request where the law requires or permits us to keep them.

Apart from what we reserve above, we keep connection records only as long as needed to investigate abuse and keep the prototype running. If you would like yours removed, contact us.

The hosted web version can use Google Analytics in two places, and they work differently. Our front page counts arrivals without asking: it loads Google Analytics only for visitors whose own browser places them in the United States, where a first-party measurement tag needs no prior permission, and not at all if the browser sends a Global Privacy Control or Do Not Track signal. THE EDITOR asks first. It counts usage — which screens are reached, which tools are used, and whether the introductory tour is finished — and it asks before the browser loads anything of Google's for that purpose, and does not run unless you agree: nothing about what you do is collected if you decline, and the editor works the same either way. We do count the ANSWER itself — one of "asked", "agreed" or "declined" is added to a running total on our own server, so that we can tell what proportion of people accept. That total is three numbers. It carries no identifier, no address, and no time beyond the period it covers, and there is no record of any individual answer, including yours. We cannot use it to tell what you did, or that it was you. You can change your answer at any time from the status bar at the bottom of the editor; turning it off stops collection immediately and clears the identifier cookies. Those events carry no names, room names, map names, or file contents. Google sets its own identifiers and processes what it receives, including your IP address, under its own terms. If your browser sends a Do Not Track signal we do not load it at all and do not ask. The desktop application does not use analytics.

If the editor CRASHES, two different things happen and only one of them is automatic. We count that a crash occurred: a short code derived from the error and the version of the software, which carries no name, no address, no identifier, and nothing that can be turned back into what you were working on — it tells us that a fault exists and how often, and nothing else. The crash REPORT — the error message and where in the program it came from — is a different matter, because it can name a file or a map you had open. It is held on our server for a few minutes and then deleted automatically, and it is kept only if you tell us it may be: the crash screen asks, and shows you the report in full first. If you decline, or close the tab, it is deleted and nothing is written down. Nothing about a crash is stored on your device, and the crash screen offers to save your map before you reload.

Our marketing pages — the front page and the public features page — also carry ADVERTISING tags, one from Google and one from Reddit. Advertising is not measurement: these are there so that we can tell which advertisements bring people here, and they allow those companies to show you advertisements elsewhere. They record that you reached the page and, if you click through to the editor, that you did so. They set their own cookies and identifiers in your browser, and each company processes what it receives, including your IP address, under its own terms rather than ours. They load under the same rule as the front page's counting and never a looser one: only for visitors whose own browser places them in the United States, and not at all if the browser sends a Global Privacy Control or Do Not Track signal. The editor's analytics question does not cover them: agreeing to it does not switch them on, and declining it does not switch them off. The editor itself carries no advertising tag, and neither does the desktop application.

If you SEND US FEEDBACK from the editor, we keep it. That is the one thing here you type on purpose and hand over, so it works the other way round from the rest of this section: nothing is collected unless you press the button, and what is collected is what you wrote. We keep your message, the version of the editor you were using, and which screen you sent it from, and we use it to decide what to fix and what to build. If you give an email address it is optional and it is used to reply to you about what you sent — we do not add it to a mailing list and we do not pass it to anyone. Your map does not travel with it: not its contents, not its name, not the files you had open. We keep feedback for as long as it is useful to us, and if you would like yours removed, contact us and say what you sent.

Our public features page counts arrivals separately and much more narrowly, on our own servers, with no third party and nothing stored on your device. When the page opens we record the page you reached, the campaign or link that brought you, the site you came from, and a shortened form of your IP address with the final part removed — enough to tell networks apart, not enough to identify you. That record is held only in memory, and is deleted automatically a short time later unless you tell us we may keep it: the page asks, and if you decline, or simply close the tab, it is discarded and nothing is written down. Your answer is remembered in your browser so we do not ask again, and if you decline we do not even send the next visit. If your browser sends a Do Not Track signal we neither count nor ask.

5. Your content

You keep ownership of the maps, images, text, comments, names, and other material you create or upload ("your content"). You grant us only the limited permission needed to transmit, relay, cache, and display your content in order to operate the prototype.

You are responsible for having the rights to everything you upload or transmit, including any third-party images, tilesets, or drawings.

Copyright notices (DMCA). If you believe material transmitted through the prototype infringes a copyright you own or represent, send a written notice to Gnarled Helix LLC at info@gnarledhelix.com with "DMCA" in the subject line. Under 17 U.S.C. § 512(c)(3) your notice must include: your physical or electronic signature; identification of the work you claim is infringed; identification of the material you claim is infringing, with enough detail for us to find it — for a collaboration session, the room name and when you saw it; your address, telephone number, and email address; a statement that you believe in good faith that the use is not authorized by the copyright owner, its agent, or the law; and a statement, under penalty of perjury, that the information in the notice is accurate and that you are the owner or authorized to act on the owner's behalf.

We will remove or disable access to material we determine to be infringing, and we will terminate the access of anyone we determine to be a repeat infringer. Because we hold no persistent copy of a session, acting on a notice may mean ending a session or blocking a room name rather than deleting a file, and it cannot reach copies participants have already saved to their own machines.

If your material was removed and you believe it was removed by mistake or misidentified, you may send a counter-notification to the same address with the elements required by 17 U.S.C. § 512(g)(3). Knowingly misrepresenting that material is infringing, or that it was removed by mistake, carries liability for damages under 17 U.S.C. § 512(f).

6. Conduct in collaboration sessions

Anything you place in a shared session — map content, entity and layer names, comment text, your display name, and anything else that syncs — is transmitted to every other participant in that room. Treat it as a message to them.

You agree not to use the prototype, and in particular not to use collaboration sessions, to transmit, display, or send to any other person content that: harasses, threatens, defames, stalks, or intimidates; is hateful or promotes violence or discrimination against any person or group; is sexually explicit, or sexually exploits or endangers a minor in any way; is obscene, or is intended to shock or disgust; infringes anyone's intellectual property or privacy rights; is unlawful, promotes illegal activity, or facilitates fraud; contains malware or attempts to compromise the service or other participants; or is unsolicited advertising or spam.

You also agree not to impersonate another person, not to misrepresent your affiliation, and not to attempt to identify, track, or contact other participants outside the prototype without their consent.

7. We do not monitor or moderate

The collaboration relay passes data between participants. We do not pre-screen, review, filter, or moderate what participants send each other, and we have no obligation to do so.

You may encounter content from other participants that is offensive, inaccurate, or otherwise objectionable. Gnarled Helix LLC is not responsible for the conduct of any participant or for content that any participant transmits, and you interact with other participants at your own risk.

We may, but are not required to, remove content, end sessions, block room names, or revoke access at any time, for any reason, without notice. If another participant's conduct concerns you, leave the session and contact us.

8. No warranty

THE PROTOTYPE IS PROVIDED "AS IS" AND "AS AVAILABLE", WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, OR NON-INFRINGEMENT. GNARLED HELIX LLC DOES NOT WARRANT THAT THE PROTOTYPE WILL BE AVAILABLE, UNINTERRUPTED, SECURE, OR ERROR-FREE, OR THAT ANY DATA WILL BE PRESERVED.

9. Limitation of liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW, GNARLED HELIX LLC WILL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR FOR ANY LOSS OF DATA, PROFITS, GOODWILL, OR BUSINESS, ARISING OUT OF OR RELATING TO THE PROTOTYPE.

WE ARE NOT LIABLE FOR THE ACTS OR OMISSIONS OF OTHER PARTICIPANTS, INCLUDING ANY CONTENT THEY TRANSMIT TO YOU THROUGH A COLLABORATION SESSION. OUR TOTAL LIABILITY ARISING OUT OF OR RELATING TO THE PROTOTYPE WILL NOT EXCEED ONE HUNDRED U.S. DOLLARS ($100).

Some jurisdictions do not allow certain limitations, in which case the limitations above apply to the greatest extent permitted.

10. Indemnity

You will indemnify and hold harmless Gnarled Helix LLC and its officers, employees, and agents from any claim, demand, loss, or expense (including reasonable legal fees) arising out of your content, your use of the prototype, or your violation of these terms or of anyone's rights.

11. Suspension and changes

We may suspend or end your access at any time, with or without cause. We may change these terms; if we do, you will be asked to accept the updated version before continuing to use the prototype.

These terms are governed by the laws of the State of Wyoming, USA, without regard to conflict-of-laws rules. The state and federal courts located in Wyoming have exclusive jurisdiction over any dispute arising out of or relating to the prototype or these terms, and you consent to their jurisdiction and venue.

12. Contact

Questions about these terms, or a report about another participant's conduct, should go to Gnarled Helix LLC at info@gnarledhelix.com. Reports of conduct that violates section 6 are read, but we do not promise a response or any particular action.

Notices may also be sent by mail to: Gnarled Helix LLC, c/o Registered Agents Inc., 30 N. Gould St., Ste R, Sheridan, WY 82801.

Gnarled Helix LLC · c/o Registered Agents Inc., 30 N. Gould St., Ste R, Sheridan, WY 82801