Privacy

Updated November 9, 2026

This note explains what happens to your information on warofart.org. It’s short because the site collects very little, and only what it needs.

Messages you send

When you use the form on the Contact page, your name, email address and message go to Web3Forms, a service that delivers them to my inbox as an email. The site itself doesn’t keep a copy. I use your details only to reply to you, and I don’t add you to any mailing list. Web3Forms handles the message on its way under its own privacy policy.

Booking a meeting

The calendars on the Consulting page come from Cal.com, and nothing loads from Cal.com until you choose a service. If you book, the details you enter, such as your name, email and notes, go to Cal.com and to me so we can hold the meeting, under Cal.com’s privacy policy. Cal.com may set its own cookies once its calendar has loaded.

Your account

If you make an account on the Network, the site keeps the phone number or email address you sign in with, so it can send you sign-in codes or links, and whatever you add to your profile: your name, profile address, craft, discipline, city, bio, the Currently and Next lines, your links, a public email if you choose to show one, your photo, the work in your folder (images, PDFs, videos, audio tracks, and links to pieces on Vimeo, YouTube or SoundCloud) with their titles and captions, and, if you offer consulting, what you consult on and the address of your booking page. Bookings made through that page happen on that service, not on this site. It’s stored with Supabase, which runs the site’s database and file storage, under Supabase’s privacy policy. Sign-in codes by text are sent through Twilio, under Twilio’s privacy policy, and sign-in emails through Resend, under Resend’s privacy policy. Your phone number is used only to sign you in: texts go out only when you ask for a code, and your number is never shared or used for marketing. Accounts are made with a phone number; an email you add for notices, and to sign in, is kept the same way.

The join and sign-in forms use Cloudflare Turnstile to check that you’re a person before a code or link is sent, which keeps automated sign-ups (and the cost of their texts) away. It loads only on those forms and handles your visit under Cloudflare’s privacy policy.

If your account has an email, I send it two kinds of email from the site, and never marketing: notices about your profile (one when it goes live on the Network, and one reminder if your set-up stops partway), one email each time another member asks to connect with you, and at most one email a day when new messages are waiting for you.

Your profile stays private until it’s complete. Once it’s on the Network, the details on your profile and the work in your folder are public, including a public email if you add one. The phone number and email address you sign in with never are. A photo or image you add is cropped and resized on your own device before it’s uploaded, which also removes the hidden camera details, such as location, that phone photos often carry. PDFs, videos and audio tracks are uploaded as they are, so remove anything in them you don’t want public before adding them. For a link to Vimeo, YouTube or SoundCloud, the site asks that service for the piece’s title and still picture; nothing from you is sent with that request.

Messages between members are kept with Supabase too, and only the two members in a conversation can read them. I don’t read members’ messages; the one exception is a conversation one of its members reports to me, which I then read to look into it. I can see how many messages are sent across the Network in total, never who sent them or what they said. The site notes when each of you last read a conversation, to show “Seen” and to send the daily email. Connections between members are kept the same way. Who you are connected to, and requests you’ve sent or received, are seen only by you and the other member; on your public profile only the number of members you’re connected to shows. If you block a member, only you can see that, and it isn’t shared with them. If you report a profile, the reason you choose and anything you write come to me. To limit how many reports one person can send, the site keeps a one-way code made from your network address (it can’t be turned back into the address), and never your name or contact details.

Group conversations are kept the same way, and only the people in a group can read it; a member who leaves stops seeing new messages. As with conversations, I read a group’s messages only if one of its members reports it to me.

If you apply as a brand, the site keeps your company’s name, website and category, what you make and what you’re looking for, your name and role, and the email you apply and sign in with, with Supabase as above. Nothing about the brand is public until I approve it; then its page (everything except the email it signs in with) is public. Briefs a brand sends are read only by that brand and by me: I use them to find the artists who fit and put them in touch through Messages.

Questions and answers you post in the forum are public on the web, with your name, craft and photo beside them, as on your profile. The site keeps which questions you follow, to send you at most one email a day about new answers, and only you can see that list. If you report a post, the reason you choose and anything you write come to me, kept as with other reports.

To delete your account and everything on it, email me and I’ll remove it.

What the site remembers

The site sets no tracking cookies and uses no outside analytics company. It does keep its own simple count, so I can see how the site is doing: how many visitors it has each day, which pages they read, where they came from (such as Instagram or a search engine), whether they’re on a phone or a computer, and how many pressed Book consultation, finished a booking or opened the Join window. These are kept with Supabase only as daily totals. No name, IP address or identifier is stored with them, and there’s no record of what any one person did, so the totals can’t be traced back to you.

If you sign in, a cookie keeps you signed in on that browser until you sign out; it’s used for nothing else. Otherwise the site saves three things in your own browser: when you last entered from the opening screen, so it doesn’t show you that screen again for a day; when you last closed or used the invitation to join the Network, so it stays away for a week; and today’s date with what has already been counted from this device today, so you aren’t counted twice in a day. None of these leaves your device, apart from the count itself, and clearing your browser’s data for this site removes them.

Hosting

The site is hosted by Vercel. Like any web host, Vercel handles basic technical information, such as your IP address and the pages you request, to deliver the site and keep it secure, under Vercel’s privacy policy. The short videos on the About page are stored with Supabase and load from there only when you press play, under Supabase’s privacy policy. The longer films there play from Vimeo, which also loads only when you press play; the player is set not to track you or set cookies, and Vimeo handles the visit under its own privacy policy. The same goes for work members link to on their profiles: the player from Vimeo, YouTube or SoundCloud loads only when you press play (YouTube’s privacy-enhanced player, and Vimeo’s set not to track you), and that service handles the visit under its own privacy policy (Vimeo, YouTube, SoundCloud). Until then, the still you see is served from this site.

Links elsewhere

Links to Substack, Instagram and LinkedIn take you to those sites, which have their own privacy policies.

Seeing or deleting your information

You can ask me to see or delete anything you’ve sent or added to your account. Email calebsmdesign212@gmail.com and I’ll take care of it.

Changes

If the site starts collecting more, for example when paid plans arrive, this note will say so before that happens.