Draft version
Part 1: common to the whole service
This policy has a part common to the whole service, then a section for each platform or service (part 2).
1. Controller
Corentin Chopin EI (sole proprietorship, entreprise individuelle), trade name Digi-Nord, 11 Rue Eugène Livois, 62200 Boulogne-sur-Mer, France (digi-nord.eu), which runs Dispatch.IO (website, bots and Android app). Contact for anything about your data: [email protected].
2. Your Dispatch.IO account
- your account: id, name, picture, email address (given by the first linked account that provides one), the list of your linked accounts (Discord, Fluxer, Stoat, Facebook) and your preferences;
- your sessions (IP address, browser or app, dates) for security, and an audit log of the administration;
- your exchanges with the support.
The data read on each platform is described in part 2.
3. Why
To provide the features of the bots, the dashboard and the app, keep the service secure (anti-abuse, bans, audit), manage subscriptions and billing, and answer your requests.
4. Legal bases
Performance of the service you use (terms of use and sale), our legitimate interest (security, preventing abuse), legal obligations (billing), and your consent for audience measurement.
5. Retention
[To complete: retention periods, e.g. data of a server deleted [X] after the bot is removed, sessions kept [X], invoices kept 10 years.] The retention of the My networks data is given in sections 16 and 17.
6. Recipients
Data is only accessible to the Dispatch.IO team, as needed for their role. Subcontractors: [hosting provider and location], Stripe (payment), Google (audience measurement, only with your consent). Each platform (Discord, Fluxer, Stoat, Meta, Google, Twitch) receives what the service sends it for the features you use. Some of them are outside the European Union; transfers then rely on the safeguards provided by the GDPR. No data is sold.
7. Your rights
You can access, correct or delete your data, object to or limit its processing, and ask for its portability, by writing to [email protected]. You can also file a complaint with the CNIL (cnil.fr).
8. Cookies
The website uses the cookies needed to work (sign-in session, language and display preferences) and, only if you accept it in the banner, Google Analytics audience measurement. You can change your choice at any time with Manage cookies at the bottom of the pages. No advertising cookie.
9. Changes
This policy can change. The date of the last update is shown on this page.
Part 2: each platform or service
Linked channels (all bots). When the managers of a server link one of its channels to other servers (Linked channels page of the dashboard), the messages you post in that channel (text, attachments, replies, edits, deletions and reactions), with your display name and avatar, are copied to the channels of the other servers of the group, on Discord, Fluxer, Stoat or Twitch, where those servers' and platforms' rules apply. Deleting your message deletes its copies. For the group's moderation, Dispatch.IO keeps a log of these messages (author, platform, server, excerpt) and the link between each message and its copies for 7 days, then deletes them automatically.
10. Discord
When you use the bot on a server:
- your Discord id, username and avatar;
- activity used by the enabled features: XP and levels, streaks, statistics (messages, voice time, commands), tickets and their transcripts, moderation actions (warnings, sanctions);
- what server administrators configure (messages, images, roles).
When you sign in with Discord: your Discord profile (id, username, avatar, banner) and email address provided by Discord, and the list of your servers (Discord "guilds" access), to show the ones you manage. Discord's own policy: discord.com/privacy.
11. Fluxer
When you use the bot on a community: the same kind of data as on Discord (id, name and avatar, activity used by the enabled features, configuration of the administrators).
When you sign in with Fluxer (permissions identify, email, guilds): your Fluxer profile (id, username, display name, avatar, banner), your email address, and the list of your communities, to show the ones you manage. Fluxer's own policy: fluxer.app/privacy.
12. Stoat
When you use the bot on a server: the same kind of data as on Discord (id, name and avatar, activity used by the enabled features, configuration of the administrators).
When you sign in with Stoat: Stoat has no sign-in for apps; you confirm by sending a code to the bot in a private message. We receive your Stoat id, username, display name and avatar; Stoat gives no email address. Stoat's own policy: stoat.chat/legal/privacy.
13. Android app
- Your session is kept in the phone's secure storage and ends when you sign out of the app.
- The app checks for its updates on the website and downloads them from it; that's why it asks for Android's permission to install apps. It reads no contacts, location, photos or files.
- The music search of the app queries YouTube directly from your phone: YouTube then receives your search and your phone's IP address, under its own rules.
- Sign-in and the data of the platforms are the same as on the website (sections 10 to 12 and 16).
14. Premium and payments (Stripe)
Your subscription and the references of your payments and invoices. Payment details are handled by Stripe only (Stripe privacy policy).
15. Linked accounts
Each sign-in method adds its account to your Dispatch.IO account. Unlinking it in Linked accounts removes it from your Dispatch.IO account; the data that the bots keep on a server stays under the rules of that server's features.
16. Facebook and Instagram
Controller for this section too: Corentin Chopin EI (sole proprietorship, entreprise individuelle), trade name Digi-Nord, 11 Rue Eugène Livois, 62200 Boulogne-sur-Mer, France (digi-nord.eu), which runs Dispatch.IO (contact: [email protected]). Meta's own rules: Meta Terms of Service, Meta Privacy Policy, Instagram Terms of Use.
Dispatch.IO uses Meta in two separate ways. Signing in with Facebook (your identity) and the accounts linked to post (My networks relay) are not the same thing: signing in with Facebook never lets Dispatch.IO post anything, and linking a Page to post on it never signs you in.
Sign in with Facebook (website and Android app). Through Facebook Login for Business, we receive your Facebook id (specific to our app), your name, your profile picture and your email address if Facebook provides it. They are used only to sign you in to your Dispatch.IO account and to show your name and picture in your space. The Instagram button of the sign-in page uses the same Facebook sign-in: Meta doesn't offer an Instagram sign-in to new apps, so you sign in with the Facebook account linked to your Instagram. To stop using it, unlink Facebook in Linked accounts of the dashboard, or remove Dispatch.IO from your Facebook apps (Settings › Security › Apps and websites).
My networks relay. The My networks page of the dashboard posts the new videos and lives of the YouTube and Twitch channels you add (yours or any public channel) on your Facebook Page and your Instagram account. It is only used if you set it up. Data we process:
- Facebook: your app-scoped id, your name and picture, the Pages you can post on (name, picture, id) and their access tokens (permissions pages_show_list, pages_read_engagement, pages_manage_posts).
- Instagram: linked through Facebook Login for Business (Instagram API with Unified Login): the id of your business portfolio, the id, username and picture of the professional accounts you pick, and the access token of your portfolio (permissions instagram_basic, instagram_content_publish).
- Your relays: their settings and texts, and the history of their posts (title and link of the video, destination, date, id of the post, error if any).
Why: only to sign you in, and to post, at your request, on your own accounts, the videos and lives of the channels you chose. Nothing is posted without a relay you created. This data is never used for advertising, never sold or shared, and never used to train AI models. Meta data is processed in line with the Meta Platform Terms.
Security: Meta tokens are encrypted (AES-256-GCM) in our database. Only the pictures posted (cards) are public, for one hour, the time for Instagram to download them.
Retention: as long as the account stays linked. Tokens are never renewed behind your back: an Instagram access with an end date is marked "to reconnect" a few days before; a token Meta refuses is no longer used and the account is marked "to reconnect". The history is kept as long as the relay exists.
Deleting this data: "Remove" on an account or a channel in My networks deletes it at once; unlinking Facebook in Linked accounts ends the Facebook sign-in; removing Dispatch.IO from your Facebook apps (or from your business portfolio's integrations for Instagram) erases its access; a deletion request sent from Facebook deletes your Facebook accounts, the Instagram accounts linked to the same Dispatch.IO account and your sign-in with Facebook, and can be followed on the data deletion page (your Dispatch.IO account itself stays; if Facebook was its only sign-in, you are signed out and can write to us to get it back or delete it); deleting your Dispatch.IO account deletes everything. You can also write to [email protected].
17. YouTube and Twitch (public data)
The channels you add to the My networks relay (by their link or their name, yours or any public channel) are read through the official APIs, with public data only: no sign-in to YouTube or Twitch, no access to your accounts there.
- YouTube: the channel's id, name, address and avatar, and its new videos (title, link, picture). Dispatch.IO uses YouTube API Services: by using this feature, you agree to the YouTube Terms of Service, and the Google Privacy Policy applies.
- Twitch: the channel's id, name, login and avatar, and its lives (title, game, link), read through Twitch's API. Twitch's rules: Terms of Service, Privacy Notice.
These channels are kept as long as they stay in My networks; "Remove" deletes them at once.
