Your data, handled.

Who we are

Slop Agency is the in-house AI studio of Kempu. The website slop.ee, Slop Cloud (cloud.slop.ee) with its apps (Client Hub, CVI, Moodboards, Social Media, Social Poster and SEO Audits) and the Social Poster apps for iPhone and Android are run by Kempu OÜ, a company registered in Estonia. Kempu OÜ is responsible for the personal data described on this page.

Questions, requests and complaints: info@kempu.com. Using Slop Cloud and its apps is also covered by our Terms of service.

The website, slop.ee

Visiting. Like every website, our server receives your IP address and browser details with each page you open, and our hosting provider keeps them in its access logs to run and protect the site.

Cookies and analytics. Nothing is measured until you say yes on the cookie ticket. If you do, Google Analytics sets its cookies and sends Google the pages you view and basic details about your device and browser, so we can see which pages people read. Advertising storage, ad personalisation and ad user data stay switched off. Your answer is kept in your own browser (local storage), not on our server. You can change it at any time under Cookie settings in the footer; saying no removes the Google Analytics cookies.

Start a brief. When you send a brief, we store your name, email address and your answers in the site, and email them to our team so we can reply. To stop floods of automated submissions, we count submissions for one hour against a keyed hash of your IP address; the address itself is not stored.

Comments are closed on this site, and we do not run advertising.

Slop Cloud

Slop Cloud is by invitation, for Kempu teams and the people and organisations we work with.

• Your account: name, email address, the avatar you picked, your password (stored only as a hash) and your two-factor authentication secret and recovery codes (stored encrypted).
• Workspaces: the organisations you belong to, your role in each, invitations, the apps, licences and seats you have, and the organisation’s logo if one is set. The logo is redrawn as a small square image and shown only to the organisation’s members.
• Billing: the billing details an organisation enters (name, billing email, address, registry code and VAT number) and the invoices we issue.
• Security: your signed-in sessions (with IP address and browser), the phone apps you are signed in to, and a record of administrative, billing and security changes (who made them, when, and from which IP address).
• Connected services: the social media accounts, Google Search Console, websites and webhooks a workspace connects on the Integrations page. What we receive from each is described under Connected accounts and services.
• AI agents: the agents you connect, the workspaces you let each work in and what you allowed it to do in each, described under AI agents.

We email you about your account and your organisation: invitations, password resets, invoices and payment receipts; if you monitor a scheduled SEO audit, when it finds the site got worse; and in Social Media, when a post waits for your approval, when yours was approved or declined, and when a post you wrote or scheduled did not go out everywhere. You can turn the Social Media emails off in its settings. We do not send marketing email from Slop Cloud.

What you keep in an app is shared with everyone who uses that app in the same workspace (Social Media narrows this for drafts, see below), and belongs to that workspace’s organisation (or to you, in your personal workspace). People an owner allows can move clients, projects, brand books, boards, audits, drafts and posts to another workspace they belong to; they then belong to that workspace’s organisation, and the change record keeps who moved what, and when.

Client Hub

Client Hub keeps what a workspace knows about its own organisation (“Our brand”), its clients and its projects: guidance (background, audiences, search keywords, tone of voice, wording, rules, colours, typefaces, prompts, notes and decisions), organised in topics, files, a picture for each client and project, contacts, and which projects each person starred or opened last.

• Contacts are the people at a client your team works with: name, role, email address, phone number and notes. They are never part of the AI brief and never sent to an AI service by Slop Cloud’s own features. An AI agent you allow to read Client Hub can read them, and they then go to that agent’s provider (see AI agents).
• The AI brief is compiled from the guidance, the titles and descriptions of files and, with Moodboards and CVI, the names of the client’s boards and brand book. People in the workspace and the agents they allow can read it; SEO Audits sends it to an AI service when it reviews a client’s pages, and Social Poster and Social Media when you write or plan posts for a client (see AI features).
• Files and pictures are stored privately with the workspace. A client’s or project’s picture is redrawn as a small square image; the file sent is not kept. Our brand uses the organisation’s logo as its picture.
• Live sources. A live source (a feed, sitemap, calendar or published sheet) is an address that our server opens when someone, or an agent they allow, reads it. What it returns is shown and not kept.

CVI

CVI keeps a workspace’s brand books: each brand’s visual identity in chapters of text, logos, colours, typefaces with their font files, text styles, pictures, rules and downloads. A brand book can be for a Client Hub client or project; only which one is kept, not a copy of it.

• Files are stored privately with the workspace, and only kept for what their contents are: a picture is redrawn as previews, a font must be a font. Font files are sent to the browsers of people in the workspace so the brand book shows in its own fonts.
• Pictures by address. When an agent adds a picture by its address, our server opens that address once and keeps the copy.
• CVI has no AI features. AI agents you allow can read a brand book and download its files (see AI agents).

Moodboards

Moodboards keeps a workspace’s boards and everything on them: pictures, videos, sound, typefaces, files, links, colours, code, notes, text and drawings, with the notes written about each.

• Files are stored privately with the workspace. Pictures and video stills are shown from previews drawn from them.
• Links and pictures by address. When a link, or a picture from another page, is added, our server opens that address to read its title, description and image, and keeps the card’s picture.
• YouTube and Vimeo. A video link shows as a card. Only when you press play does the board load the video from YouTube (youtube-nocookie.com) or Vimeo, whose privacy policies then apply.
• Code on a board is drawn in a sandbox that loads nothing from other sites.

Social Media

Social Media plans and schedules what a workspace posts: its queues (their names, descriptions, weekly times, time zones and accounts, and who may suggest, post or review in each), posts and threads with their photos and videos, when each goes out, approvals with the notes left on them, the history of each post, and how each post did.

• Who sees drafts. A draft is seen by the person who wrote it and the app’s managers; posts that were sent for approval or scheduled are also seen by the people who review or post in that queue.
• Publishing on schedule. A scheduled or approved post goes out at its time without anyone pressing a button, in the name of the person who scheduled or approved it, to the services of its queue, where their own privacy policies apply.
• How posts did. For each account a post went out to, our server asks the service how the post is doing about 2 hours, 1, 3, 7 and 30 days after it went out, and keeps the counts it reports: views, reach, likes, comments, shares, quotes, saves and clicks, as far as the service reports them. We read counts only, never the comments themselves or who liked or shared. See Connected accounts and services for the access this needs.
• AI tools (writing, image descriptions, planning and the analytics review) are described under AI features.
• Social Poster and its phone apps can send a post to a queue; it is then kept here.

Social Poster

Social Poster, on the web and in the iPhone and Android apps, keeps what you write and upload in your workspace: posts and threads, drafts, photos and videos with their alt text, link previews, and the archive of what was posted where, with links to the published posts. Everyone who uses Social Poster in the same workspace can see its drafts and archive.

• Publishing. When you post, the text and media go to the services you picked, where their own privacy policies apply. Some services collect media from a temporary signed link to our server, which stops working after an hour; the copy behind it is then deleted.
• Link previews. When you add a link, our server opens that page to read its title, description and image.
• GIF search. When you search for a GIF, our server sends your search words to GIPHY. The previews then load straight from GIPHY, which sees your IP address and browser like any site you visit. The GIF you choose is copied into the workspace like an upload.
• AI tools (writing modes and image descriptions) are described under AI features.
• The phone apps keep your sign-in in the device’s secure storage (the iOS Keychain, or encrypted storage on Android). A sign-in lasts at most 90 days, and signing out, or signing the app out from Account and security in Slop Cloud, ends it. The apps only see the photos and videos you pick. On Android, a notification shows while a post is being published. The apps contain no advertising, analytics or crash-reporting tools and do not track you across other apps.

SEO Audits

SEO Audits keeps a workspace’s audits: the addresses to check, the documents uploaded to it, and the results of each run.

• Checking websites. Our server opens the pages of the site being audited, as “SlopCloudSEO”, and follows the site’s robots.txt. From each page it keeps facts such as its status, title, description, headings, links and word count, not the page itself. An uploaded document is kept, one copy per version, until its audit is deleted.
• Google’s data. With a Google Search Console connection, an audit reads the site’s clicks, impressions, positions, searches and indexing from Google and keeps them with the run. To measure speed, it sends the addresses of the most important pages to Google PageSpeed Insights.
• AI reviews the most important pages and writes an action plan as part of an audit, when the workspace’s plan includes AI: see AI features.
• Alerts. The person who monitors a scheduled audit gets an email when it finds the site got worse.

AI features

The AI features in Slop Cloud run on AI services the platform has set up: Anthropic (Claude), OpenAI, Google (Gemini) or OpenRouter, which passes a request on to the provider of the model chosen for that feature. The service processes what it is sent to return the result.

• Social Poster, when you press them: the writing modes send the text of your post, with its links, @mentions and #hashtags left out, your own writing guidance and, when the post is for a Client Hub client, its AI brief; image descriptions send the picture. If you turn on describing pictures as you attach them, each picture is sent when you attach it.
• SEO Audits, as part of every audit, scheduled ones included, when the workspace’s plan includes AI: the text, title, headings and top searches of the most important pages, for the content review; the run’s findings and figures, for the action plan; and, for an audit of a Client Hub client, the client’s audiences, search keywords, offering, messages, competitors and project briefs, to work out what those audiences search for, and the client’s AI brief, to review the pages in its voice. “Explain” and title and description suggestions send the same kind of content when you press them.
• Social Media, when you press them: writing and image descriptions send what Social Poster’s do; planning sends what you ask for, the queue’s description, accounts, their limits and weekly times, the text of the posts already planned for the period and, for a client, its AI brief; the analytics review sends the period’s figures and the text of each post with its figures.
• Client Hub, CVI and Moodboards have no AI features of their own.

We keep how many times each person used an AI feature each month. We do not keep what was sent. We keep what came back only where it becomes part of your work: the text you keep in a post, an audit’s content review, action plan and suggestions (with the run), and the analytics review (for you, with the view it was made for).

AI agents

You can connect an AI agent, such as Claude, ChatGPT, Codex, Cursor or Gemini CLI, on the Agents page of a workspace. It signs in as you, works only in the workspaces you choose, and can read and do in each only what you allowed there, never more than you can yourself. Before it writes or designs anything it looks up the directions your workspaces keep (Client Hub briefs, brand books and boards) that it is allowed to read. Owners and admins of an organisation can limit agents or switch them off for it.

• What we keep: the agent’s name and the addresses it registered to sign in with, what you allowed it, when it was last used and from which IP address, and its sign-in keys, stored only as hashes. An access key lasts an hour; the key that renews it lapses after 90 days unused.
• Install links for an agent’s plugin: a secret address per person, agent and workspace, stored encrypted so it can be shown to you again. It delivers the plugin only, never workspace data.
• What an agent reads goes to its provider. Whatever an agent reads in Slop Cloud (a brief, a client’s contacts, a brand book and its files, a board and its pictures, drafts and posts with how they did, an audit) is sent to that agent’s AI provider, under your own agreement with that provider. Give an agent only what you are happy for its provider to process.
• Files an agent sends in or downloads go through a one-time address that works once, for 30 minutes.
• We do not keep a record of what an agent reads. What it changes is saved like a change made on the web. Disconnect an agent on the Agents page to end its access at once.

Connected accounts and services

A workspace owner or admin can connect social media accounts and other services on the Integrations page of Slop Cloud, so the apps can use them: Social Poster and Social Media publish to them, Social Media reads how the posts it published are doing, and SEO Audits reads Google Search Console. For most services you sign in at the service itself and approve the access we ask for; we never see your password there. We ask only for the access the apps need. From each service we receive and keep:

• Facebook: your name and Facebook user ID, and the list of Facebook Pages you manage and may create content on, so you can pick which Page to post to. We publish the posts, photos, videos and links you send to those Pages. For Social Media, we read the number of reactions, comments and shares of the posts it published and, where reading insights is switched on, their views, reach and clicks. Permissions: public_profile, pages_show_list, pages_read_engagement, pages_manage_posts, and read_insights where insights are switched on.
• Instagram (professional accounts): the account ID, username and name. We publish the photos, videos and carousels you send, and read back the link to each published post. For Social Media, we read the number of likes and comments of the posts it published and, where reading insights is switched on, their views, reach, saves and shares. Permissions: instagram_business_basic, instagram_business_content_publish, and instagram_business_manage_insights where insights are switched on.
• Threads: the account ID, username and name. We publish your posts and threads, with their photos and videos. Where reading insights is switched on, we read how many views, likes, replies, reposts, quotes and shares the posts Social Media published have. Permissions: threads_basic, threads_content_publish, and threads_manage_insights where insights are switched on.
• X: the account ID, name and username. We upload your media and publish your posts and threads, and, for Social Media, read the public counts of the posts it published (views, likes, replies, reposts, quotes and bookmarks). Permissions: tweet.read, tweet.write, users.read, media.write, and offline.access so the connection keeps working without signing in again.
• LinkedIn: your name and LinkedIn member ID from the sign-in. We publish your posts, photos, videos and link cards on your profile. Permissions: openid, profile, w_member_social. Where posting to company Pages is offered, also r_organization_admin and w_organization_social, to list the Pages you administer and publish to them. Where reading how posts do is switched on, also r_member_postAnalytics for posts on your profile and rw_organization_admin for posts on Pages, and we read those posts’ figures for Social Media.
• TikTok: your TikTok open ID and display name. Each time you prepare a post, we read your current posting settings (your nickname and username, which audiences you can post to, whether you have turned comments, Duet or Stitch off, and the longest video you may post) to show you the choices TikTok requires; they are not stored. We upload and publish the videos and photo posts you send, with the audience, interaction and commercial-content settings you choose for each. Where reading how posts do is switched on, we read the views, likes, comments and shares of the videos Social Media published. Permissions: user.info.basic, video.upload, video.publish, and video.list where that is switched on.
• Bluesky: your handle, account identifier (DID) and the address of your account’s server, through a sign-in at that server. We publish your posts and threads, with their images, videos and link cards. For Social Media, we read the public counts of likes, replies, reposts and quotes of the posts it published.
• Mastodon: your server’s address and your account name. You sign in at your own server, where Slop Cloud registers itself as an app, and approve read:accounts, read:statuses, write:statuses and write:media. We publish your posts and threads with their media and, for Social Media, read the counts of favourites, replies, boosts and quotes of the posts it published.
• WordPress: the site address, your user name and an application password you create in WordPress.
• Webhooks: the address you enter, and a token for it if you add one. Each post is sent there, with its images and a link to its videos that works for an hour.
• Google Search Console (for SEO Audits): your Google account ID and email address. We only read: the search performance and indexing of the sites being audited. Permissions: openid, email, webmasters.readonly.

The only figures we read from the social media services are those of posts published through Social Media, as described above. We do not read your feed, messages, followers or contacts, or what comments say. Nothing is posted unless someone in your workspace publishes, schedules or approves it, or an agent they allowed to do so does it for them. The keys a service issues are stored encrypted, are used only for the workspace that connected them, and are renewed automatically while the connection is in place. Each connection shows who connected it.

Disconnecting and deleting your data

• Disconnect a service in Slop Cloud under Integrations: open the connection and press Disconnect. Its keys and account details are deleted at once; the change record keeps only that it was disconnected, by whom and when.
• Remove our access at the service instead, in its settings for connected apps (for example Facebook’s Business integrations or X’s Connected apps). The keys we hold then stop working, and the connection is shown as needing attention until it is reconnected or disconnected.
• Delete a draft or a post in Social Poster or Social Media to remove our copy of it, its media and, in Social Media, its history and figures. A post that was already published stays on the service until you delete it there.
• Delete a client, a brand book, a board or an audit in its app to remove it with everything in it: a client with its projects, guidance, files and contacts, once it is marked as a former client; a brand book with its files, once it is archived; a board with everything on it, once it is archived; an audit with its runs and documents.
• Disconnect an agent on the Agents page of the workspace to end its access at once.
• Have everything deleted, including the connections, agents and everything kept in the apps of a workspace, by writing to info@kempu.com from the email address on your Slop Cloud account. We confirm when it is done, within a month.

Why we use it

• To provide the service you use (your account, workspaces, apps, publishing, audits and the agents you connect): necessary for our agreement with you or your organisation.
• To keep things secure and running (logs, sessions, the change record, limits on repeated attempts) and to answer your brief: our legitimate interest.
• Analytics on slop.ee: only with your consent, which you can withdraw at any time.
• Invoices: required by accounting law.
• Data a workspace keeps about other people, such as the client contacts in Client Hub or the people in pictures on a board: we store and process it for the workspace’s organisation and on its instructions. The organisation decides what it keeps and is responsible for having a reason to keep it.

We do not sell personal data, use it for advertising, or use it to train AI models.

Who else handles it

• Netiserver, an Estonian hosting provider, hosts slop.ee and Slop Cloud, their databases and the email they send.
• Google: Google Analytics, only if you allow analytics on slop.ee; for SEO Audits, Search Console (only with a workspace’s connection) and PageSpeed Insights (the addresses of the pages measured).
• Anthropic, OpenAI, Google (Gemini) and OpenRouter, for the AI features in Social Poster, Social Media and SEO Audits: the service set up for a feature receives what that feature sends.
• GIPHY, for GIF search in Social Poster.
• YouTube and Vimeo, when you play a video on a moodboard.
• The services you connect and post to, for what you send them, and when we ask how the posts published through Social Media are doing.
• The providers of the AI agents you connect, for what your agents read, under your own agreement with them.
• Apple and Google deliver the phone apps through the App Store, TestFlight and Google Play, under their own terms.

Google, the AI services, GIPHY, YouTube and Vimeo may process data outside the European Economic Area. Where they do, the transfer relies on the safeguards they provide, such as the European Commission’s standard contractual clauses.

How long we keep it

• Your account and workspace content (guidance, contacts, files, brand books, boards, drafts, posts and audits): for as long as the account or organisation exists, or until you delete it.
• Uploads that no draft or post uses: deleted after a day. Temporary copies for publishing: an hour.
• Keys and account details of a connected service: until it is disconnected, or its workspace is deleted.
• Drafts, the archive of published posts, and Social Media’s posts with their history and figures: until you delete them, or the workspace is deleted. Figures are read for 30 days after a post goes out, then no more.
• Audit results and uploaded documents: until the audit is deleted. A Social Media analytics review: until you make a new one for the same view, or your account is deleted.
• Things removed from a board: 14 days, so they can be restored.
• Agent sign-in keys: an hour for access keys, and 90 days unused for the key that renews them. One-time upload and download addresses: 30 minutes.
• Phone app sign-ins: at most 90 days.
• Briefs: until we have dealt with them, or until you ask us to delete yours.
• Invoices: for the period accounting law requires (seven years in Estonia).

Your rights

You can ask for a copy of your personal data, have it corrected or deleted, restrict or object to how we use it, take it with you, and withdraw consent you gave. Write to info@kempu.com and we will answer within a month. To delete your Slop Cloud account, email us from the address on the account.

If you think we got something wrong, tell us first so we can fix it. You can also complain to the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon, www.aki.ee) or to the data protection authority where you live.

Children

Slop Cloud, its apps and the Social Poster phone apps are tools for work and are not meant for children.

Changes

When what we do with data changes, we update this page and the date at the top.