What happens
to your request.
Who handles your data
The data controller hasn't been specified yet. The owner must add their details before enabling sending.
Questions about your request or deleting data: Message me on Telegram.
What data, and why
Sending a request requires a name or nickname, a contact method, contact details and an idea description. For preparation on your device, the name and contact details are optional. The budget is always optional. This information is used to reply and discuss possible work. Please leave out passwords, payment details, medical information and anything else that isn't needed for an initial conversation.
When and where a request is sent
When server delivery is enabled, your details are emailed to the data controller only after you consent and click “Send my idea”. The site doesn't keep a request database. The email provider processes the message during delivery and storage in the controller's mailbox.
In email draft mode, the site opens your email app. You check the recipient and message, then send it yourself. Opening a draft doesn't mean it has been sent.
Drafts and the idea builder
The Open in Telegram button passes the prepared text to the messenger in a link. Opening the chat does not send it. You can download a long brief as a file and attach it yourself. Once you follow the link, Telegram’s policy applies: Telegram Privacy Policy.
The builder processes answers in your browser. Builder drafts and request descriptions are saved in the current tab for up to 24 hours so they survive a refresh. Names, emails and other contact details aren't saved in drafts. Use “Clear” to delete a draft; closing the tab also ends storage. Drafts aren't sent to AI services or third-party APIs. A temporary copy fills in the request form when you transfer a brief, then that transfer copy is removed. The description draft follows the rules above. Copying and downloading save the text only where you choose.
Retention and deletion
If a request is sent to the controller, it is kept for discussing your enquiry for up to 90 days, unless further work or applicable requirements call for a different period. The controller must respect this period and delete enquiries no longer needed. To withdraw consent, correct or delete your data, use the controller's contact above. Consent applies from sending until its purpose is fulfilled or consent is withdrawn.
Maps in Connections
Connections stores the current map and named saves in this browser's localStorage until you delete the maps or clear site data. Use JSON export and import to move them between devices or from the previous address. A shared link contains the map: share it only with people you want to see its concepts and explanations.
Built-in examples don't make external requests. When you run an analysis of your own concepts, the entered text goes to an external processing service through the app's server. The secret key stays on the server. Opening a saved map or shared link doesn't start a new analysis.
In the Margins maze
The game stores the difficulty, current maze, pencil trail and elapsed time in this browser’s localStorage so you can continue after reloading or changing language. A shared link contains only the maze code and difficulty, without your trail or time. Clear the site data in your browser to remove the save.
Technical information
This site uses Yandex Metrica and Google Analytics 4 for visitor statistics: pages viewed, referral sources and devices. These services receive technical browser information and may store cookies to distinguish visits.
Webvisor records interactions with pages. Request fields, builder answers and prepared descriptions are hidden from recording. Request contents aren't added to analytics parameters. Google Signals and ad personalisation are disabled in the site's code.More about data handling: Yandex Metrica terms, Google's policy.
For server delivery, your IP address is held temporarily in memory to limit spam and removed from that counter within 11 minutes. The app doesn't log request contents. The web server and hosting may keep their own technical logs; the controller determines their contents and retention when deploying.
This describes how the site actually works. Before a public launch, the controller adds their details, checks their email provider's terms and ensures this information matches the way data is really handled.