Privacy Policy

1. Who is responsible

Dorsia operates BeatPublish and is the controller for personal data processed to run the service. For privacy questions, access requests or deletion requests, contact:

2. Information we process

• Account and profile: your email address, authentication information, user identifier, chosen name, profile image and timezone.
• Media and workspace: uploaded audio, video and artwork; file names, sizes and types; generated videos; captions, drafts, presets, calendar entries and publishing settings.
• Connected accounts: platform account or channel identifiers, display names, usernames and profile images, together with access tokens, refresh tokens where provided, and token-expiry information. Tokens are stored encrypted. We do not ask you to give BeatPublish your social-platform password.
• Publishing activity: your selected destination and settings, processing status, platform post identifiers, timestamps and error information. TikTok may provide the account’s available visibility choices, interaction restrictions and video-duration limit.
• Technical and support information: information needed to serve and secure requests, such as IP addresses, browser/request details and operational logs, plus the information you send when contacting us.

Media can contain personal information about you or other people. Only upload material you are authorised to use.

3. Why we use it

We use account, connection and media information to provide the service you request: sign-in, workspace storage, conversion, account selection, publication and status updates. Where GDPR applies, this processing is based on performing our contract with you.

Security, abuse prevention, service troubleshooting and handling enquiries may be based on our legitimate interests in running a secure and reliable service, balanced against your rights. Records required by law are processed to comply with legal obligations. If we request consent for an optional use, you can withdraw it without affecting processing already lawfully performed.

Social-platform authorisation controls which platform features we can access. You may refuse or revoke it; the corresponding integration will then be unavailable. BeatPublish’s publishing flow does not require access to your direct messages or contact list.

4. Platforms and service providers

When you ask us to publish, we send the selected media, caption and publishing options to the destination platform. Published material may become visible to others according to your settings and the platform’s rules. Platforms process that information under their own policies.

Our infrastructure uses Supabase for authentication and database storage, Cloudflare R2 for media storage, Vercel for the website and server endpoints, and Railway for background processing. Stripe processes billing details, customer and subscription identifiers, and payment status. Card details are handled by Stripe; BeatPublish does not store full card numbers. See the Stripe Privacy Policy. These providers process information necessary for their roles. Information may also need to be disclosed to comply with a lawful requirement or protect users and service security.

Platform policies: TikTok Privacy Policy, Meta/Instagram Privacy Policy and Google Privacy Policy. BeatPublish uses YouTube API Services for its YouTube integration.

Infrastructure and platform providers may process information outside your country, including outside the EEA. Where GDPR requires safeguards for a transfer, these must be provided through an applicable adequacy decision or appropriate safeguards, such as standard contractual clauses. Contact us for information about safeguards relevant to your data.

YouTube API Services and your choices

BeatPublish uses YouTube API Services to identify channels you authorise and upload videos you choose to publish. We access channel identifiers, names and profile images, and store encrypted authorisation credentials for your requested uploads. Publishing records may include YouTube video identifiers, upload status and error details.

We send your selected video, title, description, tags and publishing settings to YouTube. See the Google Privacy Policy and YouTube Terms of Service.

Choose Disconnect in BeatPublish to stop queued uploads, remove the channel’s stored YouTube data and request revocation of Google access. Original media, your written draft content and videos already on YouTube are kept. Other channels sharing the same Google authorisation may need reconnecting. You can also revoke access directly in Google security settings — connected apps and permissions.

To request deletion of stored YouTube-related data, email prodjody@gmail.com from your account email and identify the channel and data to remove. Do not send passwords or tokens. Dorsia handles emailed requests manually and removes requested YouTube API data within seven calendar days. You can use Disconnect for channel-data deletion without emailing us. Deletion from BeatPublish does not delete videos or other data held by YouTube; manage those directly on YouTube.

5. Cookies, local storage and website analytics

BeatPublish uses cookies for authentication and connection security. Browser storage is also used for workspace preferences and interface state. Disabling this storage may prevent sign-in or other requested features from working.

We use Vercel Web Analytics to understand website traffic through aggregated statistics, including page views, referring websites, approximate location, and browser and device information. Vercel Web Analytics does not use analytics cookies. We do not send account email addresses, uploaded media or payment details as custom analytics events. This application does not include advertising pixels. See Vercel Web Analytics privacy information.

6. Retention and security

For YouTube, a daily maintenance job checks authorisation and refreshes connected-channel information. Confirmed revocation triggers removal of the associated stored API data. Returned video identifiers, visibility responses and publishing error details are removed on the daily run after 27 days. Minimal service-usage records without YouTube identifiers may remain for subscription accounting.

If Google revocation is temporarily unavailable, the connection is disabled immediately and an encrypted credential is retained only for retries. It is removed on the first daily cleanup after six days, with persistent failures flagged for follow-up. You can also revoke access through Google security settings.

Account information is retained while needed to maintain your account. Media, drafts and publishing history are stored to support your workspace and requested operations; completing a post does not automatically delete the source upload. They are not intended to be retained indefinitely without a service need.

When you request deletion, we assess and remove information no longer needed, subject to identity verification, legal obligations and legitimate requirements such as resolving disputes or preventing abuse. Backup copies and provider logs may remain until their applicable retention cycles expire and are not used for ordinary product operations. Contact us for details about a particular record.

We use authenticated access, user-scoped database permissions, encrypted connection credentials and time-limited media links. No service can guarantee absolute security. Treat downloaded files and any media links you share with care.

7. Disconnecting accounts and deleting data

Use the connected-accounts controls in BeatPublish to disconnect a platform. YouTube disconnection removes stored channel references, upload sessions and associated API data as described above; completed publication counts without YouTube identifiers may remain. Other platform integrations clear their stored credentials and retain a disconnected-account record. Disconnection does not delete original media or posts on the platform. An upload already being transmitted may still complete before cancellation takes effect.

You may also revoke access in the platform’s app-permission settings. For Google/YouTube, visit Google account permissions.

To request deletion of your BeatPublish account, uploaded media or platform-related data, email prodjody@gmail.com from your account email and specify what you want deleted. Do not send passwords or access tokens. We may ask for reasonable identity verification. To delete a published post, use the destination platform’s controls.

8. Your rights

Depending on applicable law, you may request access, correction, deletion, restriction or a portable copy of your personal data, and object to processing based on legitimate interests. Where processing relies on consent, you may withdraw it. Some rights are subject to legal conditions.

Contact us using the email above. For GDPR requests, we normally respond within one month; if a lawful extension is necessary, we will explain it. You may complain to your local supervisory authority or the Danish Data Protection Agency, Datatilsynet.

BeatPublish does not use automated decision-making to make decisions with legal or similarly significant effects on you.

9. Children and updates

BeatPublish is not directed at children. Users must meet the age and authorisation requirements described in our terms and those of connected platforms. Contact us if you believe a child has provided personal data inappropriately.

We will update this page when our practices change and provide appropriate notice of material changes. The date above identifies the current version.