Privacy
Updated: 8 October 2026 · Private testing / limited provider-review phase
Controller and contact
Charline Bramorski, sole trader operating as Moonlio Digital, Akeleiweg 2a, 22607 Hamburg, Germany. Publisher Worksolution (PWS) is a product of Moonlio Digital. Privacy: legal@getpws.com. Help: support@getpws.com. Security reports: security@getpws.com. No data protection officer has been appointed.
Scope
This notice describes the website and the existing private PWS testing with the Owner account. Public registration is disabled; an external beta has not been released. There is no billing, music distribution or royalty handling. Visiting the website does not connect a platform account or publish content. Planned features will be explained separately before activation.
Website without tracking
To provide HTTPS and deliver these static pages, the server processes the IP address, requested resource and necessary connection data. The legal basis is Article 6(1)(f) GDPR: our interest in a secure, accessible information website. The page cannot be transmitted without connection data. Website access logs are disabled in the reviewed configuration. The pages set no cookies and use no analytics, trackers, external fonts or embedded platform content. There are no tracking accesses requiring consent here.
Contact and support
For an enquiry, we process your sender address, message, communication data and voluntarily supplied attachments to handle your request. General enquiries rely on Article 6(1)(f) GDPR (responding directly to the help requested). Article 6(1)(b) applies only to objectively necessary steps under an actual contract with you or before entering into one at your request. Fulfilling statutory privacy rights relies on Article 6(1)(c) in conjunction with Articles 12–22 GDPR. Email links open your email application; this website has no contact form or automatic attachment upload. Do not send passwords, tokens or one-time codes. legal@getpws.com and security@getpws.com are reception aliases of the support mailbox hosted by Hetzner; replies initially come from support@getpws.com. partners@getpws.com is not a privacy contact.
Private account and passkeys
PWS processes account and device identifiers, roles, workspace/project membership, permissions and session state. For the operator’s current use, this serves the secure administration of her business and test system (Article 6(1)(f) GDPR). No contract by the sole trader with herself is claimed as a legal basis. PWS stores public passkey keys, identifiers, verification and security metadata. Private keys and local verification stay with the operating system or authenticator. PWS stores no biometric data and receives no fingerprint or Face ID data. Any iCloud Keychain synchronization you use is separately governed by Apple’s services. Short-lived PWS access tokens are held in memory during the session. The normal Mac client stores the PWS session-renewal key and associated account/device identifiers in the local, non-synchronizing, device-only Keychain; signing out removes that entry. Server-side PWS session values are hashed. This PWS sign-in is separate from the Google/YouTube connection: its credentials are encrypted in the server vault and are not returned to the native client.
Projects, media and local preparation
Projects, branding, imported media, checksums, technical analyses, local transcripts, text, variants, schedules and reminders support the operator’s content preparation. These working data generally remain on your Mac; Apple-native analysis and supported speech recognition run on device without a cloud fallback. Necessary organization of the operator’s business content relies on Article 6(1)(f) GDPR. This does not generally authorize importing or publishing personal content about others; special categories may additionally require a basis under Article 9 GDPR. User-selected exports, local backups and original files are outside server-side erasure. There is no automatic diagnostics upload or PWS push service.
Existing platform connections
Telegram, Bluesky, YouTube, Instagram and TikTok are genuinely connected in private testing. PWS uses only the platform identity, permissions, destinations, connection and expiry data and server-encrypted credentials required for the selected connection. TikTok Creator Info supplies the account name, available visibility options, interaction permissions and technical limits for the local preview. A connection does not authorize delivery; Instagram publishing and TikTok publishing are disabled. Necessary connection management for the operator’s own test accounts serves controlled business testing (Article 6(1)(f) GDPR). OAuth approval is platform authorization, not general GDPR consent. PWS does not collect platform passwords or sell platform data. Facebook Pages, Threads, LinkedIn, Pinterest and music distributors are not active PWS content connections.
Approvals and publication history
Controlled execution of a content job processes selected content, destination, settings, approval, attempt, outcome and time. The existing private evidence comprises individual Telegram/Bluesky test texts and an imported private YouTube receipt without a new upload. For the operator’s business content, this serves traceable testing; minimal duplicate-protection evidence prevents unintended repeated actions (each under Article 6(1)(f) GDPR with a separate purpose). A local preview or media approval does not create a TikTok post. Changing content or destination invalidates its approval. A future user contract could cover only data required for the expressly requested job, not advertising or unlimited history retention.
Private staging and temporary TikTok delivery
Private staging stores only selected files, type, size, checksum and job binding. It is not a permanent cloud media library. Separate TikTok delivery uses restricted, random retrieval links for immutable copies. Access is valid for 90 minutes; expiry or revocation blocks retrieval. Existing maintenance removes expired copies on its next minute run; downtime can delay physical removal. An uncertain delivery outcome does not extend access validity. Old unbound copies become eligible for cleanup after 180 minutes; minimal metadata are retained for seven days. This applies to the delivery copy, not automatically to private source files or backups. Testing has used synthetic transport only, with no TikTok API media transfer. Necessary staging of the operator’s test media serves controlled functional testing (Article 6(1)(f) GDPR); transfer to TikTok requires a separate lawful approval.
Operations and security evidence
Normal operations/error logs contain limited event categories, status and time for failure detection. The technically configured 14-day policy applies with rotation and cleanup; downtime and file-based rotation can delay removal. The basis is Article 6(1)(f) GDPR: detecting failures without logging content or secrets. This policy does not cover every system, SSH or provider log. The Authority Ledger and Chronicle hold separate minimal permission, revocation, event and revision evidence to prevent unauthorized actions and the revival of revoked permissions after restore (Article 6(1)(f) GDPR). Hashes and identifiers can remain personal data. The need for current revocation evidence does not automatically justify keeping every old event and full backup indefinitely.
Recipients and their functions
Hetzner Online GmbH supplies PWS hosting, server backups, BX11 storage and business email, processing the PWS data held there on our behalf. Hetzner separately acts as controller for its own customer, contract and security data. Conclusion and specific coverage of the required processing agreement must be evidenced for these services; a public template is not evidence of conclusion. Apple supplies local operating-system/authenticator functions; user-chosen Apple account and synchronization services are separate. Google/YouTube, Meta/Instagram, TikTok, Telegram and participating Bluesky/AT Protocol services receive data needed for the actively used platform function and act as controllers for their own services. They are not generally described as PWS processors. Joint controllership depends on actually shared decisions about purposes and means; an API connection alone does not establish it. Processing on behalf of future business customers is not yet a released service.
Locations and international transfers
The PWS server is in Nuremberg and BX11 backup in Falkenstein, Germany. Platform services may process data outside the EEA. Google LLC’s EU-US DPF participation is active in the official register, covering Google LLC and the US subsidiaries specified there. Meta Platforms, Inc. is registered as active with recertification under review; other entities are not automatically covered. This is not a general adequacy assurance for all US recipients. Google and Meta additionally describe standard contractual clauses for relevant transfers. For EEA accounts, TikTok names TikTok Technology Limited (Ireland) and TikTok Information Technologies UK Limited and international processing, including in the USA, Malaysia and Singapore and access from other countries. Current Developer Data Sharing Terms distinguish controllers and provide SCCs for their specifically defined restricted receipt of TikTok data; they do not automatically evidence every transfer direction from PWS to another recipient.
Further transfer limits and safeguards
Telegram Messenger Inc. is established outside the EEA; Telegram identifies further group companies in the British Virgin Islands and Dubai and intra-group SCCs. Bluesky Social, PBC (USA) describes worldwide processing and safeguards including SCCs; a federated network may redistribute public content. These provider statements do not prove a PWS-executed SCC agreement for every direct transfer. The Telegram, Bluesky and precise TikTok transfer directions therefore remain documented assessment gaps before external product release. They do not authorize new transfers concerning data subjects. The static website does not initiate these connections. No PWS cloud processor or US DPF coverage is claimed for local Apple functions. Correspondents and user-chosen synchronization may use their own international services. Our privacy contact supplies information about specifically applicable safeguards and copies; only safeguards actually in place will be confirmed.
Retention and its limits
The periods below describe actual technology. Where no fixed period exists, the active purpose, unresolved jobs, necessary revocation blocks and specific statutory duties are the relevant criteria. Data without a remaining necessity should be erased or effectively anonymized. Missing automatic cleanup does not create an unlimited retention right; the outstanding manual erasure and backup procedures are not released as an external product service in this limited testing.
| Data class | Actual technical state |
|---|---|
| Operations/error logs | 14 days in PWS API/operations journals and monitor; rotation/downtime may delay removal. |
| System/SSH logs | Separate system rotation; no general 14-day deadline. |
| Sessions and devices | Access five minutes, refreshable session at most 24 hours; expiry is not row erasure. No confirmed maximum for device/old-row cleanup. |
| Account and passkeys | Active private use; removing permissions blocks access. General final account erasure is not yet released. |
| Platform credentials and metadata | For the required valid connection; assess expiry/revocation and erasure requests. No generally confirmed metadata period. OAuth state valid for five minutes. |
| Publication/approval history | Only necessary job and duplicate evidence; no justified general permanent archive. YouTube API data separately: 25/30 days locally while app runs. |
| Local media and variants | User-managed working files/exports; no automatic external erasure. |
| Private media staging | Default cleanup eligibility after 24 hours since update; uncertain or open jobs can be excluded. No general active scheduler evidenced. |
| TikTok delivery copies | 90-minute access; removal by minute timer, orphan copies eligible after 180 minutes; minimal metadata seven days. |
| Authority and Chronicle | Current revocation/revision blocks protect against stale restore; old events have no confirmed general expiry. Retry receipts: 7/30 days, removed when compact() is invoked. |
| Support email | Enquiry until resolved; further storage only where specifically necessary. No automatic erasure/mailbox-backup period evidenced. |
| Hetzner/BX11 backups | Seven rotating server slots replaced by successful backups; BX11 all versions without automatic expiry/deletion. No immediate selective removal from old backups. |
Backups and restore
Hetzner server backups have seven rotating slots. An old slot is replaced by a successful new backup; seven slots do not guarantee erasure after seven calendar days. Erasure from the active system does not selectively remove a record from old disk images. Separate encrypted BX11 backups currently retain all versions; automatic expiry/deletion rules are not configured. Ordinary Owner/Authority exports exclude platform tokens; full server images can contain encrypted vaults, session metadata and older data. Backups serve protected recovery and integrity checking, not normal content use. Current revocations, erasure restrictions and log cleanup must be reapplied before service resumes. A verifiable retention endpoint for historical full versions remains outstanding; encryption alone does not replace storage limitation. You manage user-selected local copies yourself.
Your rights
Under the statutory conditions, you may request access, rectification, erasure and restriction. Portability applies in particular to automated processing of data you supplied based on consent or a contract. For processing under Article 6(1)(f) GDPR, you may object on grounds relating to your particular situation. You may withdraw a specific GDPR consent for the future without affecting the lawfulness of earlier processing. No general consent is claimed for the core activities described here. Requests: legal@getpws.com or by post to the controller. See Data deletion for the safe procedure. Any justified refusal or restriction will be explained. You may complain to a supervisory authority, particularly the Hamburg data protection authority, or in your habitual residence, workplace or the place of the alleged infringement.
Sources, required data and automation
Contact and content data come from you; platforms confirm identity, permissions, Creator Info and publication status. The authenticator and system generate security and technical metadata. Connection/content data are optional in the sense that you may omit the corresponding feature; it cannot run without the necessary data. No account is needed to read the website. Data about individuals obtained elsewhere additionally require Article 14 GDPR information, generally no later than one month or the first contact or disclosure; publishing this page does not replace every required individual notice. The described scope includes no solely automated decision with legal or similarly significant effects on individuals. Scheduling, analysis and approval checks are technical working functions, not personal profiling. Purpose changes will be explained before implementation.
YouTube data and revocation
PWS uses YouTube API Services for the existing channel connection and its historical private receipt. This involves authorization, channel identity and video/status data needed for the selected operation. Content goes to YouTube only for a separately approved operation. YouTube Terms of Service and Google Privacy Policy also apply. Revoke access through Google account permissions. You may expressly request erasure of YouTube data stored by PWS through our privacy contact; this does not delete your Google account or automatically remove videos from YouTube. Google requires erasure of the affected API data as soon as possible within seven calendar days of a deletion request, account closure or revocation in PWS; in-app revocation also requires immediate programmatic token revocation. Revocations through the Google account must be checked regularly and affected data erased within 30 calendar days of that revocation. Other stored API data must be refreshed or erased within 30 days. Existing local 25/30-day reconciliation runs only while the app is open. Continuous server/dormancy/backup compliance has not yet been evidenced, so external YouTube product release remains open. This limitation is not an exemption from provider duties.