Privacy Policy

Controller and scope

This Privacy Policy explains how OfficeOS processes personal data when you visit the website, join a waitlist, create an account, request app work, upload materials, communicate with us, or grant access to third-party tools.

OfficeOS is operated by Harro Krog as an Einzelunternehmen in Germany. The complete provider details are listed in the legal notice / Impressum and can be used for privacy requests.

This policy covers the OfficeOS side: officeos.co, the creator dashboard, and the landing and waitlist pages OfficeOS operates on its own domains. It does not cover the finished app OfficeOS builds for a creator. That app belongs to the creator, its users are the creator's users, and the creator's own privacy notice governs their data. If you signed up inside a creator's app, read that creator's notice instead.

For website visitors, prospects, account users, billing contacts, waitlist signups, and OfficeOS customers, OfficeOS acts as controller. For personal data from a creator's app users, the creator is the controller and OfficeOS is the processor under the data processing section of the Terms of Service.

Personal data we collect

We may collect account details, name, email address, company or project name, billing status, request descriptions, uploaded files, app screenshots, comments, support messages, access confirmations, technical logs, device and browser metadata, cookie preferences, payment event references, and website analytics.

During discovery and planning, we may review information you provide about your channel, audience, content, community, products, offers, app goals, monetization ideas, analytics, screenshots, and existing tools.

When you invite OfficeOS to systems such as App Store Connect, Google Play Console, RevenueCat, Supabase, GitHub, Stripe, analytics tools, email tools, or similar services, we may process data visible through that access for approved service work, verification, QA, support, release preparation, billing, and security.

If OfficeOS builds or reviews product analytics for a creator's app, we may process app events, funnel steps, paywall views, subscription status, campaign source, cohort membership, churn signals, device metadata, and similar product usage data. Creators should avoid sending unnecessary sensitive data into app analytics.

Waitlist signups

Before a creator's app exists, OfficeOS runs a landing page and a waitlist for it on a domain OfficeOS operates. OfficeOS decides how that list is collected, stored, and secured, so OfficeOS is the controller of it under Article 4(7) GDPR, even though the page carries the creator's brand.

We collect the email address you enter and the basic technical data that comes with the request, such as time of signup and the page you signed up on. We use it to tell you when the app launches, to send launch and marketing emails about that app, and to invite you into the app once it is live.

The legal basis is your consent under Article 6(1)(a) GDPR, together with the consent that Section 7 UWG requires for marketing email. The signup form asks for both in the same step: joining the list, and receiving those emails. We confirm your address by email before sending anything else. Every email carries a working unsubscribe, and unsubscribing withdraws your consent for further email without deleting you from the list itself. To be removed from the list entirely, write to the contact address below.

The creator whose app you signed up for can see and export the list, and the signup form names them. Once an export leaves OfficeOS, the creator processes it as a separate controller under their own privacy notice.

When a creator's project ends, the service stops: OfficeOS stops the emails, takes the page offline, gives the creator a final export, and deletes its own copy apart from records the law requires us to keep.

Why we process data

We process personal data to provide OfficeOS, create and manage accounts, scope requests, implement approved work, run QA, prepare releases, document what changed, communicate with you, run waitlists and launch emails, process billing and revenue share, prevent abuse, secure the service, meet legal obligations, and improve the product.

We do not use customer app data, credentials, uploaded materials, or private business information to create public case studies, testimonials, or marketing claims unless you have given clear written permission for that specific use.

Legal bases

Where GDPR applies, we process data when it is necessary to perform a contract or take steps before entering into a contract, when we must comply with legal obligations, when processing is necessary for legitimate interests such as security, fraud prevention, support, service improvement, payment handling, service documentation, and legal defense, or when you have given consent.

You can withdraw consent where processing is based on consent. Withdrawal does not affect processing that already happened lawfully before withdrawal.

Cookies, local storage, and analytics

The website and dashboard may use necessary cookies or local storage to keep the service working, remember session state, remember cookie preferences, and protect accounts.

Optional analytics cookies or similar technologies may be used only where allowed by law or consent settings. These help OfficeOS understand which pages visitors read and how the website performs.

Product analytics inside a creator's app are separate from website analytics. If an app uses analytics built or configured by OfficeOS, the creator's own app privacy notice should explain that analytics to their app users.

Sharing and processors

We do not sell personal data. We may share data with service providers that host, secure, analyze, bill, email, monitor, or support OfficeOS. These providers may include infrastructure, database, payment, email, error monitoring, analytics, communication, and authentication providers.

Current provider categories may include Vercel or similar hosting providers, Supabase for database and authentication, Stripe for payments, Resend or similar email providers, Sentry for error monitoring, OpenAI or similar AI providers where used for approved service work, and analytics providers where enabled.

We may also disclose data when required by law, to enforce agreements, to protect rights and security, to respond to lawful requests, or as part of a business transfer. We only share the data needed for the relevant purpose.

Creator app data and the processing agreement

Where OfficeOS processes personal data from a creator's app users, the creator is the controller and OfficeOS is the processor. The data processing section of the Terms of Service is the written agreement Article 28(3) GDPR requires for that relationship, and it lists the subject matter, purposes, data types, subprocessor rules, and deletion duties. A separately signed Auftragsverarbeitungsvertrag controls where one exists.

If OfficeOS operates the backend, database, authentication, storage, analytics, API, push, or automation layer for an app through an OfficeOS-controlled provider account, the providers behind that layer, such as Supabase, act as subprocessors.

Creator app data may include app-user identifiers, account details, subscription status, purchase events, entitlement state, content access, product analytics, support diagnostics, push tokens, device metadata, and technical logs, depending on the app configuration.

Creators are responsible for telling their app users how the app processes their data, which providers it uses, what analytics it runs, and how users can exercise their rights. OfficeOS can prepare the technical information for that notice, but the creator remains responsible for their own app privacy compliance.

If an app is suspended, canceled, migrated, or handed off, related app data may be exported, retained, archived, deleted, or made unavailable according to the Creator Agreement, the processing agreement, legal retention duties, and provider limits.

International transfers

Some providers may process data outside Germany or the European Economic Area. Where required, OfficeOS relies on appropriate safeguards such as adequacy decisions, standard contractual clauses, data processing agreements, or other lawful transfer mechanisms.

Retention

We keep personal data only as long as needed for the purpose collected, including service delivery, account management, accounting, tax records, dispute handling, fraud prevention, legal defense, and platform security.

Account, billing, and tax records may be kept for statutory retention periods. Request materials, access notes, support records, analytics notes, and billing references may be retained while an account is active and afterward where retention is necessary for legal, contractual, audit, or security reasons. Waitlist signups are kept while the creator's project runs and deleted when it ends, as described above.

Unneeded production credentials should not be sent to OfficeOS. If temporary access is no longer needed, you should revoke it in the relevant third-party provider.

Security and customer access

We use reasonable technical and organizational measures to protect personal data, including access controls and limiting use of customer tool access to approved work. No internet service is perfectly secure, and customers should avoid sharing unnecessary secrets, passwords, private keys, or unrestricted production access.

You remain responsible for managing your own accounts with Apple, Google, Stripe, RevenueCat, Supabase, GitHub, and other third-party providers, including revoking access when work is complete or when you no longer want OfficeOS to have access.

Your rights

Where applicable, you can request access, correction, deletion, restriction, portability, or objection to processing of your personal data. You may also have the right to complain to a data protection authority.

Some requests may be limited where we must keep data for legal obligations, accounting, security, dispute handling, legal defense, or to complete a contract.

Contact

For privacy questions or requests, contact OfficeOS at krogharro@gmail.com or by using the contact details listed in the Impressum.