Privacy

Forsk is a solo project by me, Julian Riise, in Norway. I decide what happens to the data on this page, and I’m the only person who can see it.

Address: Oslo, Norway

For questions, a copy of your data or to have it deleted, email julian@forsk.app. I answer within a month at the latest, usually much sooner.

When you join the waitlist I store what you type in the form:

• your first name and email address
• the operating systems and Rhino versions you use
• where you work: an office, freelance or other
• whether you want to help shape Forsk
• what you write about how Forsk could help you, if anything
• when you signed up and when I sent your welcome email

I use it to decide which setups to support first, to send you one welcome email, and to email you when Forsk runs on your setup, with your waitlist offer. If you said yes to helping shape Forsk, I may email you personally to hear how you work. I don’t sell it or share it for advertising.

The basis is your consent, which you give when you submit the form. You can withdraw it any time by replying “unsubscribe” to any email from me or by emailing julian@forsk.app, and I delete your signup. Otherwise I keep it until 12 months after I’ve emailed you that Forsk runs on your setup, and then delete it.

Signing up again with the same email changes nothing. To change your answers, email me.

If you sign in to the dashboard, I store:

• your email address, when the account was created and when you last signed in
• your licence: plan, status and dates
• the Macs you connect to Forsk: each Mac’s name, its Rhino and Forsk versions, and when it last checked in

You sign in with a 6-digit code sent by email. Codes, sign-in links and session tokens are stored only as one-way hashes. Old codes are cleared after about a day, and a session ends 60 days after you last use it.

The basis is our agreement: I need this to give you and your Macs access to Forsk. It’s kept until you delete your account on the Account page, which also deletes your sessions and connected Macs. Licence records stay behind with nothing that links them to you, so I can count how many licences I’ve given out.

Your drawings, images and geometry stay on your Mac. Forsk only reaches out in these cases:

• Once per Rhino session it asks forsk.app whether there’s a newer version. The request carries your Forsk version and nothing about you.
• If you connect Rhino to your account, it sends your Mac’s name and its Rhino and Forsk versions, then checks your licence with forsk.app.
• A support report goes to forsk.app when you send one. See below.
• Chat sends what you type, and facts such as wall lengths and room names, straight to xAI with your own key. That never passes through forsk.app, and xAI’s own privacy policy applies.

When you send a report from Forsk’s Support card, I store its type, your message, your reply email, your Forsk and Rhino versions, your operating system, the debug report if you attach one, and a hash of your IP address that helps me stop spam. The raw IP address is never stored. The report is also emailed to me and filed as an issue in Forsk’s private GitHub repository so I can fix it. The public open tickets page lists each report only as its type, such as “Bug report”, with its status and dates, until I give it a public title and a summary that can’t identify you.

Email sent to any @forsk.app address is forwarded to my own inbox. forsk.app doesn’t store it. Resend keeps it for 30 days, and it stays in my inbox.

The basis for both is my legitimate interest in answering you and fixing Forsk. I delete support reports, and their copies on GitHub and in my inbox, 24 months after you send them. I keep other email as long as I need it to answer you.

forsk.app uses Vercel Web Analytics and Speed Insights to count page views and measure how fast pages load. They set no cookies and aren’t tied to your IP address. A visit is recognised only by a hash of the request, which is thrown away after 24 hours, so they can’t follow you to other sites or from one day to the next. Fonts and images are served from forsk.app itself, so a visit doesn’t reach Google or any other third party.

The only cookie is the dashboard sign-in cookie. It’s set when you sign in, and the dashboard can’t work without it. Like any web server, the host briefly processes your IP address to deliver pages and to block abuse. The basis for this is my legitimate interest in running a site that works and is fast.

These companies process data for me, under data processing agreements that let them use it only to provide their service:

• Vercel: hosts forsk.app and its server code, and provides the visit statistics. Vercel Inc., USA. Pages are served from the location nearest you; the server code runs in Frankfurt, Germany.
• Neon: the database for the waitlist, accounts, connected Macs and support reports. Neon, LLC (part of Databricks), USA. The database is stored in Frankfurt, Germany.
• Resend: sends the welcome, sign-in and support emails, and receives mail sent to @forsk.app. Plus Five Five, Inc., USA. It keeps the emails it handles for 30 days.
• GitHub: keeps support reports as issues in a private repository so I can fix them. GitHub Inc., USA.
• HEY: my own inbox, where mail sent to @forsk.app and copies of support reports end up. 37signals LLC, USA.

They’re all US companies, so data can reach the United States even where it’s stored in Germany. Vercel, Neon, Resend and GitHub are certified under the EU–US Data Privacy Framework, which the EU, and through the EEA Agreement Norway, treats as giving adequate protection. Their agreements also include the EU’s Standard Contractual Clauses. 37signals, which runs HEY, relies on the Standard Contractual Clauses.

You can ask to see, correct, export or delete your data, to limit or object to how I use it, or to withdraw your consent. Email julian@forsk.app.

If you think I handle your data wrongly, please tell me first. You can also complain to Datatilsynet, the Norwegian Data Protection Authority, at datatilsynet.no, or to the authority where you live.

Forsk is made for architects and isn’t meant for children under 16.