Legal

1. Who we are, and what these terms cover

OKRGoal is a cloud service run by OKRI Sdn. Bhd. ("OKR Institute"), a company registered in Malaysia under number 201601036941 (1207882-D). Its registered office is at F-2-11, 2nd Floor, Block F, Pusat Komersil Jalan Kuching, No. 115, Jalan Kepayang, off Jalan Kuching, 51200 Kuala Lumpur, Malaysia, and its office is at 111, Jalan Telawi, 59100 Kuala Lumpur, Malaysia. In these terms, "we", "us" and "our" mean OKR Institute. "You" means the person or organisation that creates or uses an OKRGoal workspace.

These terms cover OKRGoal: the service you reach from okrgoal.com, the integrations that connect to it, and the support we give with it. They do not cover OpenOKR software you run yourself, which its licence governs (section 2). Support contracts for self-hosted OpenOKR, and OKR Institute's courses and coaching, have their own terms.

By creating a workspace, or by using one you have been invited to, you accept these terms. If you accept them for an organisation, you confirm that you are allowed to bind it, and "you" then means that organisation.

If your organisation has signed a separate agreement with us, such as an enterprise order form, that agreement wins where the two differ.

2. OKRGoal and OpenOKR

OKRGoal is OpenOKR, run for you. OpenOKR is open source under the GNU Affero General Public License, version 3 (AGPL-3.0), and the source of every release OKRGoal runs is on GitHub.

Nothing in these terms limits what the AGPL-3.0 lets you do with that software. You can download it, run it on your own servers, change it and share it, on the licence's terms. What these terms add is our service: running the software, securing it, backing it up, upgrading it and supporting you.

The AGPL-3.0 is a copyright licence. It gives no rights in our names or logos. How to use them is set out in Using the OpenOKR and OKRGoal names.

3. Your account and your workspace

• Give us accurate details when you sign up, and keep them current.
• Keep your password, passkeys, authenticator codes and backup codes to yourself. Tell us at once if you think someone else has used your account.
• You must be 16 or older to have an account. OKRGoal is for work and study.
• A workspace's owners and admins decide who joins it, what each person can do, which integrations and AI providers are switched on, and when it is exported or closed. If you are a member of a workspace someone else holds, its owners control it, including your access to it.
• The organisation that holds a workspace is responsible for what its members, guests and connected agents do in it.

4. Plans, seats and payment

4.1 Plans. The current plans and prices are on the pricing page. A plan is a monthly allowance of AI credits, a number of seats and a level of support. Every plan includes every feature.

4.2 Seats. Active and invited members count as seats. Guests, the OKR Coach and the OKR Champion, and people who have left do not. A person stops counting the day you suspend them. When a workspace is full, a new invitation is refused until you free a seat or add one. Nobody already in the workspace loses access.

4.3 The free plan. The free plan has the limits shown on the pricing page. We may change them with 30 days' notice. If a workspace is over a new limit, we will ask its owners to choose who goes. We will not remove anyone ourselves.

4.4 Paying. Paid plans are billed in advance, monthly or yearly, in the currency shown when you subscribe. Prices do not include taxes, which we add where the law requires. A plan renews for the same period until you cancel it. Adding people within your plan's seats costs nothing. If you move to a larger plan during a period, it starts at once, and you pay the difference for the rest of that period.

4.5 Price changes. We tell a workspace's owners at least 30 days before a new price applies to them. It applies from their next renewal.

4.6 Smaller plans. You can move to a smaller plan from the end of the current period. If the workspace has more people than the new plan allows, we tell you how many are over, and you decide who goes. We never pick for you.

4.7 Late payment. If a payment fails, we tell the owners and try again. If it is still unpaid 14 days after it was due, we may put the workspace into read-only mode until it is paid. In read-only mode everyone can still sign in, read everything and export the workspace.

4.8 Refunds. Fees are paid in advance and are not refunded. If you cancel, move to a smaller plan or remove people part way through a period, your plan carries on until the end of that period, and nothing is refunded for the time left or for unused AI credits. The only exceptions are those in sections 9, 12.4 and 16 of these terms and section 6.3 of the data processing agreement, and any refund the law requires.

5. AI features

5.1 What the AI does. Every workspace includes two AI teammates, the OKR Coach and the OKR Champion, and other features that use an AI model. By default an agent proposes and a person approves. The rules that check, gate, score and escalate are code, not AI: turn AI off and every escalation, gate, score and diagnostic still runs, and every nudge but the one that needs a model.

5.2 AI credits. Every plan includes AI credits each month. A credit is one US cent of AI model cost, at the provider's price. Credits renew each month, and unused ones do not carry over. A workspace's owners can buy extra credits, which last twelve months. When the credits run out, AI features pause until the month renews or an owner buys more. We never charge you for AI use beyond the credits you have.

5.3 Your own key. If your workspace, or a person in it, uses their own key for an AI provider, what is sent to that provider is governed by your agreement with them, and they bill you directly. We are not responsible for their service.

5.4 Check what it says. AI output can be wrong, incomplete or out of date. Read a proposal before you approve it. The decisions you make with OKRGoal are yours.

5.5 No training. We do not use your content to train AI models, and the providers behind the AI credits in our plans do not train on it under their terms.

6. Your content

6.1 It is yours. "Your content" means everything you and your members put into OKRGoal: objectives, key results, check-ins, KPIs, documents, files and comments, and what comes in from chat apps and connected agents. You keep every right you have in it.

6.2 What you let us do with it. You give us permission to store, copy, process, display and transmit your content only as needed to run OKRGoal for you, to support you when you ask, to keep the service secure, and to comply with the law. The permission ends when your content is deleted.

6.3 Who can see it. Your content is visible to the people your workspace's permissions allow. We cannot open your workspace through the product unless a workspace administrator grants a support session. The request names the person and the reason. A session lasts four hours by default and twenty-four at most, and while it lasts a banner on every screen says who is in. There is no back door in the product. Direct access to the service's database is limited to the people who operate it.

6.4 When the law requires it. If a court or authority legally requires us to disclose your content, we tell you first unless the law forbids it, and we disclose no more than we must.

6.5 Personal data. Where your content includes personal data, we process it for you under the data processing agreement, which forms part of these terms.

6.6 Export. You can export the whole workspace whenever you like, to an encrypted, checksummed archive, sealed with a passphrase you choose, that any OpenOKR instance, cloud or self-hosted, can import. Keys, connections and the audit trail stay out of the archive, and the audit trail can be exported on its own as CSV. No notice period, no request, no fee.

6.7 Your responsibility. You are responsible for having the right to put your content into OKRGoal, and for your content and your use of it being lawful.

7. Acceptable use

Do not use OKRGoal to:

• break the law, or harass, deceive or harm anyone;
• upload malware, or content you have no right to share;
• reach another workspace's data, get around a permission, a seat limit or an AI cap, or interfere with the audit log;
• send messages through its email or chat channels to people who have not agreed to receive them;
• overload the service, or call the API or scrape it in a way that harms other customers;
• resell access to OKRGoal itself without our written agreement. You may run OpenOKR yourself and offer it to others under its licence.

Security research. We welcome research done in good faith. Test only your own workspace, do not touch other customers' data or slow the service down, and report what you find to us privately through the contact page, never in a public issue. We will not take action against research that follows these rules.

If someone breaks this section, we may remove the content involved or suspend the account, as section 12 describes.

8. Services you connect

OKRGoal can connect to services others run: Slack, Microsoft Teams, WhatsApp, Telegram, your single sign-on provider, an AI provider on your own key, and AI agents your members connect over MCP, such as Claude, ChatGPT or Cursor. When you connect one, you instruct us to send and receive what it needs to work. Your agreements with those providers govern their services, and we are not responsible for them.

An agent you connect works as you, within your permissions. What it does in OKRGoal counts as what you did. You can withdraw its access at any time.

9. What we promise

• We run OKRGoal with reasonable care and skill.
• We protect it with the measures described on our security page, and we will not materially weaken them during a period you have paid for.
• We back it up, and prove the backups restore.
• We apply new releases, and the release notes say what changed.
• We keep your workspace's data in the European Union, in Frankfurt, Germany.
• We give support at the level your plan includes.

These terms do not promise an uptime figure. If your organisation needs one, it belongs in a signed agreement. We announce planned maintenance in advance where we can.

OKRGoal changes as OpenOKR develops. If we remove a major feature during a period you have paid for, you may cancel, and we refund the part of the period you have not used.

10. Confidentiality

Each of us will keep the other's confidential information confidential, use it only for the purposes of these terms, and share it only with people who need it and are bound to keep it confidential. Your content is your confidential information. This section does not cover information that is public through no fault of the one receiving it, that they already knew, that they received from someone free to share it, or that the law requires them to disclose. In the last case, they tell the other first where the law allows.

11. Feedback and contributions

If you send us ideas or suggestions, we may use them without owing you anything. Contributions to OpenOKR's code or documents are made under the project's licence and contribution rules on GitHub, not these terms.

12. Ending

12.1 You can leave at any time. Close your workspace, or cancel a paid plan, whenever you like. A paid plan stays active until the end of the period you have paid for.

12.2 When we may suspend or close an account. If you seriously or repeatedly break these terms, if a payment stays unpaid as section 4.7 describes, or if the law requires it. Unless there is an urgent risk to the service, to other customers or under the law, we tell you first, and give you a reasonable chance to put it right and to export your content.

12.3 After a workspace is closed. We keep its content for 30 days, so a mistake can be undone, then delete it. Copies in backups are deleted as the backups expire, within a further 30 days.

12.4 If OKRGoal ever closes. We will tell you at least 90 days before, refund fees paid for any time after it closes, and keep export open until the last day. You keep the code and the signed release, so you can run the same software yourself with nothing lost.

12.5 What carries on. Sections 10, 13, 14, 15 and 17 continue after these terms end.

13. Warranties

We provide OKRGoal with the care section 9 describes. Beyond that, and as far as the law allows, it is provided as it is, and we make no other promises, express or implied, including that it will be uninterrupted, free of errors, or fit for a particular purpose. If you are a consumer, nothing in these terms takes away rights the law gives you that cannot be excluded.

14. Liability

14.1 Nothing in these terms limits liability that the law does not allow to be limited, such as liability for death or personal injury caused by negligence, or for fraud.

14.2 Neither of us is liable to the other for loss of profit, revenue, business, goodwill or anticipated savings, or for any indirect or consequential loss.

14.3 Otherwise, each party's total liability under or in connection with these terms, in any twelve months, is limited to the fees you paid for OKRGoal in the twelve months before the event that caused the claim, or US$100 if that is more.

14.4 Sections 14.2 and 14.3 do not limit your obligation to pay fees, or your obligations under section 15.

15. Claims caused by your use

If someone else brings a claim against us because of your content, or because you broke section 7 or the law, you will cover our reasonable losses and costs. In return we tell you promptly, let you control the defence, and help where it is reasonable.

16. Changes to these terms

We may update these terms. For a change that matters, we email workspace owners at least 30 days before it applies. If you do not agree, you can close your workspace before then, and we refund fees paid for any time after the change. Small changes, such as corrections, apply when they are published here. Each version shows the date it came into force.

17. General

• Law and courts. These terms are governed by the laws of Malaysia, and the courts of Kuala Lumpur decide any dispute about them, unless the law gives a consumer the right to bring a claim where they live.
• Notices. Send notices to us at hello@okrinstitute.org. We send notices to you at the email addresses of your workspace's owners.
• Events beyond control. Neither of us is responsible for a failure caused by events beyond its reasonable control.
• Transfer. You may not transfer these terms without our agreement. We may transfer them to an organisation that takes over OKRGoal, and we will tell you if we do.
• If part fails. If a court finds part of these terms unenforceable, the rest stays in force.
• No waiver. Not enforcing a right straight away does not give it up.
• The whole agreement. These terms, the data processing agreement and any order form we sign with you are the whole agreement about OKRGoal.
• Language. If these terms are translated, the English version prevails.

1. Who we are

OKR Institute (OKRI Sdn. Bhd., 111, Jalan Telawi, 59100 Kuala Lumpur, Malaysia) decides how and why the personal data this policy describes is used. In data protection law, that makes us its controller.

• Write to us about privacy: hello@okrinstitute.org
• Our data protection officer: Dirk Schmellenkamp, at hello@okrinstitute.org
• Our representative in the EU: OKR Institute Germany, Zeppelinstr. 73, 81669 Munich, Germany
• Our representative in the UK: OKR Institute, Golden Cross House, 8 Duncannon St, London WC2N 4JF, United Kingdom

2. What this policy covers

• okrgoal.com, this website;
• OKRGoal accounts: the details we need to run the service and to bill for it;
• the live demo at demo.okrgoal.com;
• messages you send us, and the support we give.

It does not cover the content of an organisation's OKRGoal workspace: the objectives, check-ins, comments and files its members write. The organisation is the controller of that content, and we process it for them under the data processing agreement. If you are a member of a workspace, your organisation's own privacy notice explains how it uses that content, and requests about it go to them first.

Nor does it cover a self-hosted OpenOKR instance. Whoever runs one is responsible for the data in it.

3. What we collect, and why

4. AI providers

When AI features run on your plan's AI credits, the context a feature needs is sent through OpenRouter, named in our subprocessors list, to the model provider that runs the feature, and the answer comes back. Your workspace's admins choose what context may be sent, and can have email addresses and phone numbers redacted before anything leaves. We route only to model providers whose terms do not allow them to train on what we send, and we do not train models on it ourselves.

When your workspace uses its own AI key, the provider is your organisation's choice, and that provider's terms apply.

5. This website

• No advertising trackers.
• Analytics only if you accept performance cookies. Then Google Tag Manager loads Google Analytics, which records the pages you visit, how you arrived, and your device, browser and approximate location, and sends them to Google under its own privacy policy. The cookie policy lists the cookies it sets.
• Your browser keeps three small settings on your device: your light or dark theme, whether you closed the announcement bar, and your cookie choices. It also keeps the GitHub figures shown in the header for an hour, so they are not fetched on every page. None of this is sent to us. The cookie policy lists each one.
• To draw the pages, your browser fetches fonts from Google Fonts, and the star count and latest release from GitHub. Those requests send your IP address to Google and to GitHub, under their own privacy policies.
• Our host, Cloudflare, handles each request, including your IP address, to serve the site and protect it from attacks, under its own privacy policy.
• The contact form puts your message into an email from your own mail program, addressed to us. We receive it like any other email.

6. The live demo

The demo at demo.okrgoal.com needs no account. Everyone who opens it shares the same invented company, so other visitors can see what you type, and it is wiped when the demo resets. Do not enter real personal or confidential information. Our servers keep the same technical logs as for OKRGoal.

7. Who we share it with

• Subprocessors, the companies that help us run OKRGoal, each listed with what it does and where on our subprocessors list. Each is bound by contract to use the data only for us, and to protect it.
• Professional advisers, such as lawyers, accountants and auditors, who owe us a duty of confidentiality.
• Authorities, when the law requires it. We disclose no more than we must, and tell the person affected where we are allowed to.
• A buyer, if OKR Institute or OKRGoal is sold or merged. We will tell you before your data comes under a different privacy policy.

We do not sell personal data, rent it, or share it for advertising.

8. Where it is stored

OKRGoal stores its data in the European Union, in Frankfurt, Germany. Our own team works from Malaysia and other countries, and some subprocessors work from outside Europe. When personal data moves to a country whose law protects it less, we use the safeguards the law of its home country requires, such as the European Commission's standard contractual clauses for data from Europe.

9. How long we keep it

• Account details: while you have an account. When an account or a workspace is closed, they are deleted after 30 days, and from backups within a further 30 days.
• Billing records: 7 years, as Malaysian tax and company law requires.
• Technical and security logs: 30 days.
• Messages to us: 2 years after the conversation ends, unless they belong to a customer's records.
• Product news: until you unsubscribe.

10. Your rights

Depending on where you live, you can ask us to:

• tell you what personal data we hold about you, and give you a copy;
• correct it;
• delete it;
• give it to you, or to another service, in a form a machine can read;
• stop or limit using it, or object to how we use it;
• stop using it where we rely on your consent.

Write to hello@okrinstitute.org. We may need to confirm who you are first, and we reply within 21 days.

If your data is in an organisation's workspace, ask that organisation. If you write to us instead, we pass your request on. When a workspace erases a person, OKRGoal removes their personal details and keeps the authorship of their work, so the history still makes sense.

You can also complain to a data protection authority: in Malaysia, the Personal Data Protection Commissioner; in the UK, the Information Commissioner's Office; in the EU, the authority in your country. We would like the chance to put things right first.

11. Security

Workspaces are isolated inside the database, secrets are encrypted and never logged, and nobody at OKR Institute can open a workspace through the product unless a workspace administrator grants a support session. The security page describes the measures in full.

12. Children

OKRGoal is not meant for children. You must be 16 or older to have an account, and we do not knowingly collect personal data from anyone younger. If you think we have, tell us and we will delete it.

13. Changes to this policy

We publish changes here, with the date they come into force. For a change that matters, we email account holders before it applies.

1. What this policy covers

This website, okrgoal.com. Cookies are small files a website asks your browser to keep. Your browser's local storage and session storage work the same way, so this policy calls all three cookies. It does not cover OKRGoal itself or the live demo, which need essential cookies to sign you in and keep your session secure.

2. Essential: always on

These keep the site working and remember choices you made. None of them is sent to us, and none tracks you.

3. Optional: only if you accept

• Performance cookies help us see which pages are useful and where the site is slow.
• Advertising cookies would help us measure our adverts on other sites and show you relevant ones.

Until you accept a group, nothing in it runs.

Performance. Once you accept, Google Tag Manager loads Google Analytics. Google Tag Manager sets no cookie of its own. Google Analytics sets these:

If you take your consent back, Google Analytics stops at once. The cookies it already set stay until they expire, or until you delete them in your browser.

Advertising. This website uses none today. Before we add one, we will name it here, with what it sets and for how long, and ask you again.

4. Other companies

To draw the pages, your browser fetches fonts from Google Fonts and figures from GitHub, and the privacy policy explains what they receive. Neither sets a cookie on this website. Our host, Cloudflare, may set a short-lived security cookie, such as __cf_bm or cf_clearance, when it needs to tell people from automated traffic. That cookie is essential, and is used only to protect the site.

5. Your choices

Use Cookie settings, at the foot of every page or with the button below, to accept or reject each optional group. Rejecting them changes nothing about how the site works. Your browser's settings can also block or delete cookies; if you delete them, the site asks for your choices again.

Open cookie settings

6. Changes to this policy

We publish changes here, with the date they come into force. Questions go to hello@okrinstitute.org.

1. Parties and roles

This agreement is between the organisation that holds an OKRGoal workspace ("you") and OKR Institute ("we"). For the personal data in your workspace ("customer personal data"), you are the controller and we are your processor. Where you are yourself a processor for someone else, we are your subprocessor, and you confirm that your controller has approved this.

"Data protection law" means the laws on personal data that apply to the processing. Depending on where you and the people concerned are, they may include the EU General Data Protection Regulation, the UK GDPR and Data Protection Act 2018, and Malaysia's Personal Data Protection Act 2010.

Where this agreement and the terms of service differ about personal data, this agreement wins.

2. The processing

3. Your instructions

We process customer personal data only on your documented instructions. The terms of service, this agreement, and the way your owners and admins set up OKRGoal, such as the integrations, AI settings and support sessions they choose, are your instructions. If we believe an instruction breaks data protection law, we tell you. If the law requires us to process customer personal data in another way, we tell you first unless the law forbids it.

You are responsible for having a lawful basis for the personal data you put into OKRGoal, and for giving people the notices the law requires.

4. Our people

Only people who need access to run the service have it, and each of them is bound to confidentiality. We cannot open your workspace through the product unless a workspace administrator grants a support session, as section 6.3 of the terms of service describes. There is no back door in the product. Direct access to the service's database is limited to the people who operate it.

5. Security

We protect customer personal data with the technical and organisational measures in Annex 1, which are appropriate to the risk. We may improve them over time. We will not lower the overall level of protection.

6. Subprocessors

6.1 You authorise us to use subprocessors. The current ones are on our subprocessors list.

6.2 We tell you at least 30 days before a new subprocessor starts handling customer personal data, by updating the list and emailing your workspace's owners.

6.3 You may object, on reasonable data protection grounds, before the new subprocessor starts. We will then look for a reasonable alternative. If we cannot find one, you may end your use of OKRGoal, and we refund fees paid for any time after it ends.

6.4 Each subprocessor is bound by a written contract that protects customer personal data at least as well as this agreement does. We remain responsible to you for what they do.

6.5 Services your workspace connects on its own account, such as chat apps, an AI provider on your own key, your identity provider and agents your members connect, are not our subprocessors. You direct the data to them.

7. Helping you

• People's rights. OKRGoal lets you export, correct and erase a person's data yourself. Erasure removes their personal details and keeps the authorship of their work. If a request about your workspace reaches us, we pass it to you, and we do not answer it ourselves unless you ask us to.
• Assessments. We give reasonable help with data protection impact assessments, and with consulting an authority, using what this agreement and the security page describe.

8. Personal data breaches

If we become aware of a breach affecting customer personal data, we tell you without undue delay, and within 48 hours. We tell you what we know: what happened, the data and the people likely to be affected, the likely consequences, and what we are doing about it, and we keep you updated as we learn more. We take reasonable steps to contain it. Telling you is not an admission of fault.

9. At the end

Before your workspace closes, you can export all of it. After it closes, we delete customer personal data within 30 days, and from backups as they expire, within a further 30 days, unless the law requires us to keep it. We confirm the deletion in writing if you ask.

10. Showing that we comply

We make available the information you need to check that we meet this agreement: this document, the security page, the source code of the release OKRGoal runs, and written answers to your security questionnaire. Because OpenOKR is open source, your auditors can inspect and test the software itself.

If that is not enough, or an authority requires it, you may audit us at your own cost, with 30 days' notice, during business hours, no more than once a year, under a duty of confidentiality, and in a way that protects other customers' data.

11. Transfers

Customer personal data is stored in the European Union, in Frankfurt, Germany. We run OKRGoal from Malaysia, and some subprocessors work from other countries, so it may be accessed from outside Europe. When we or a subprocessor transfer it out of a country whose law restricts that, we do it on a ground that law allows. For data from the EU, that is the European Commission's standard contractual clauses, with the UK's addendum for data from the UK. Where they apply, those clauses form part of this agreement: module two, or module three where you are a processor, with their annexes completed from this agreement, and, for the clauses, the law and courts of the EU member state where you are established, or of Ireland if you are not established in the EU.

12. Liability

Liability under this agreement is subject to the limits in section 14 of the terms of service, except where data protection law does not allow them.

Annex 1: Security measures

• Isolation. Every business table carries its workspace and a row-level security policy in PostgreSQL. The application's database role cannot bypass it.
• Access control. Every read of a protected object goes through one access-aware function, and every write through one permission check, for the browser, the API, the command line, the chat apps and the agents alike. A forbidden object answers "not found".
• Sign-in. Passwords, passkeys and authenticator codes with backup codes. A second factor can be enforced for a whole workspace. Single sign-on with OIDC and SAML 2.0, and directory sync with SCIM 2.0. Session tokens are stored hashed. Rate limits on every sign-in, password reset and second-factor attempt, and a lock after repeated wrong authenticator codes. Suspended members lose access everywhere, at once.
• Agents. Built-in agents act as their own members, with access to named spaces and goals only. By default they propose and a person approves. Every step is metered, and a hard cap halts a run. External agents sign in with OAuth 2.1 and a consent screen, with short-lived tokens and refresh tokens that rotate on every use.
• AI egress. The workspace chooses what context may reach an AI provider, can redact email addresses and phone numbers, and can allow-list the hosts it may call. Retrieved content is treated as data, never as instructions.
• Secrets and transport. Provider keys, mail passwords and channel credentials are envelope-encrypted, opened only on the server, and never logged. Transport security, secure cookies, and a strict content security policy with per-response nonces.
• Input and output. Every input is validated at the boundary. Rich text is stored as structured data and rendered through an allow-list.
• Audit. Every sensitive action writes an append-only audit row in the same transaction as the change, naming who acted and through which channel. Rows are chained by hash, so a changed or deleted row shows, and the chain can be verified from the admin screen.
• Logs. Personal data is kept out of logs.
• Support access. Only through a session a workspace administrator grants, four hours by default and twenty-four at most, with a banner on every screen while it lasts. The product has no emergency override. Direct access to the service's database is limited to the people who operate it.
• Resilience. Encrypted backups, with a check that a backup would restore. Restore drills run automatically. Migrations only move forward, and an upgrade takes a backup first. A read-only freeze for maintenance and incidents.
• Development. Code scanning and dependency review on every change, a licence gate on every dependency, a pinned lockfile, and every commit signed off by its author. Every release is a signed container image with a software bill of materials, and is tested end to end.
• Organisation. Staff sign confidentiality agreements and are trained in security. Access is reviewed regularly, and removed when someone leaves. An incident response plan says who does what when something goes wrong.

Annex 2: Subprocessors

The subprocessors are those on our subprocessors list at the time of processing.

The companies that help us run OKRGoal, what each one does with customer data, and where it does it. Each is bound by a written contract to use the data only for us, and to protect it.

Not on this list

Services a workspace connects on its own account: Slack, Microsoft Teams, WhatsApp, Telegram, its single sign-on or directory provider, an AI provider on its own key, and the AI agents its members connect. The workspace chooses them and directs the data to them, so its own agreements with those providers apply.

A self-hosted OpenOKR instance uses none of the companies above.

Hearing about changes

We update this list at least 30 days before a new subprocessor starts handling customer personal data, and email workspace owners when we do. To object, follow section 6.3 of the data processing agreement.

You are welcome to write about OpenOKR and OKRGoal, build on them and teach with them. This page says when you can use the names freely, and when to ask first.

OpenOKR and OKRGoal, and their logos, are trade marks of OKR Institute. They tell people where the software and the service come from, so we look after them. The AGPL-3.0 licence gives you the code. It does not give you the names.

Without asking

• Use the names to refer to the software and the service, in articles, reviews, talks, courses, books, videos and posts.
• Say truthfully that your product works with OpenOKR, connects to OKRGoal, or is built on OpenOKR. A name like "Acme Reports for OpenOKR" is fine, as long as your own name comes first and stands out more.
• Distribute OpenOKR under its own name, unchanged or with only packaging and configuration changes.
• Say that you offer services around OpenOKR, such as "OKR consulting with OpenOKR" or "we install and support OpenOKR".
• Use the logo, unchanged, to link to okrgoal.com or to the OpenOKR repository.

Ask first

• Using either name, or something close to it, in the name of a company, product, service, domain or social account, other than in the "for OpenOKR" form above.
• Calling a changed version of OpenOKR "OpenOKR". If you changed more than packaging and configuration, give it a name of your own and say it is "based on OpenOKR".
• Offering OpenOKR to others as a hosted service under the OpenOKR name. The licence lets you run it for others, and asks you to share your changes. Call the service by your own name, such as "Acme OKR, built on OpenOKR".
• Merchandise, such as T-shirts and stickers.
• Using the logo in any other way.

Never

• Suggest that OKR Institute made, endorses, certifies or partners with you or your product, unless we have agreed to it in writing.
• Use the name OKRGoal for a service of your own, even one that runs OpenOKR. OKRGoal is the name of the service we run.
• Change the logo, recolour it, or combine it with your own mark.
• Use the names to mislead. Criticism is fine. Confusing people about who made what is not.

Writing the names

• OpenOKR: one word, with a capital O and OKR in capitals. Not "Open OKR" or "Openokr". In code and addresses, such as the GitHub repository, open-okr is fine.
• OKRGoal: one word, with OKR in capitals and a capital G. Not "OKR Goal" or "Okrgoal".
• If you mention both, say how they relate: OKRGoal is OpenOKR, run for you by OKR Institute.

This page covers OpenOKR and OKRGoal only. OKR Institute® and its certification marks, such as C-OKRP® and C-OKRL®, are not covered. Ask us before using them.

To ask, write to hello@okrinstitute.org or use the contact form. Most requests get a yes.