Creator Agreement

What this is

This Creator Agreement is the written order form for a revenue-share app project between OfficeOS (Harro Krog, Einzelunternehmen, Hamburg, Germany) and you, the Creator. You accept it by checking the acceptance box during onboarding, by confirming acceptance in writing, or by letting OfficeOS start work after you received this document.

The OfficeOS Terms of Service apply to everything not covered here. Where this Agreement and the Terms of Service say different things about your project, this Agreement controls. You accept this Agreement as an entrepreneur within the meaning of Section 14 BGB and not as a consumer.

Nothing in this Agreement creates a partnership, a Gesellschaft bürgerlichen Rechts, a joint venture, an employment relationship, or shared liability. OfficeOS is your service provider. The revenue share is the price of that service and not a share of your profit or your business.

What OfficeOS does

OfficeOS scopes, designs, builds, submits, hosts, operates, and keeps improving a subscription app under your brand, together with a landing page for it. OfficeOS decides the technical implementation, the infrastructure, and the tools used to deliver that work.

Until you have your own domain, OfficeOS publishes your landing page on a subdomain of officeos.co that OfficeOS operates and controls. Moving the page to a domain you own is a separate step that OfficeOS agrees to in writing.

OfficeOS is not obliged to start, continue, or prioritize work before you have completed the onboarding steps, granted the required access, connected a Stripe account under the OfficeOS platform, and accepted this Agreement.

What you commit to

You provide your brand assets, content direction, and the access listed in the onboarding checklist, and you respond to questions and approval requests without unreasonable delay.

Within 30 days of your landing page going live, you publish at least three posts or stories on your main channel that link your audience to that page. After the app launches, you keep promoting it to your audience on a regular basis.

The promotion commitment is the reason OfficeOS builds without a fixed fee. If you do not meet it, OfficeOS may pause or take down the landing page, the waitlist, the app, and the backend under the section below, and that takedown is not a breach by OfficeOS.

Your brand and how OfficeOS may use it

You keep every right in your name, handle, likeness, logo, trademarks, and content. You confirm that you hold the rights needed to let OfficeOS use them, including rights in anything you supply that was made by someone else.

You grant OfficeOS a worldwide, royalty-free, non-exclusive licence to use your name, handle, likeness, logo, trademarks, and supplied content to scope, design, build, submit, host, operate, and market the app and its landing page, including on an officeos.co subdomain and in the launch and marketing emails OfficeOS sends to your waitlist. The licence lasts as long as OfficeOS works on your project, and it ends when this Agreement ends.

You also give OfficeOS written permission under the confidentiality section of the Terms of Service to name you as a customer and to show the app, the landing page, screenshots, and design work as a portfolio item, reference, and case study, during the project and after it ends. This permission does not cover your revenue figures, your user data, or anything else you mark as confidential in writing. You may withdraw it for future publications by writing to OfficeOS, and OfficeOS will stop using the material in new publications within a reasonable period.

OfficeOS will not register, apply for, or claim any trademark, company name, or domain based on your brand, and will not use your brand for anything other than your project.

Landing page, waitlist, and user data

The landing page and the waitlist run on OfficeOS infrastructure, on an OfficeOS-controlled domain, under the OfficeOS privacy policy. OfficeOS is the controller of the waitlist data within the meaning of Article 4(7) GDPR and decides how it is collected, stored, and secured.

People join the waitlist on the basis of the consent text shown to them on the signup form. That text names OfficeOS as the controller, names you as the creator the list belongs to and who will see it, and covers both joining the list and receiving launch and marketing emails about the app. OfficeOS confirms every signup by email before sending anything else, and every email carries a working unsubscribe. Neither party may use the waitlist data for anything the signup consent does not cover, and OfficeOS may change the consent text where the law requires it.

OfficeOS gives you an export of the waitlist signups on request and invites the list into your app at launch. Reading or exporting the list makes you a recipient of the data, not a co-controller of the OfficeOS copy. From the moment an export reaches you, you carry your own legal basis and your own privacy notice for it.

Personal data of the people who use your finished app is a separate matter. There you are the controller and OfficeOS is your processor under the data processing section of the Terms of Service.

OfficeOS only ever publishes the landing page and emails the waitlist under your brand. If this Agreement ends, OfficeOS stops the service: it stops emailing the waitlist, takes the page offline, and stops using the waitlist data. OfficeOS gives you a final export first, then deletes its copy except where the law requires it to keep records. You keep any export OfficeOS already gave you and handle it under your own privacy notice and legal basis.

Revenue share

App Revenue means what your users pay through the checkout pages OfficeOS builds and hosts for your app, after payment processing fees, refunds, chargebacks, and taxes. It is the money that actually reaches you on that route. Purchases your users make directly through Apple or Google in-app purchase are not App Revenue: those are entirely yours, OfficeOS takes nothing from them and is not involved.

OfficeOS receives 40% of App Revenue and you keep 60%, for as long as OfficeOS operates your app. Stripe Connect applies that split at the moment of each payment: your 60% settles into your own connected Stripe account and the 40% is taken as a platform fee, so there is no invoice to pay. There is no monthly retainer. If the app earns nothing, OfficeOS is owed nothing. Any setup or commitment fee applies only if agreed in writing before work starts.

Connecting a Stripe account under the OfficeOS platform is a prerequisite for going live, because the split cannot be applied to an account that is not connected. Checkout stays off until you complete that connection. If App Revenue is ever collected outside the connected account, OfficeOS may invoice for its share of it, payable within 7 days.

RevenueCat is the record both parties use to determine App Revenue. You keep the RevenueCat account and the store accounts, you keep OfficeOS invited with the access needed to read that data, and you do not disable, misreport, or route revenue around that tracking. Revenue that is deliberately routed around the tracking still counts as App Revenue.

You are the merchant of record for every sale to your users. You are responsible for VAT and other taxes on those sales, for refunds, for chargebacks, and for your own app users' support and contract terms. OfficeOS is not a party to your contracts with your users.

If an invoice is unpaid for more than 7 days after it falls due, OfficeOS may suspend the app, the backend, the landing page, and support until it is paid, after telling you first.

Ownership

You own your brand, your content, your audience, your store listings, your RevenueCat account, your payment accounts, and the subscriber and revenue data held in them.

OfficeOS owns the source code, templates, reusable components, design system, backend, internal tools, automations, infrastructure, and the officeos.co subdomain, including anything built while working on your project. You do not receive the source code, a copy of the backend, or the right to have the app operated by someone else, unless OfficeOS agrees to a transition project in writing and you pay for it.

Your app depends on the backend OfficeOS operates. If this Agreement ends, that dependency ends with it under the hosted backend section of the Terms of Service, and you are responsible for telling your own app users what that means for them.

Pausing, ending, and what survives

Either party may end this Agreement with 14 days notice in text form. Email, dashboard message, or a message in the channel the parties already use is enough.

OfficeOS may suspend or end it immediately, and take the app, landing page, waitlist page, and backend offline, if you do not meet the promotion commitment, if an invoice stays unpaid, if you revoke the access OfficeOS needs, or if your content or conduct breaks Apple, Google, Stripe, or German law or creates a serious legal, security, or platform risk.

When it ends, OfficeOS stops all work, hosting, support, and waitlist emails, takes the subdomain and waitlist page offline, and gives up the brand licence. You keep your brand, your accounts, your store listings, your data, and any waitlist export OfficeOS gave you. OfficeOS keeps the code and infrastructure and the right to show the work as a portfolio item and case study, and deletes its copy of the waitlist and app-user data except where the law requires it to keep records.

Invoices for revenue already earned stay payable after the Agreement ends, and OfficeOS may invoice a final month for App Revenue earned up to the end date.

No guarantees

OfficeOS does not guarantee App Store or Google Play approval, a launch date, waitlist signups, downloads, subscribers, revenue, retention, or any other business result. The delivery, warranty, and liability sections of the Terms of Service apply in full.

German law applies, excluding the CISG. Hamburg is the place of jurisdiction to the extent permitted by law.