Draft for legal review. This page will be finalised before the pilot opens.

Privacy Policy

buildIt.social is a team chat, video meeting, screen sharing and remote control service for small and mid-sized businesses. It is run by Kamm Creative Solutions, LLC (“we”, “us”). This policy explains what we collect when you visit this website or use the buildIt.social apps for Windows, macOS, iOS, Android and the web, why we collect it, who else handles it, and how long we keep it.

buildIt.social is organized into orgs: workspaces that a business creates and whose admins decide who joins. Most of what you put into buildIt.social, such as messages, files and pages, belongs to the org you posted it in.

This website

• This website sets no cookies, runs no scripts and has no analytics or advertising trackers.
• Its fonts and images are served from this site, so your browser doesn’t contact any other company to show it.
• It is hosted on Cloudflare Pages. Like any web host, Cloudflare processes your IP address and the details of each request in order to deliver the pages and protect the site from abuse.
• The site has no forms and doesn’t ask you for any information.

What we collect when you use buildIt.social

Your account

• When you create an org on the web, we collect your name, your work email address, the org’s name, a password and your language. We confirm the email address with a 6-digit code.
• When you join an org, you do so through a single-use invite link that an admin sends to your email address. Invite links expire.
• Your profile: your name and, if you add one, a profile picture. You can have a different profile in each org. Guests in an org can’t see other people’s email addresses.
• Your password is stored only as a hash. We don’t ask for a phone number, and there is no sign-in through Google, Apple or other accounts.
• Two-factor sign-in is optional, unless an admin of your org requires it. It uses an authenticator app. If you set it up, you get ten single-use recovery codes, which we store only as hashes.

What you and your team create

• Messages, threads, reactions, mentions and the files, photos and videos you share.
• Pages (each channel’s wiki), project items, and your Schedule: working hours, time off and holidays. Guests never see working-hours details.
• Your status, which people who share an org with you can see.
• Location in photos and videos: your device removes GPS and other location data from photos and from MOV and MP4 videos before they upload. A photo that is downscaled before upload (the default) keeps no metadata at all. So does a video that your phone compresses before upload.

Calls, screen sharing and remote control

• Calls aren’t recorded. Audio, video and shared screens pass through Cloudflare’s realtime service on their way to the other participants, and they aren’t stored.
• Every call goes through that service, even a call between two people, so participants never see each other’s IP addresses.
• We keep a history of calls: who joined, when, and for how long. Missed and declined calls appear in the conversation.
• Remote control lets a presenter on Windows or macOS hand one viewer their keyboard and mouse. The presenter has to agree each time, for 5, 15, 30 or 60 minutes. A banner shows for as long as someone has control, and everyone in the call can see who controls whom.
• We keep a record of remote-control requests, grants, refusals, starts and ends: who was involved, which devices, how long, and why it ended. We never record keystrokes, typed text, pointer positions or window titles.

Devices and notifications

• For each device you sign in on, we keep a session, and a push token on phones and in browsers where you allow notifications.
• Notifications can include the sender and the text of the message. You choose how much is shown in Settings: the full message (the default), only the sender, or nothing.

Billing

• Orgs pay through Stripe. Your card details go to Stripe and are never stored by us. Stripe, through its Link service, is the merchant of record: it charges the card, handles sales tax and sends receipts and invoices.
• We keep the org’s Stripe customer and subscription ids, the subscription’s status, a copy of its invoices (amounts and links), and a daily count of each org’s active users, which is what an org is billed on.
• To allow one free trial per person and per card, we keep a hash of the email address used to sign up and a keyed hash of the card’s fingerprint. We can’t turn either back into the address or the card.

Optional features

• GitHub linking. If an org connects GitHub, we store metadata about the repositories it chooses: repository and branch names, commit ids and the first line of each commit message, pull request numbers, titles and states, author logins, links and times. We never store code, diffs, file paths, email addresses or pull request descriptions.
• Agent access. If an org admin turns it on, members can create personal tokens that let an AI assistant or script act as them in one org, with the permissions they choose. Tokens expire (after 7 to 365 days) and can be revoked at any time. They can never read direct messages. We store tokens only as hashes, label every change made through one with its name, and keep a log of their requests, without their content, for 90 days.
• AI. buildIt.social doesn’t send your content to any AI service today.

Crash reports

• When the apps for iOS, Android, macOS or Windows, or our server functions, hit an error, they send a crash report to Sentry. The web app sends none.
• Reports contain the type of error, a scrubbed description, where in the code it happened, the app version, the device model and operating system, language, time zone, memory and storage, and an anonymous id for the installation.
• Reports are scrubbed of message content, file names, email addresses, tokens, file paths and IP addresses. They carry no user id, name or org. Sentry is set not to store IP addresses.

Server logs and security

• Our servers log requests, including IP addresses, to keep the service running and secure. Logs are rotated out by size.
• The sign-up form on the web is protected by Cloudflare Turnstile, which checks that a person, not a bot, is signing up.
• Each org has an audit log of important changes, such as membership, roles and settings, that its admins can read.

How we use it

• To run buildIt.social: deliver messages, calls and notifications, keep your apps in sync, and show each org only its own data.
• To bill orgs, enforce plan limits and prevent abuse of free trials.
• To keep the service secure, investigate problems and fix crashes.
• To send you the emails the service needs, such as invites, sign-in codes and password resets.

We don’t sell your information, we don’t show ads, and the apps contain no analytics or advertising trackers.

Who else handles your information

We use these companies to run buildIt.social. Each gets only what it needs for its job.

Things that connect from your device

• GIFs. When you search for a GIF or see one, your device connects to KLIPY directly, so KLIPY sees your IP address. We keep only which GIFs you sent, your 50 most recent and your favorites.
• Embedded videos and posts. YouTube, Vimeo, Loom and TikTok videos play inside the app after you tap them. Reddit, Threads, Instagram, Facebook and X posts load when you tap “Load post”. Each provider then sees your IP address and may set its own cookies. Org admins can turn embedded players off.

Link previews

• When you send a link, our server, not your device, fetches the page to make a preview card. The website sees our server’s address and your language, never your IP address or any cookies.
• Each card is a saved snapshot: its image is copied into our storage, so viewers don’t contact the website either.
• You can turn previews off for yourself. Admins can turn them off for the org or block domains. The sender and admins can remove a preview.

Where your data is kept, and how it’s protected

• Your data is stored in the United States: the database on Hetzner servers in Ashburn, Virginia, and files and backups on Cloudflare R2 in eastern North America.
• Connections to our servers are encrypted. Calls are encrypted between your device and Cloudflare’s realtime service.
• Messages and calls are not end-to-end encrypted. Our servers and Cloudflare’s realtime service can technically access their content.
• Each org’s data is kept apart from every other org’s by rules enforced in the database itself.
• Backups are encrypted before they leave our server.
• The apps keep a local copy of your orgs’ data so they work offline. On Windows, macOS, iOS and Android, it’s encrypted with a key held in your device’s secure keychain. In a browser, it’s kept only in memory. A video waiting to be compressed on a phone is stored unencrypted until it is compressed.
• The local copy is wiped when you sign out, when you leave or are removed from an org, when you delete your account, and if a device hasn’t been able to confirm your membership for 30 days.
• Our own admin tools show counts, billing data and ids, never people or content, and record every use.

How long we keep it

• Your account is kept until you delete it.
• Messages: deleting a message removes its text. Files attached to a deleted message are kept.
• Org data is kept while the org exists. If an org cancels its subscription, it stays readable but can’t be changed, and it is deleted 90 days after cancellation. The org’s admins are emailed 30 days and 7 days before.
• Backups are kept for about a month, so deleted data can remain in them until they expire.
• Audit logs are kept for the life of the org.
• Agent token request logs: 90 days. Billing activity records: 400 days. Link preview cache: 24 hours.
• An org sign-up that was never completed is deleted after 7 days.

Deleting your account

You can delete your account yourself, in the app (Settings, then You) or in the web app. When you do:

• We delete your sign-in, your profile (name and picture), your devices and push tokens, your settings, reactions, agent tokens and invites, and any direct message with nobody else left in it.
• Your messages and files stay in your orgs’ channels and conversations, shown as “Deleted user”, because they belong to the org.
• Org audit logs keep their records, with your email address and GitHub login blanked out.
• If you are the last owner of an org, you need to hand ownership to someone else, or have the org deleted, before you can delete your account.

Your choices and rights

• You can see and change your profile, notification previews, link previews and two-factor sign-in in the app’s Settings.
• For anything in an org’s workspace, such as messages others posted, your first contact is that org’s admins.

Children

buildIt.social is a service for businesses and isn’t meant for children.

Changes to this policy

We’ll post changes on this page.

Contact

buildIt.social is run by Kamm Creative Solutions, LLC. Contact details will be posted on this page.