Privacy Policy

Who we are

EmberShape is operated by Bodrogi Bence Barnabás E.V. (Sole Proprietor), tax number (adószám) 90500619-1-33, registered in Hungary. For any question about this policy, or to exercise any of the rights described below, contact us at support@embershape.com. We aim to respond to every request within 30 days.

What we collect

Account and sign-in. When you sign in with a platform (Discord, Google, Twitch, Kick, or Instagram), we receive your platform user ID, username (for Google, your email address), and avatar URL from that platform, and store them to identify your account. We do not receive or store your password for any platform: sign-in happens entirely through that platform's own OAuth flow, and we never see your credentials. If you instead create an EmberShape ID, we store your email address and a salted hash of your password, never the password itself. When you sign up for an account, we also record that you accepted the Terms and this Privacy Policy and confirmed that you are at least 16, with the date and the version of the text you accepted.

Discord server data. When you authorize EmberBot for a Discord server, we store that server's ID and name, and which tool configuration is active there, so EmberBot knows where and how to operate. We don't read the contents of a server's messages beyond what EmberBot's specific moderation or engagement features require to function.

People in servers where EmberBot runs. EmberBot also stores records about members of a Discord server, keyed by their Discord user ID, even if they have never used EmberShape themselves. Which of these exist depends on the features a server's administrators switch on:

• Strike counts for word-filter and spam infractions, used to escalate from a mute to a kick or a ban. A strike stops counting after the server's decay period (30 days unless its administrators change it), and the record itself is deleted automatically 12 months after the member's last infraction.
• A log of EmberBot's own automatic moderation actions (mutes, kicks, bans) with the reason, kept for one year by default, or for the period the administrators choose (between 1 day and 10 years).
• Daily check-in streaks for the opt-in check-in feature. They are deleted automatically after 3 months without a check-in, a member can delete their own check-in data in a server with the slash command /mydata delete, and we delete them on request.
• In servers where the honeypot is switched on (a feature of the Standard plan and above), the IDs, channels and authors of recent messages (never their text), kept for 24 hours so EmberBot can remove a trapped account's recent messages if the honeypot fires.
• If administrators of a paid server turn on message logs: the text of messages, the sender's username at the time, and attachment file names, kept for 7 days so a deleted or edited message can be shown in the server's log channel, and deleted sooner if the administrators switch message logs off or ignore a channel. Once posted there, an entry is an ordinary Discord message controlled by that server's staff.
• A list of members an administrator has exempted from spam detection.

A server's administrators choose which of these features run and can see some of the results. To ask us to delete what EmberBot holds about you, contact us at support@embershape.com. Everything described here also exists in our database backups until they are deleted after 14 days.

Images on weekly schedule posts. On Premium servers, administrators can attach one image (PNG, JPEG, GIF or WebP, up to 8 MB) to a weekly schedule post. The image is chosen by the administrator and stored encrypted in our database. We delete it right after the post goes out, or when the administrator removes the image or the entry, and in any case an automatic daily cleanup deletes it after 60 days. A server can hold at most 10 stored images. Our database backups, which are deleted after 14 days, can contain the encrypted copy. EmberBot sends the image to Discord as an attachment on the post, and from then on Discord's own terms apply to it. The preview in the dashboard is only shown to signed-in administrators of that server.

Instagram post announcements. If a server's administrators set up Instagram announcements, EmberBot reads the media information (post ID, caption, type, link, timestamp and thumbnail link) of the Instagram account that the server's EmberShape account connected and chose to share with EmberBot. It does this with a read-only access token that it fetches from our connection service each time and keeps only in memory; EmberBot never stores it or writes it to a log. For each server, EmberBot stores the Instagram username and user ID, the Discord channel, role and message settings, and a short fixed error note if the connection breaks. For each announced post it stores only an identifier, a status and a time, which a daily cleanup deletes after 60 days; those rows are also in our database backups for up to 14 days. It does not store captions, images, videos or thumbnails. The announcement posted in Discord (the account's username, the first line of the caption up to 100 characters, a link to the post and a link to its thumbnail) is visible to everyone in the channel the administrators chose. Only posts published after an administrator turns an announcement on are announced, and never posts older than 14 days.

Posting and data-access connections. Separately from signing in, you can grant EmberShape's tools permission to post content or read data on your behalf on TikTok, Instagram, YouTube, or Twitch. Doing so stores an encrypted access token (and, where the platform issues one, a refresh token) for that connection, along with the scopes you granted and the connected account's platform username. These tokens are used only to perform the actions you've enabled, for example publishing a video you've created through EmberShape's tools, and are encrypted at rest. Exactly what we can see or do through a connection depends on the specific permissions you grant when you connect it, and on that platform's own policies.

YouTube API Services. EmberShape's use of YouTube data, when you connect a YouTube channel, is governed by the YouTube API Services Terms of Service and by Google's Privacy Policy. We access only what's needed for the features you use: basic channel and video information to display and manage your own content, and, if you grant it, the ability to publish a video you've chosen to post.

Billing. Subscription payments are processed by Stripe. We store your Stripe customer ID, subscription ID, and subscription status. We never receive or store your card number, expiration date, or CVC; Stripe handles those directly.

Usage. We keep basic timestamps of account activity (when a server was linked, when a platform was connected, when a subscription started) so you can see your own account's activity history from your dashboard.

Support communications. If you email us, we keep that correspondence (and any information you choose to include in it) so we can respond to you and keep a record of the conversation.

Server logs. Our web server keeps a log of requests to embershape.com and emberbot.embershape.com: the time, your IP address, the page requested, the response status, and browser details such as your user-agent. We use it to keep the services secure and to investigate abuse, and we delete entries after 30 days. The log does not contain your cookies, passwords, or the one-time codes in sign-in and verification links.

Cookies

We use a small number of first-party cookies, all needed for the site to work. One keeps you signed in, for up to 30 days or until you sign out. The others are short-lived, lasting no more than 10 minutes, and exist only while you sign in or add EmberBot to a Discord server: one protects the sign-in process itself from forgery, one holds a temporary code that Kick requires for its sign-in, one remembers where to send you back to after a sign-in you started elsewhere, and one remembers which Discord bot you're adding to a server. None of them are used for advertising, and we don't run any third-party analytics or tracking scripts on EmberShape.

How we use it

To operate your account and the tools you've enabled, to run EmberBot in the Discord servers you've authorized it for, to perform posting or data-access actions you've explicitly granted, to process billing, and to communicate with you about your account. We do not sell your data, and we do not use it for advertising.

Who we share it with

Stripe, for payment processing. The platform each connection is with (Discord, Google, Twitch, Kick, TikTok, Instagram, YouTube), necessarily, to perform the sign-in or action you've requested. Our email provider, to send you account messages such as email verification, password resets, and account-deletion notices. Infrastructure providers that host EmberShape's services, bound by their own confidentiality and security obligations. We don't share your data with anyone else, and we've never sold it to anyone.

International data transfers

EmberShape is based in Hungary, within the EU. Some of the infrastructure and platform providers we rely on (including Discord, Google, Twitch, Kick, TikTok, Instagram, YouTube, and Stripe) are based outside the EU, most commonly in the United States. Where we transfer personal data outside the EU, we rely on the transfer mechanism that provider itself offers (such as the EU-U.S. Data Privacy Framework or Standard Contractual Clauses) to keep it protected to a comparable standard.

Security

Posting and data-access tokens are encrypted at rest. All traffic to EmberShape is encrypted in transit over HTTPS. We limit access to your data to what each part of our system actually needs to function. No system is perfectly secure, but we treat your platform tokens as the sensitive credentials they are.

Your rights and controls

You can disconnect any signed-in platform or posting connection from your Connections page at any time. Disconnecting a posting connection revokes its access token where the platform supports remote revocation. You can also revoke EmberShape's access directly from the connected platform's own settings (for example, Discord's Authorized Apps, or Google's Security page); either side works.

You can delete your account yourself from Settings at any time. On a free account, it's deleted 7 days after you confirm. On a paid plan, your subscription is canceled straight away so it won't renew, and the account is deleted when the billing period you've already paid for ends (or 24 hours after you confirm, if that is later). You can cancel a scheduled deletion any time before it happens.

Depending on where you live, you may have the right to access, correct, export, or delete the personal data we hold about you, to object to or restrict certain processing, and to withdraw consent at any time where processing is based on it. To exercise any of these, email support@embershape.com. If you're in the EU or UK and believe we haven't resolved your request adequately, you also have the right to lodge a complaint with your local data protection authority.

Children's privacy

EmberShape isn't directed at children. You must be at least 16 years old to create or use an EmberShape account, and you must also meet the minimum age of any platform you sign in with or connect (for example, Discord requires users to be at least 13). We don't knowingly create accounts for anyone under 16. If you believe someone under 16 has created an account, contact us at support@embershape.com and we'll delete it.

Retention

We retain account data for as long as your account exists. Posting and data-access tokens are retained only while that connection remains active, and are deleted on disconnect. When you disconnect a sign-in method, we delete its stored profile details too. When your account is deleted, we permanently delete your sign-in profiles (including any email address and password hash), your account and connection records, and the data other EmberShape services hold for your account. Discord servers you linked stay registered with EmberBot but are unlinked from your account, and the dashboard access you gave other people for those servers, or that others gave you for their servers, is removed. Some things are not removed with your account: billing records, which we and our payment provider are legally required to keep; database backups, which are overwritten within 14 days; EmberBot's records about members of Discord servers, which are tied to a Discord user ID rather than to an EmberShape account and expire on the schedules described above; dashboard access you granted to others on servers owned by someone else, which stays and records you as the person who granted it; and emails you have sent us, which we keep for as long as we need them to deal with your request.

Changes to this policy

If we make a material change to this policy, we'll update the date above and, where required, notify you directly.