privacy
last updated
who we are
dithr is a calm space for creative work, bringing your projects, people and plans together - from the studio to the world. it’s run by Floating Waves. write to contact@dithr.space about anything on this page.
what dithr keeps
your account: your name and email, and the id Auth0 gives your sign-in. Auth0 handles every password, reset and email check: dithr never sees or stores your password.
who can join: dithr is by invitation. someone new gets in only if their email is on the list dithr keeps for that, or a team has invited them (an invitation lasts 14 days), and Auth0 has confirmed the address is theirs.
signing in with google: Google tells Auth0 your name, email address and profile picture, and nothing else, and Auth0 passes them to dithr. dithr keeps your name and email. signing in with Google gives dithr no way into your Gmail: that is a separate choice, set out under gmail below.
what you put in: tours, calendar items, contacts, budgets, messages, files, music, your catalogue, your inventory, your space and anything else you add, with the people in your teams and the emails you invite to join them. only you, the people in your team and the people you share something with can see it, apart from what you publish on a space page, a release page or a download gate, which anyone with the address can see. files are kept in private storage. an aiff you upload is turned into a wav in your browser first, and the wav is what is kept.
your profile card: what you choose to tell your teams for the road: dietary needs, coffee order, seat, cabin and stay preferences, work roles and frequent flyer programs. people in your team see which programs. the numbers, and the vehicle you take to the airport (make, model, colour and plate), are seen only by you and whoever books your team’s travel. super fund details are yours alone, and go into an export only when you tick them.
your settings: choices like your atmosphere, how the glass looks (the colour of its words, milk and smoke), your cities for the weather and the time, how far you’ve read each conversation and, if you allow them, notifications to your devices.
your calendar link: if you make one, a private link that shows your calendar in another calendar app. anyone who has the link can read your calendar, and “reset link” in the calendar makes a new one and stops the old.
what you send to dithr: the ideas and problems you send from support, with the part of dithr they’re about. only you and the people who run dithr can read them.
your mailing lists: when someone signs up on your space or downloads from one of your gates, they give their first name, last name, city and email. on a sign-up they tick a box to say yes to emails; on a gate the box is their choice, and without it they’re kept only so you know who downloaded, and sent nothing. dithr emails whoever ticked yes a link, and they join your mailing list only when they press it. dithr keeps the words they agreed to, and when. they’re kept in your audience, and they can unsubscribe at any time from any email. dithr stops sending to an address that bounces or marks an email as spam.
download gates: for each download gate, dithr counts page visits and download starts by country. the country is an approximate estimate from the visitor’s network, worked out by our hosting provider, Vercel, from the address the request comes from. dithr’s own database keeps only the two-letter country (or “unknown”) in monthly totals per gate: no ip address, city or precise location, and nothing linking a count to an email address, contact or download. Vercel handles those addresses to deliver every page and keeps its own short request logs under its own terms.
private listening links: when you send someone a private link to your music (an unreleased track or playlist, or an industry promo), dithr keeps the name, and the email if you gave one, that you made it for. it notes when the link is opened, played and how far, and any downloads, so you can see how it landed. you can give a link its own background picture, shown on that person’s page only; removing the person deletes it. if you allow it, they can leave comments at a moment in a track, and you can reply; a promo’s written feedback is kept too. dithr doesn’t note their address or device. it notes the approximate country of each open, play and download, which the sender sees beside that link’s activity.
release pages and ticket buttons: when you publish a release page or a show’s tickets button, dithr counts visits to the page, clicks on the places it sends on to (a streaming service, a ticket site) and ticket clicks. it keeps nothing about who made them: no name, address, device, precise location or cookie. for a ticket click it keeps the ticket site’s host name only, never the full address.
tracking links: a tracking link is a short dithr address you make for a release page, a download gate or a show’s tickets, so you can tell which post or placement worked. it forwards to the page and keeps its label, and the approximate country set out below, beside each visit, click, ticket click or download request that goes through it. a tracking link that is copied or forwarded keeps its label.
download gates and tracking links: when someone asks for a download through a tracking link, dithr keeps that label beside the details they gave, for their first ask only. dithr also notes, once, the moment it began sending the file to their download link: whether it finished isn’t known.
countries on pages and links: when someone opens a private listening page, an industry promo, a release page or a tracking link made in dithr, dithr notes the approximate country of that open, play, download or click. the country is estimated by our hosting provider, Vercel, from the visitor’s network. dithr keeps only the two-letter country: never the network address, a city or a precise location. on a link sent to a named person, the sender sees the country beside that link’s activity. it is an estimate from the network the link was opened on, not proof of who opened it or where they are. countries are kept for 24 months, then deleted, and sooner if the link or page is deleted. dithr leaves out your own opens and your team’s, and the automated link previews it recognises; some automated previews may still be counted. download gates keep monthly country totals, as set out under download gates.
services you connect
only when you connect them, and you can disconnect any of them in settings, under integration. gmail, youtube and instagram have their own parts below.
your audience numbers: for the artist’s own YouTube, Instagram, Facebook and TikTok, read only: the followers of a Facebook page you choose, and the followers, likes and videos of a TikTok account. SoundCloud’s numbers are the public ones its profile shows, read from the profile link with no sign-in. dithr keeps the latest figures and the account’s name with the artist’s space, and whoever that space lets near its audience can see them.
buffer: sends the posts you make in dithr to Buffer to publish, and only when you ask it to. your Buffer key is kept encrypted.
your shop: dithr reads your Big Cartel or Shopify store’s public catalogue.
a calendar you link: the private address of a Google, Apple or Outlook calendar, if you give dithr one, so that calendar’s events show in your dithr calendar. dithr keeps the address encrypted, with the name you gave it, and nothing else of the calendar: its events are read when you open your calendar, held in the server’s memory for up to 15 minutes and not stored, and only you see them, in every space. dithr only reads the calendar: nothing in dithr is ever added to it. “remove” on a linked calendar in the calendar’s filters, or closing your account, deletes the address. anyone who has a calendar’s private address can read that calendar, so keep it to yourself, and reset it in Google, Apple or Outlook if it gets out.
the keys these services give dithr are encrypted, stay on dithr’s server, never reach a browser and are never written to logs.
gmail
you connect Gmail from settings, and Google’s own screen asks you first. dithr asks Google for these permissions and no others:
openidandemail: to know which Google account it is.https://www.googleapis.com/auth/gmail.readonly: to read your emails and their attachments. apart from the emails you send, dithr never changes, labels, archives or deletes anything in your Gmail.https://www.googleapis.com/auth/gmail.send: to send emails as you, when you press send or when a scheduled email’s time comes.
you can leave the send permission unticked on Google’s screen. dithr then shows your email and can’t send any.
what dithr reads, and when: open the gmail tab and dithr asks Google for your inbox: each email’s sender, subject, a line of preview, its time and whether you’ve read it. open an email and it asks for the whole conversation: the words, the email as it was designed, who it went to, and the name, type and size of each attachment. a search you type goes to Google, which finds the emails. an attachment is fetched from Google only when you open or download it, passed to your browser, and not kept.
what dithr keeps: your emails stay with Google: dithr doesn’t copy them into its database. to make the inbox quick, the server may hold each email’s sender, subject and preview line in its memory for up to ten minutes. what dithr keeps in its database is the Google account’s address and id, and the keys below. so that an email you have opened in dithr stops showing as unread there, dithr also keeps, for each conversation you opened, its id and the time of its newest email (the 200 newest at most). nothing is sent to Google: it still shows the email as unread. disconnecting the account deletes them.
how an email is shown: an email’s design is shown in a sealed frame where nothing in it can run. its pictures load from the sender’s own servers when you open it, without telling them which page you’re on, so the sender can tell they were fetched. pictures that came inside the email are fetched from Google through dithr, as an attachment is, and not kept. dithr leaves out the one-pixel pictures senders use to track opens. for a link in an email, dithr’s server asks that site for its title and picture, so your browser never does, and keeps the answer in memory for six hours.
sending: an email you send goes straight to Google, from your account, and dithr keeps no copy. files you attach wait in private storage, in a folder of your own, until the email is sent, then are deleted. if you close the page first, dithr clears left-over files once they’re a day old, the next time you attach a file.
scheduled emails: Gmail has no scheduled send, so dithr holds the email until its time: the words, who it goes to (to, cc and bcc), the subject, which of your accounts it goes from, the time you chose and any attached files, which wait in private storage. at that time dithr sends it through Google as you. only you can see, change or cancel it. once it’s sent, or you cancel it, the words and files are deleted at once, and the people, subject and time are kept 30 days more, then go too. an email that couldn’t send is kept so you can send it again, and goes 30 days after.
keys: when you connect, Google gives dithr a short-lived access key and a longer-lived refresh key. dithr keeps both encrypted (AES-256-GCM) in its database, with a secret that isn’t in the database. they are opened only on dithr’s server, to talk to Google, and are never sent to a browser or written to logs.
disconnecting: disconnect an account at any time, in settings under integration or in the gmail tab. dithr tells Google to cancel its access, deletes the keys and the record of the account, and deletes any email waiting to be sent from it, with its files. you can also cancel dithr’s access yourself, at any time, at Google’s permissions page.
youtube
this is for the artist’s audience numbers. dithr uses YouTube API Services. by connecting a channel you agree to be bound by the YouTube Terms of Service, and Google’s Privacy Policy applies to what YouTube hands over.
a link alone: if you give dithr only a link to a channel, it reads the channel’s public counts (subscribers, views, videos) with a key of its own, at most every six hours. nothing is connected.
a connected channel: Google asks you for two read-only permissions: https://www.googleapis.com/auth/youtube.readonly and https://www.googleapis.com/auth/yt-analytics.readonly. dithr reads the channel’s name or handle, its subscriber, view and video counts, and from YouTube Analytics the last 28 days of views, minutes watched, and subscribers gained and lost. it reads nothing else: not your videos, comments or viewers.
what dithr keeps: those numbers and the channel’s name, with the artist’s space, read again when they’re more than six hours old, and the keys, as set out under gmail. whoever the space lets near its audience can see the numbers.
revoking access: disconnect the channel in settings, under integration: dithr tells Google to cancel its access and deletes the numbers and the keys. you can also revoke dithr’s access at Google’s permissions page. do that alone and dithr can no longer read your channel, but it still holds the last numbers until you disconnect it in dithr or write to contact@dithr.space.
dithr uses Meta’s own API for Instagram, through its unified login (Facebook Login for Business), for professional accounts (business or creator) only. you log in with Instagram or Facebook, then choose the business portfolio and the Instagram accounts to share. no Facebook Page is needed.
audience numbers: Meta asks you for instagram_basic and instagram_manage_insights. dithr reads the account’s handle, its followers and number of posts, and its reach and views over the last 28 days. it’s read only, and kept as the other audience numbers are.
messages: Meta asks you for instagram_basic and instagram_manage_messages. dithr reads your conversations when you open message: the handles of the people in them, the latest 20 messages of a conversation and their times. it sends the replies you write, and the reactions and files you choose, within 24 hours of the other person’s last message, as Instagram requires; a reply or file you write can go up to 7 days after it, marked as one a person wrote, if Instagram allows it, and if it doesn’t dithr keeps the time of that refusal for an hour so it doesn’t keep asking. dithr keeps no message text and no reactions. a copy sits in the server’s memory for under a minute to keep the screen quick. to show which conversations are unread, dithr keeps, for each recent conversation, its id, the time of the other person’s newest message and the time of the newest one you were shown by opening the conversation in dithr: for the 50 newest conversations at most, and only those from the last 7 days. disconnecting the account deletes them. when someone shares a reel or post in an Instagram message, Instagram tells dithr as it arrives, and dithr keeps the link to it, and its title if it has one, with that message for up to 7 days so it can show it to you, the newest 100 for an account at most. disconnecting the account deletes these too. a photo, video, audio file or pdf you send is kept in dithr’s private file store only until Instagram has its own copy: it’s deleted as soon as dithr sees the message in the conversation, and never kept longer than an hour whatever happens. nobody else can open it, and the link dithr gives Instagram stops working after ten minutes.
your business portfolio: Meta also asks you for business_management, shown as “manage your business”. it lets Meta hand the Instagram account you choose to dithr inside your business portfolio. dithr uses it for nothing else: it never reads or changes the portfolio’s settings, people, pages or ad accounts.
keys: kept encrypted, as set out under gmail.
taking dithr’s access away: disconnect the account in settings, under integration: dithr deletes its connection and its keys. dithr doesn’t cancel its own access with Meta, so also remove dithr in your Meta business settings, under integrations, connected apps.
asking for deletion: if you remove dithr in Meta, or ask Meta to delete the data dithr holds about you, Meta tells dithr and dithr deletes its connection to your account at once, the one for audience numbers included, with the unread marks kept with it. it gives Meta a confirmation code and a page where you can check. dithr keeps no messages of yours, so the connection is all there is to delete. you can also write to contact@dithr.space.
google user data
dithr's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
in plain words: what dithr gets from Gmail and YouTube is used only to show it to you in dithr, to send the emails you ask it to send, and to show your channel’s numbers. dithr doesn’t use it for advertising, doesn’t sell it, and doesn’t use it to train artificial intelligence or machine-learning models. it goes only to your screen, to Google and to the services that run dithr (below). no one at dithr reads it unless you ask us to look into a problem and agree, it’s needed to look into abuse or keep dithr secure, or the law requires it.
who helps run dithr
Vercel hosts dithr and stores your files. Supabase runs its database. Auth0 handles signing in. Resend sends the emails dithr sends: a team invitation, a shared calendar item, the link that asks someone to confirm a mailing list sign-up, and the emails an artist sends to their mailing list, which come from send.dithr.space. Resend tells dithr when one bounced or was marked as spam, so dithr stops sending to that address.
when something breaks, dithr reports the error to Sentry: what went wrong and where in dithr, and nothing about you. no name, email, cookies, or what you typed or were looking at, and the code in a private link’s address is taken out. where your browser sends the report, Sentry also sees your device’s internet address, as any site you visit does.
the weather and finding places use Open-Meteo, OpenStreetMap, Photon and Wikipedia (for a city’s photo): they’re sent a city, a place you typed or its position, nothing about you. where your browser asks them, they also see your device’s internet address, as any site you visit does. a show list can come from Bandsintown. if you add your own Google Maps key in explore, your browser loads Google Maps with it. a page that shows a video or player loads it from its own service (YouTube, Vimeo, SoundCloud, Spotify, Canva). currency rates come from public rate services, and notifications reach your devices through their own push services (Apple, Google, Mozilla).
some of these may keep data outside your country.
cookies
one to keep you signed in. two that remember your time zone and today’s sunrise and sunset, so pages open in the right light, while your light follows the time of day. short-lived ones while you sign in, or connect Google, Instagram or another service. a few preferences are kept in your browser. no advertising, tracking or analytics cookies.
what dithr doesn’t do
dithr doesn’t sell anything about you, show advertising, run analytics on what you do in dithr (the counts on your own release pages, gates and tickets buttons are set out above), or send your content to artificial intelligence services. to keep itself working, its server log counts how many requests each page gets, without who made them, their cookies or what they asked. to slow down spam and guessing, a form or a private link may count tries from an internet address in the server’s memory for a few minutes: it is never stored.
keeping and removing
what you put in is kept while your account is open, and you can delete it at any time; a file goes from storage with whatever it belonged to, unless something else of yours still uses the same file. hiding something only tidies your view. disconnecting Gmail, YouTube or Instagram deletes the keys and what dithr kept through them, as set out above.
you can close your account yourself, in settings, under profile, at the foot. it happens at once: there is no grace period, and it can’t be undone. dithr tells Google to cancel the access you gave it, deletes what is yours (your profile, settings, your own space and its files, the keys of every service you connected) and your sign-in at Auth0, and signs you out. what you made in a team stays with the team, and so do the messages you sent, shown as “deleted account”. a team you alone own, with other people in it, passes to the person you pick before you delete; one with nobody else in it is deleted with you. copies in Supabase’s daily backups of the database are kept for 7 days, then gone. write to contact@dithr.space if anything of yours is left.
a gate’s country totals are kept for 24 months, then deleted. they are deleted with the gate. a gate that belongs to a team stays with the team, and so do its totals, when one member deletes their account; gates in a person’s own studio are deleted with that account. the database host’s automatic backups are kept for seven days; backups taken by hand before a release are kept for up to 30 days, then deleted.
your say
you can ask what dithr holds about you, have it corrected, or take a copy, by writing to contact@dithr.space. to have it all removed, close your account in settings, as above.
changes
when this changes, this page and its date change with it. the date at the top is when it last changed.