Who we are
Multimedia Monster ("we") sets up, connects and posts social media for brands from its own server. This policy explains what we store when a brand uses the service and when a brand's person connects an account to us.
It covers three groups of people: the brands (businesses) that use the service, the people who act for a brand (for example, the person who approves our app on a network), and visitors to this website.
What we store
| What | Details |
|---|---|
| Connections | The access a network grants us when a brand's person approves our app on that network's consent screen, or the access key or webhook address that person enters on our connect page. These let us post for the brand. |
| Account identifiers | The identifiers we need to post and confirm posts, such as a Page or channel identifier, an Instagram account identifier, a blog or board name, a member identifier, or a Discord server and channel identifier. |
| Connection dates | When each connection was made and when it expires. |
| Account details | For each of the brand's network accounts we work on: the sign-in email, how two-step sign-in is set up, who holds the owner and admin roles, and our role. |
| Sign-in details, only where needed | Where a network does not give us API access, and only if the brand asks us to post there, we may sign in to the brand's account through a browser on our server. For that account we hold the sign-in details the brand gives us, kept secured like the brand's other access (see protection). |
| Content | The videos, captions and related details the brand supplies for posting. |
| Post records | What we posted, on which network, when, its status and, where the network returns one, its public link. |
| Contact details | Names and work email addresses of the brand's people we deal with. |
How we use it
- To set up and repair the brand's accounts, connect them, and post the brand's content to the networks the brand chose.
- To confirm each post went out and show the brand what was posted and when.
- To tell the brand when a connection needs renewing or a network reports a problem.
A brand's connections are used only for that brand's posts. We do not sell this information, we do not use it for advertising, and we do not use it to train AI models.
The visual check
Every post is reviewed visually before it is published, including by an AI model. For that review, still images from the video are sent to an AI model service, which uses them only for the check.
Who receives it
- The network a post is for. Content and the connection for that network go only to that network.
- Providers that run our service: the companies that host our server and store our data, the AI model service used for the visual check, and, only for accounts we post to through a browser, the browser and network-connection providers we use for that.
- When the law requires it.
Google and YouTube data
When a brand's person connects a YouTube channel, they approve our app on Google's consent screen. We use YouTube API Services.
- What we access: permission to upload videos to the channel, to read the channel's identifier and the status of videos we uploaded, and to read YouTube Analytics figures for the channel.
- How we use it: to upload the videos the brand gave us, confirm each upload, and report results to the brand. Nothing else.
- How we store it: the access Google grants us is kept secured on our server; the channel identifier and post records are kept with the brand's records.
- Who we share it with: no one beyond the providers that run our service, listed above. Google user data is not sold or passed to anyone else.
- How to remove it: remove our app's access in the Google Account's third-party access settings, or ask us on the data deletion page.
How we protect it
- The access a brand grants us, and any sign-in details it gives us, are kept secured on our server and used only to work on that brand's accounts.
- They come from the brand's own person, through the network's consent screen or our connect page, and are not shown back on screen after entry.
- We never ask for them by chat or email, and we keep them out of our logs.
How long we keep it
- Connections, account details and content: while the brand uses the service.
- When a brand leaves or asks for deletion: we stop posting, hand back any account roles we hold, revoke our access where the network allows it, and delete the brand's stored access, sign-in details, account identifiers and content files.
- Our record of what we posted may be kept after the brand leaves, unless the brand asks us to delete it.
Withdrawing and deleting
A brand can withdraw our access at any time in each network's settings for connected apps, or ask us to delete everything. The steps are on the data deletion page.
This website
multimedia.monster sets no cookies, runs no scripts and has no analytics or trackers. The service that hosts it may keep standard technical logs of requests, such as IP address, time and page.
Other points
The service is for businesses and is not directed at children. If this policy changes, the new version is published here with a new effective date.
Contact
Multimedia Monster
privacy@multimedia.monster