Terms of Service

Provider and customers

OfficeOS is operated by Harro Krog as an Einzelunternehmen in Germany. These Terms govern the OfficeOS website, dashboard, creator account, request workflow, revenue share, custom quotes, waitlist pages, and app-related services.

These Terms cover the OfficeOS side of the relationship: officeos.co, the dashboard, and the landing and waitlist pages OfficeOS operates on its own domains. They do not govern the finished app OfficeOS builds for a creator. That app belongs to the creator, and the contract between the creator and their own app users is the creator's own terms and privacy notice.

OfficeOS is intended for creators, app owners, founders, and businesses acting for professional or commercial purposes. If mandatory consumer protection law applies to you, these Terms do not limit rights that cannot legally be limited.

If you conclude a contract with OfficeOS for a business, trade, freelance, or professional purpose, you confirm that you act as an entrepreneur within the meaning of Section 14 BGB and not as a consumer within the meaning of Section 13 BGB.

What OfficeOS does

OfficeOS helps you scope, design, build, review, publish, and improve subscription app projects. The service may include app design, implementation, paywalls, subscriptions, in-app purchases, product analytics, launch offers, push campaigns, QA, release preparation, third-party setup, documentation, and support.

A customer app may depend on an OfficeOS-operated backend, database, storage, authentication, analytics, automation, or API layer. Unless a written order form says otherwise, OfficeOS may operate that service layer through OfficeOS-controlled provider accounts such as Supabase or similar infrastructure.

OfficeOS is not a law firm, tax advisor, accountant, payment institution, app-store approval authority, platform operator, financial advisor, or business-success guarantor. You remain responsible for your app idea, business model, content, legal compliance, customer promises, pricing, taxes, and final release decisions.

Order forms and scope

The Creator Agreement, an invoice, a quote, a statement of work, or another written order form defines the specific work for your project. Where an individually agreed contract conflicts with these Terms, the individual agreement controls for that project unless it says otherwise.

An order form should identify the app goal, included features, platforms, revenue systems, analytics, required customer access, revision rounds, monthly app changes, timeline assumptions, revenue share or price, billing schedule, cancellation terms, IP handoff terms, and special exclusions.

Work outside the accepted scope requires a new accepted app change, written quote, agreed scope change, or separate order form. New features, redesigns, integrations, analytics events, paywalls, campaigns, app flows, store assets, or platform submissions can count as new scope.

The usual workflow starts with discovery based on your channel, audience, goals, content, and rough app direction. OfficeOS may then prepare a concept, wireframes, design direction, feature plan, and monetization plan for approval before implementation starts.

Approval of a concept, wireframe, design direction, monetization model, or implementation plan means OfficeOS may rely on that direction for build work. Later changes to the approved direction can be treated as new scope even if implementation has not finished.

Side agreements, scope changes, timeline changes, discounts, extra services, and special commitments should be confirmed in text form. OfficeOS may refuse to treat informal calls, chats, or assumptions as binding changes unless OfficeOS confirms them.

Customer purchase terms, procurement terms, platform terms, email footers, or other counterterms do not apply unless OfficeOS expressly accepts them in writing.

Scope, chat, revisions, and app changes

Your Creator Agreement or order form sets the service level for your project. It may cover launch work, revision rounds, monthly app changes, analytics, bug fixes, support priority, or custom work rules.

Unlimited chat means you can message OfficeOS about questions, feedback, planning, and clarification. Chat does not create unlimited build work, unlimited revisions, unlimited new features, or unlimited support obligations.

A revision round means one consolidated review pass on work that is already in scope. A request that changes the approved direction, adds new functionality, changes the product model, or requires new third-party setup can be treated as an app change or new scope.

Unless the order form says otherwise, included launch revision rounds apply after OfficeOS delivers a working draft, review build, or release candidate for feedback. They do not reset for every new build, app-store submission, or monthly app change.

A monthly app change means accepted OfficeOS work on an in-scope change. It does not guarantee that Apple or another platform will review, approve, publish, or make that change available in the same month.

Bug fixes cover issues caused by OfficeOS work that prevent accepted in-scope functionality from working as approved. Changes caused by new customer instructions, third-party changes, customer-side configuration, unsupported devices, platform review feedback, or new business requirements may be treated as new scope.

Free extras, goodwill help, beta features, experiments, informal advice, or work provided outside the written scope do not create a permanent entitlement. OfficeOS may change or withdraw them unless they are included in an accepted order form.

Design review and acceptance

Design work is evaluated against the accepted scope, brand materials, written direction, and revision rounds for the project. General dissatisfaction, changed taste, new inspiration, or a new brand direction after work starts does not by itself make delivered work defective.

Design feedback must be specific enough to act on, such as requested copy, colors, layout changes, missing states, unclear flows, or examples that fit the accepted scope. Vague feedback may be returned for clarification and may delay delivery.

If the included revision rounds are used, further design changes may require an accepted app change, agreed scope change, custom quote, or separate order form. OfficeOS may still fix clear in-scope defects caused by OfficeOS work.

Customer responsibilities

You must provide accurate instructions, complete requirements, lawful materials, valid approvals, timely feedback, and the access needed to complete approved work. You must review delivered work before release and tell OfficeOS promptly if something is wrong, missing, risky, or not approved.

You must not ask OfficeOS to build deceptive, illegal, infringing, abusive, privacy-invasive, unsafe, or platform-violating features. You are responsible for the legality of your app idea, content, trademarks, screenshots, testimonials, revenue claims, customer data, and marketing promises.

You are responsible for publishing decisions, app-store submissions, account ownership, customer support promises, refund policies for your own app users, privacy notices for your own app, and any regulated advice or restricted content in your app.

You are responsible for your customer-facing terms, privacy notices, refund promises, support promises, paid membership terms, app-store disclosures, and communications to your own app users if your app changes, pauses, shuts down, or loses access to a required third-party or OfficeOS-operated service.

You are responsible for industry-specific compliance if your app involves health, fitness, finance, investing, employment, education, children, gambling, alcohol, adult content, political content, regulated advice, contests, or any other restricted category.

You should name one authorized project contact who can approve scope, design, releases, credentials, payment decisions, and launch decisions. OfficeOS may rely on instructions and approvals from that contact unless you tell OfficeOS otherwise in writing.

You are responsible for keeping your own backups and exports of business-critical data, customer lists, content, credentials, store materials, payment records, analytics, source repositories, and app assets unless a written order form says OfficeOS is responsible for a specific backup task.

If you delay feedback, approvals, access, content, credentials, app-store responses, payment-provider responses, or other cooperation, OfficeOS may pause timelines, move work to a later slot, charge separately for extra effort, or treat resulting delays as outside OfficeOS control.

Support, maintenance, and records

Support is provided through the channels and priority level agreed for your project. Unless agreed otherwise, support is not a 24/7 emergency, uptime, moderation, or customer-support service for your own app users.

Bug reports and support requests must include enough detail to understand the issue, such as affected account, device, browser, screenshots, steps to reproduce, expected result, actual result, and relevant third-party messages.

OfficeOS may perform maintenance, dependency updates, security patches, provider migrations, or infrastructure work that temporarily affects access or delivery. OfficeOS will try to avoid unnecessary disruption but does not guarantee uninterrupted access unless expressly agreed in writing.

Project chats, dashboard activity, approvals, invoices, Stripe records, release notes, repository history, and support logs may be used to document scope, acceptance, payment status, timing, and customer instructions.

Subcontractors and processors

OfficeOS may use qualified freelancers, contractors, service providers, hosting providers, payment providers, email providers, analytics providers, AI providers, and other subcontractors to provide the service.

If a subcontractor processes personal data on behalf of OfficeOS or on behalf of a customer through OfficeOS, OfficeOS will use appropriate data protection arrangements where required by law.

OfficeOS remains responsible for subcontracted service work to the extent required by these Terms, but OfficeOS is not responsible for independent platform decisions, outages, policy changes, account suspensions, or other acts of third-party providers outside OfficeOS control.

You must not knowingly bypass OfficeOS to contract directly with freelancers, contractors, or service providers introduced by OfficeOS for the same project during the project and for 12 months after the introduction, unless OfficeOS agrees in writing.

Accounts, credentials, and third-party access

You must keep your account secure and only grant OfficeOS the minimum access reasonably needed for approved work. If possible, use role-based access, temporary access, test credentials, and revocable invitations instead of sending passwords or unrestricted production secrets.

You remain responsible for your accounts with Apple, RevenueCat, Supabase, GitHub, Stripe, analytics providers, email providers, and other third-party services. OfficeOS is not responsible for third-party downtime, policy changes, rejected submissions, account suspensions, payment holds, lost credentials, or provider decisions outside OfficeOS control.

If your app uses your own Apple, RevenueCat, or similar account together with an OfficeOS-operated backend, those systems remain separate. Ownership of your app-store account, payment-provider account, or subscription account does not include ownership of OfficeOS provider accounts, backend infrastructure, reusable code, internal tools, or operations access unless an order form says so.

Native app work that depends on Apple, RevenueCat, or similar platforms requires that you keep the required paid accounts, subscriptions, tax agreements, banking details, app-store agreements, and platform access active. OfficeOS may pause or refuse work that cannot be completed because a required account is missing, unpaid, expired, restricted, unverified, or not accessible.

If role-based access is not available for your account type, approved work may require you to provide temporary account credentials, authentication codes, screen sharing, or direct submission help. You are responsible for deciding whether to provide that access, limiting it where possible, supervising sensitive actions, and changing credentials or revoking access after the work is complete.

You must revoke OfficeOS access when it is no longer needed or when you no longer want OfficeOS to have access. OfficeOS is not responsible for damage caused by credentials, access rights, or third-party accounts that you create, share, keep active, misconfigure, or fail to secure.

Hosted backend and service dependency

If OfficeOS operates the backend, database, storage, authentication, analytics, API, push, automation, or similar service layer for your app, that hosted layer is an ongoing OfficeOS service and not a permanent standalone deliverable unless a written order form says otherwise.

Your app may become partly or fully unusable if the hosted layer is suspended, terminated, unavailable, migrated, or no longer covered by your Creator Agreement. You are responsible for making sure your own app users understand any dependency, outage, shutdown, refund, or continuity risk that affects them.

OfficeOS may suspend or restrict the hosted layer for non-payment, chargebacks, cancellation, legal risk, security risk, platform risk, abuse, or breach of these Terms. Where practical, OfficeOS will give reasonable notice before suspension for non-payment, but OfficeOS may act immediately for security, legal, abuse, or platform-risk reasons.

Handoff, migration, export, self-hosting support, source-code transfer, database export, provider transfer, or operation under your own Supabase, hosting, or cloud account is included only if the Creator Agreement or order form says so. Otherwise it requires a separately agreed and paid transition project.

Waitlist pages and launch emails

Before a creator's app exists, OfficeOS may run a landing page and a waitlist for it on a domain OfficeOS operates. If you join a waitlist there, you are signing up with OfficeOS: OfficeOS is the controller of that signup and processes it under the OfficeOS privacy policy, not under the creator's.

The consent text on the signup form names the creator the list belongs to and covers two things: joining the list, and receiving launch and marketing emails about the app. OfficeOS confirms the address by email before sending anything else, and sends every later email under the creator's brand with a working unsubscribe. Unsubscribing withdraws consent for further email without removing you from the underlying list.

The creator can view and export their waitlist through the dashboard, which makes them a recipient of the data rather than a co-controller of the OfficeOS copy. Once an export leaves OfficeOS, the creator carries their own legal basis and privacy notice for it.

When a creator's project ends, 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 it to keep.

Data processing for your app users (Article 28 GDPR)

Your app's users are your users, not OfficeOS customers. You decide why and how their personal data is processed, so you are the controller. OfficeOS processes that data only on your documented instructions, as your processor within the meaning of Article 28 GDPR. This section is the written agreement Article 28(3) requires. Where you and OfficeOS sign a separate Auftragsverarbeitungsvertrag, that document controls.

The subject matter is building and operating your app, for as long as your Creator Agreement runs. The nature and purpose of the processing is hosting, authentication, storage, subscription and entitlement handling, product analytics, push, support, and QA. The data covers app-user identifiers, account details, subscription and purchase events, entitlement state, content access, product analytics, push tokens, device metadata, and technical logs. The data subjects are the people who use your app.

OfficeOS processes the data only for those purposes, keeps everyone who touches it under a duty of confidentiality, applies appropriate technical and organizational measures under Article 32, and helps you handle data subject requests, breach notifications, and impact assessments to the extent you cannot handle them yourself in the dashboard. OfficeOS tells you about a personal data breach without undue delay after becoming aware of one, and makes the information available that you need to show compliance.

You give OfficeOS general authorization to use subprocessors, including the hosting, database, email, analytics, and monitoring providers listed by category in the OfficeOS privacy policy. OfficeOS binds each of them to equivalent obligations and stays responsible for their performance. OfficeOS tells you before adding or replacing a subprocessor, and you may object on reasonable data protection grounds, in which case either party may end the affected service.

When your Creator Agreement ends, OfficeOS gives you a final export of the app-user data and then deletes its copy, apart from records the law requires it to keep. You may verify compliance with this section once a year with reasonable notice, or more often where a supervisory authority requires it, without disrupting OfficeOS operations or exposing other customers' data.

Waitlist signups collected on OfficeOS pages sit outside this section. There OfficeOS is the controller, as set out above.

Customer materials and intellectual property

You keep ownership of your app content, brand assets, customer data, business data, and uploaded materials. You give OfficeOS permission to use those materials to provide the service, complete approved work, troubleshoot, document requests, market the app under your brand where your Creator Agreement grants that licence, and support your account.

You represent that you have the rights needed to provide all materials, assets, app screenshots, trademarks, copy, data, credentials, and instructions. You are responsible for claims caused by materials or instructions you provide, including claims involving copyright, trademarks, privacy, confidentiality, publicity rights, misleading advertising, or unlawful content.

On a revenue-share project, OfficeOS keeps the source code, backend, and infrastructure, and the Creator Agreement governs what you receive. On a project paid by quote or invoice, customer-specific deliverables become yours after OfficeOS receives all amounts due for the relevant work, and rights of use and handoff materials do not transfer before then.

OfficeOS keeps ownership of pre-existing code, templates, reusable components, internal tools, workflows, know-how, generic patterns, and non-customer-specific materials. Third-party software, open-source components, app-store tools, SDKs, APIs, and hosted services remain subject to their own license terms and provider rules.

Source code, exports, credentials, documentation, transfer help, or deployment access are provided only where the Creator Agreement, order form, or a written agreement includes them, and after all due amounts for the relevant work have been paid.

Delivery, acceptance, and release decisions

OfficeOS may refuse, pause, or return a request for revision when the request is ambiguous, unsafe, unsupported, unlawful, outside the agreed scope, missing required access, blocked by a third party, or likely to create legal, security, privacy, platform, or business risk.

Delivery estimates are not guarantees. Timelines depend on clear scope, available access, customer feedback, third-party systems, platform review, payment status, and technical complexity. A request is not ready to start until OfficeOS has the information, access, and payment status needed to work safely.

You are responsible for reviewing work before it is shipped, submitted, published, or used with real customers. If you approve release, merge code, publish an app, send marketing, or use delivered work in production, you accept responsibility for that decision.

Unless mandatory law or a written order form says otherwise, delivered work may be treated as accepted if you approve it, use it in production, publish it, or do not report a specific in-scope defect within five business days after OfficeOS asks for review.

App store submissions and app updates are controlled by Apple and other platform operators. Review can take longer than expected, submissions may require changes, and platforms may reject, delay, suspend, or remove an app or update for reasons outside OfficeOS control.

OfficeOS can help prepare release-ready work and review materials, but Apple, RevenueCat, Supabase, GitHub, Stripe, analytics providers, email providers, and other third parties make their own decisions. OfficeOS does not guarantee app-store approval, payment approval, account acceptance, ranking, revenue, conversion rates, retention, churn reduction, uptime, or third-party availability.

Defects, warranty, and maintenance

A defect exists only when delivered work materially fails to match the accepted written scope or agreed quality. Missing features, new preferences, new business goals, platform feedback, third-party changes, customer-side configuration, or post-acceptance requests are not defects by themselves.

You must report defects in text form with enough detail for OfficeOS to reproduce or understand the issue. OfficeOS may choose whether to fix the defect, provide a replacement, or propose another reasonable solution where permitted by law.

OfficeOS may refuse defect work while due invoices remain unpaid, unless you have a justified statutory right to withhold payment. Maintenance, monitoring, content updates, operating support, post-acceptance changes, and fault correction after acceptance are included only where the Creator Agreement or order form says so.

Fees and revenue share

OfficeOS is paid through the revenue share set in your Creator Agreement, not through a subscription you buy from OfficeOS. Stripe Connect applies the split at the moment your users pay: your share settles into your own connected Stripe account and the OfficeOS share comes off the top as a platform fee. In normal operation there is no invoice from OfficeOS to pay.

You are the merchant of record for every sale to your app users, so VAT and other taxes, refunds, chargebacks, and your users' support and contract terms are yours. Purchases your users make through Apple or Google in-app purchase stay entirely yours, and OfficeOS takes no share of them.

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 that connection is complete. If revenue covered by the share is collected outside the connected account, OfficeOS may invoice for its share of it.

Where a project instead runs on a written quote, milestone plan, or setup fee, that document sets the fees and the payment schedule, and OfficeOS may require payment to clear before work starts or continues. Unless required by law or agreed in writing, fees are non-refundable once work starts or a request is accepted.

Chargebacks, failed payments, late payments, or unpaid invoices may lead to paused work, account restriction, delayed delivery, withheld handoff, suspended usage rights, hosted-backend suspension, or termination.

You may set off, withhold, or reduce payment only for claims that are undisputed, finally established by a court, or legally inseparable from the invoice you are disputing. This does not limit mandatory statutory rights.

Ending the service

If your Creator Agreement ends, an invoice stays unpaid, a payment is charged back, or OfficeOS terminates for a reason set out in these Terms, OfficeOS may stop app changes, design work, support, analytics review, release preparation, monitoring, waitlist emails, troubleshooting, and other ongoing services.

Ending the agreement or failing to pay does not require OfficeOS to keep supporting, updating, monitoring, publishing, hosting, or operating your app or its backend. You remain responsible for your own app, users, third-party accounts, store listings, subscriptions, customer support, and business operations.

If you terminate a custom project without good cause before completion, you remain responsible for work performed, committed expenses, accepted milestones, and any cancellation payment stated in the order form. If no order form rule applies, OfficeOS may invoice reasonable compensation for work performed and costs already committed.

Transition help, exports, documentation, emergency support, or handoff work after termination is provided only if the Creator Agreement or order form includes it, or if it is separately agreed and paid.

OfficeOS does not permanently store project files, exports, credentials, analytics, chat history, repositories, or app assets for you after termination or handoff unless a written order form says so. OfficeOS may delete or archive materials when they are no longer needed, subject to legal retention duties and the deletion duties in the data processing section.

Revenue, analytics, and business results

OfficeOS may build paywalls, subscriptions, offers, product analytics, cohorts, funnels, churn signals, push campaigns, and retention flows. These tools help you measure and improve the app, but they do not guarantee profit or growth.

Analytics may be delayed, incomplete, estimated, blocked, sampled, misconfigured, or affected by privacy settings, app-store rules, SDK behavior, payment-provider data, device settings, user consent, or third-party outages. You should not rely on OfficeOS analytics as your only source for financial, tax, legal, or operational decisions.

Any revenue examples, projections, calculators, or strategic suggestions are estimates or planning aids. You are responsible for pricing decisions, customer promises, marketing claims, tax treatment, financial forecasts, and business decisions.

Confidentiality and marketing use

OfficeOS will not knowingly publish your private app data, credentials, revenue, screenshots, customer information, or business materials as a public case study, testimonial, portfolio item, or marketing claim without written permission for that specific use. The Creator Agreement grants that permission for the app, its landing page, and the design work, and excludes your revenue figures and user data.

You also agree not to publish misleading statements about OfficeOS, fake testimonials, false revenue claims, or materials that imply endorsement by a person or brand without permission.

Acceptable use and refusal rights

You may not use OfficeOS to create or support illegal, deceptive, harmful, infringing, abusive, discriminatory, privacy-invasive, security-breaking, spam, malware, scraping, impersonation, fake-review, or platform-evading activity.

OfficeOS may refuse, suspend, or terminate work if a request creates legal, privacy, security, reputational, payment, platform, or operational risk. OfficeOS may also remove access, preserve records, or cooperate with lawful requests where required.

Force majeure and third-party outages

OfficeOS is not responsible for delay or failure caused by events outside reasonable control, including platform outages, hosting outages, payment-provider outages, app-store review delays, cloud-provider incidents, internet or power failures, security incidents, strikes, illness, war, government action, legal restrictions, natural events, or other force majeure events.

If such an event affects delivery, affected timelines are extended for the period of disruption plus a reasonable restart period. OfficeOS may pause, reschedule, or adjust affected work where continuing would be unsafe, unlawful, impractical, or commercially unreasonable.

Liability

Nothing in these Terms limits liability where liability cannot legally be limited, including liability for intent, gross negligence, injury to life, body, or health, mandatory product liability, or mandatory consumer rights.

To the extent permitted by law, OfficeOS is not liable for indirect damages, lost profits, lost revenue, lost data, loss of goodwill, business interruption, third-party platform decisions, customer-side misconfiguration, customer-provided materials, unauthorized customer actions, or claims caused by instructions or materials you provide.

If data is lost, OfficeOS is liable only for the restoration effort that would have been required if you had kept proper and current backups, unless mandatory law requires otherwise.

To the extent permitted by law, OfficeOS liability for ordinary negligence is limited to foreseeable, contract-typical damages. Any specific liability cap, fee-based cap, or B2B liability structure should be reviewed by a German lawyer before use.

Indemnity for customer-caused claims

To the extent permitted by law, you agree to reimburse OfficeOS for losses, costs, reasonable legal fees, and claims caused by your unlawful instructions, customer materials, missing rights, false marketing claims, privacy violations, platform violations, misuse of third-party accounts, or breach of these Terms.

Changes, termination, and governing law

OfficeOS may update these Terms as the service changes. Continued use after an update means you accept the updated Terms, unless mandatory law requires a different process.

Either party may stop using the service according to the applicable Creator Agreement or order form. OfficeOS may terminate or restrict access for non-payment, abuse, security risk, legal risk, or breach of these Terms.

You may not assign or transfer your contract, account, project, or rights under these Terms to another person or business without OfficeOS consent, unless mandatory law gives you that right. OfficeOS may assign these Terms to a legal successor, payment provider, or acquirer of substantially all relevant business assets.

German law applies, excluding the United Nations Convention on Contracts for the International Sale of Goods (CISG), except where mandatory consumer protection law says otherwise. If you act as a merchant, legal entity under public law, or special fund under public law, Hamburg, Germany is the place of jurisdiction to the extent permitted by law. Any mandatory jurisdiction, consumer, data protection, or platform rules remain unaffected.

Severability

If any provision of these Terms is invalid or unenforceable, the remaining provisions remain effective. The parties should replace the invalid or unenforceable provision with an effective provision that comes closest to the economic purpose of the original provision, where legally permitted.