Skip to content
Post Your BrandPrepared social workflows
WorkflowsPilot termsLog in / Create account

Privacy information

Updated 16 November 2026. This notice covers the public website and customer workspace. The separate commercial-instruction controls described below were deployed on 16 November 2026. Proposed customer agreements still require separate acceptance.

Beat und Wagner GmbH
Chamissostraße 23
50825 Köln, Germany

Managing directors: Jan Philipp Joseph Bednorz and Paulina Marianne Wagner-Bednorz.
Register: Amtsgericht Köln (Cologne Local Court), HRB 125883.

info@postyourbrand.com

Website, origin hosting, DNS and earlier edge processing

Our origin server is hosted by Hetzner Online GmbH in Germany. Our existing hosting DPA with that company was concluded on 10 October 2026. Cloudflare provides authoritative DNS. The main postyourbrand.com domain and www were already DNS-only; review.postyourbrand.com and capture.postyourbrand.com were changed to DNS-only on 16 November 2026 at 14:56:20 UTC. At 15:00:53 UTC, Cloudflare and Google public DNS-over-HTTPS returned their CNAME chain to our German origin, 178.104.25.34, with no IPv6 address. Normal HTTPS checks from the server at 15:02:24 UTC reached that origin without a Cloudflare request header. These observations verify the configured direct route; they do not establish that every resolver or existing connection switched immediately. Some local DNS caches still returned the earlier Cloudflare addresses during propagation. Cloudflare previously terminated HTTPS and processed review/capture requests and responses, including workspace/API traffic and tool results. We have not established an exhaustive historical country list or deletion of all prior Cloudflare logs or other retained data. A German origin is not a claim that all historical or other-provider processing occurred only in Germany.

Connection information, including IP addresses and request metadata, is used to deliver and secure the service (Article 6(1)(f) GDPR). Origin access logging is disabled. Cloudflare still processes DNS-related information and may retain information from its earlier proxy processing; the routing change is not proof of deletion. Its applicable service agreement, DPA and service-specific onward-processor information describe its processing and transfer framework. We do not claim an EU-only edge configuration or that every supplier on its global list receives our data.

No advertising trackers, external fonts or social embeds are included in the public website. The interactive example uses browser memory only: its settings are not saved or sent and it makes no social API request.

Account, contract and administration

We process first-party portal email, password hashes, organization details, account settings and correspondence to operate the customer relationship. Article 6(1)(b) applies where necessary for a contract with the individual; necessary business-contact and security processing may rely on Article 6(1)(f). Specific statutory contract-record retention relies on Article 6(1)(c) where the stated duty applies.

Registration, recovery and account-administration email uses our existing Google Workspace service. It receives the relevant administrative email address, message/link and delivery metadata. Fan comments and private Instagram conversation content are not part of that described mail flow. We do not select a customer AI provider through Google Workspace. Actual supplier and transfer details must match the applicable service agreement; administrative mail is distinct from processing customer social content.

Essential host-only session cookies support sign-in and form protection. Sessions last at most eight hours; sign-in preparation lasts ten minutes. Single-use registration and recovery links expire after at most 30 minutes. No advertising or analytics cookies are used.

Connected social-account processing

Instagram authorization is handled by Meta; we do not ask for your Instagram password. Depending on the permissions and functions you enable, we process professional account identity, owned media, comments, available metrics, uploads, schedules, configured replies and execution records. Private inbox data is used only with the applicable scope and authorization. Tokens and prepared action content are encrypted on our server. Meta also processes information under its own terms, privacy information and transfer arrangements.

We act on the customer's documented instructions for social-account operations, as described in the own-service DPA. Separately, we act as controller for our own first-party contract and administration records. That distinction does not allow repurposing social data for marketing, data resale or general-purpose model training. Customer-data isolation and the actual platform permissions remain required.

Your selected AI client

Fixed catalog workflows do not require an AI provider. Optional MCP access is separately authorized for one account, scope, duration and applicable budgets. Your chosen client and inference provider can receive requested tool results, including private conversations only under private-inbox or Operate authorization. We do not forward Instagram passwords or access tokens to the AI client. A locally installed client can still send results to a hosted model.

The named recipient instruction records the selected services/plans, public terms references and operational processing settings. A customer declaration is not provider certification. General customer access requires a separately reviewed compatible arrangement and actual platform/release eligibility. The MCP addendum explains authority, recipient selection and revocation. Your separately contracted provider has its own processing, retention and transfer responsibilities; an MCP revocation does not delete its copies automatically.

Manage access can activate eligible fixed workflows; Operate access additionally permits explicitly authorized autonomous actions, including private replies and permanent comment deletion. Private data access is separately selected. Grants expire within at most 30 days and are revocable; reconnecting the social account or changing the platform password invalidates existing grants. Activated fixed workflows have their own lifetime and must be paused separately. Upload tickets expire after ten minutes. We keep credential hashes rather than the agent bearer secret, account/scope/expiry information and necessary tool/action audit metadata. Prepared action content is retained for up to 30 days, subject to earlier deletion. A stored action state is not proof of delivery.

Operational deletion and current backups

Disconnecting stops account execution and removes local connection tokens and account content through the applicable cleanup path. Remove Meta app access separately where desired. An account-association entry can remain so a disconnected connection is still displayed; first-party customer records remain until their applicable deletion or retention event. Published content is not removed from Instagram by disconnecting.

Current encrypted local operational backups keep seven versions; that is a version limit, not a guarantee of deletion after seven days. Technical release copies may also exist. Full operational customer deletion includes relevant backup/update-copy handling and is not marked complete before its required verification. There is no claimed independent offsite disaster-recovery service or supported restoration that reactivates old tokens or grants. Historical setup diagnostics are separate from ongoing operations; this website update does not itself delete them.

Separate commercial instructions

Deployed on 16 November 2026. The new flow previews an exact, separate business instruction for you to send explicitly. Its restricted encrypted receipt contains your first-party organization name/contact email, named client/provider roles, services/plans and public terms/privacy references, a random instruction reference and the fixed instruction text. It does not archive the operational form's free-text retention, training or other settings, social handles/identifiers, comments, DMs, tokens, callback URLs or connection generations.

Where the received document is classified as commercial correspondence under HGB §257, the company retains that document for six years after the receipt year. A 2026 receipt is ordinarily due for deletion on 1 January 2033. Disconnecting does not restart the clock. This is not a six-year retention rule for Meta account data.

The operator process assesses qualified erasure or correction of incorrectly classified or unlawfully retained receipts and records a minimal erasure audit/tombstone scheduled for expiry after 33 days, only after all known receipt copies have been successfully reconciled. New instruction-creation confirmations are time-bound to 30 minutes. Expiry and erasure are reconciled to the known dedicated local receipt copies, with at most 32 dated daily copies and no keys or operational database in those dedicated copies. This is not a global inventory of external copies, an offsite backup promise or permission to retain expired records for another 32 days. The deployed backup/update path excludes both receipt directories from ordinary operational backup archives and preserves the current ledger across supported source rollback. Daily receipt maintenance completed successfully for the main, review and capture workspaces after deployment. Other relevant operational/release copies still require appropriate handling. No public customer self-service override of a genuine statutory duty is promised.

Rights and contact

Request access, correction, erasure, restriction, portability where applicable, or object to relevant processing at info@postyourbrand.com. We verify necessary ownership without asking for social passwords, tokens or one-time codes. Rights requests are answered within the applicable GDPR period, normally one month. Any limited statutory retention refusal must identify the actual obligation, category and expiry; a generic claim that all records must be kept is insufficient. You can complain to a data-protection authority, including LDI NRW. See the deletion guide.

Instagram advertising

Advertising is a separate optional connection. With your Meta authorization we process your app-scoped Facebook user identity, selected ad account and linked Page/Instagram identity, campaign and creative settings, budgets, performance metrics and action receipts. Meta credentials are encrypted on our server and are not sent to your agent. Read-only Page content is used to verify the advertising identity. Public content and campaign names are untrusted data, not instructions.

You separately authorize each agent for Ads read access, management or spending. Selected agent/model services can receive Ads tool results. Existing recipient instructions and compatibility requirements continue to apply; organic Instagram grants alone do not grant Ads access. Advertising charges are paid directly to Meta, separately from any Post Your Brand fee.

OAuth state expires after ten minutes and is removed within one day after expiry. Unused action previews expire after ten minutes and are removed within one day; operational action/audit records are retained for up to ninety days, except unresolved writes retained for reconciliation. Expired/revoked Ads credentials are disabled and cleared during maintenance; retained object metadata permits safe renewal and lifecycle management. Objects and spending instructions remain while the connection is maintained and are removed on Ads disconnect, a verified matching data-deletion request or completed customer erasure. Minimal signed-request receipts contain no Facebook user ID and expire after ninety days. Existing documented backup-erasure and supplier arrangements apply.

Disconnect removes local access; it does not pause or delete campaigns on Meta. Pause running ads before disconnecting or use Meta Ads Manager. A provider revocation or token expiry stops Post Your Brand access but does not itself stop Meta delivery. Signed Facebook-user requests are matched only to the verified app-scoped USER identity, never inferred from an Instagram or business-integration ID.

TikTok module: current prototype and proposed processing

TikTok module preparation · 17 November 2026. The legal operator is Beat und Wagner GmbH; Post Your Brand is its product and brand. TikTok account connection and production operation are not available. Our existing Instagram service and its separate authorizations do not grant TikTok access.

The review prototype contains synthetic records only, runs in browser memory and makes no TikTok API call. It does not collect TikTok passwords, OAuth codes, tokens, real comments or real account metrics. Ordinary public-site connection information and first-party enquiries follow the existing website/administration sections above.

For a future authorized Accounts connection, the proposed categories are account identity and permission/expiry details; approved original media and editable publishing settings; owned post identifiers/status; available owned account/post metrics; comments on the authorized account’s own posts and approved replies; schedules and execution records. TikTok would handle authorization and platform-side processing under its own applicable terms and privacy information. Our service would process social-account data on the customer’s documented instructions; our own contract/security records remain a separate controller activity.

Proposed operational policy before activation: encrypt connection credentials and restrict them to the authorized account; keep credentials only while required for an active connection and remove local access through verified disconnect/revocation/expiry handling; retain operational post/comment/metric copies on a rolling maximum 30-day schedule and minimal execution records for up to 90 days, with documented handling of unresolved writes. Customer deletion and known backup-copy reconciliation must be verified; a backup-version count is not a deletion deadline. These TikTok controls are design requirements and have not been represented as deployed.

No TikTok data is presently forwarded to a customer AI client through this module. Before any such feature is enabled, the named recipient, exact tool scope, data categories, duration and provider arrangement must be separately reviewed and authorized. Meta token or grant permissions never confer TikTok access. Prior to production, publish and agree the actual TikTok processing/security/retention schedule and verify the implementation. Product and approval scope.

Post Your Brand

A brand operated by Beat und Wagner GmbH.

TikTok moduleGuideLegal noticePrivacyDelete dataPilot termsMCP addendumDPAContact

© 2026 Beat und Wagner GmbH · Post Your Brand