Data processing agreement

Who this agreement is between

This agreement is between Fushimi AI Inc, based in Halifax, Nova Scotia, Canada (“OrgSync”, “we”, “us”) and the customer that accepted the Terms of service (“the customer”, “you”). Words the terms define, such as content and member, mean the same here.

Roles

Company personal data means personal information in the customer's content: drafts, shared sources, company files and the text read from them, company details, work profiles, goals, reviews, derived stories, story preferences, selections, seen state, likes, discussion, Home briefs and related records, as the terms define content.

Who decides. For company personal data, the customer decides what is shared and why, and OrgSync processes it on the customer's behalf. Under privacy laws that use these words, the customer is the controller and OrgSync is the processor.

What this agreement does not cover. Accounts, sign-in records, billing records and support messages are OrgSync's own. The Privacy notice covers them, not this agreement.

Processing only on your instructions

• We process company personal data only to provide, secure and support OrgSync for you, as the terms, this agreement and your members' use of OrgSync direct. These are your instructions.
• We do not sell company personal data, use it for advertising, or use it to train AI models.
• If the law requires us to process it in another way, we will tell you first, unless the law forbids that.
• If we believe an instruction breaks a privacy law, we will tell you.

Your responsibilities

• Share only personal information that you may lawfully share and that OrgSync may process as this agreement describes, and tell the people concerned what the law requires you to tell them.
• Do not share what the terms rule out: health information, government identification numbers, payment card or bank account numbers, passwords or other secrets, or information about children.
• Decide who joins your company in OrgSync and which permission profile each member has.

Confidentiality

Anyone we allow to process company personal data must keep it confidential. Our operator can technically reach stored data while running OrgSync, for example when taking or testing a recovery point. We access content only to operate, secure, recover or support OrgSync, at your request, or when the law requires it.

Security

We keep the safeguards described on our Security and data handling page at orgsync.co/security. We may change them, but not in a way that lowers the overall protection of company personal data.

Sub-processors

You allow us to use the company-content sub-processors listed below. Each receives only the information listed for its purpose. Providers for our own billing, sign-in and support records, and browser font delivery, are disclosed separately in the service provider register at orgsync.co/security. We remain responsible for processing company personal data on your behalf.

A stopped Fly.io server in the United States still holds an older copy of service data from before October 4, 2026. It does not run the current service or receive new company content. Its deletion is pending.

We will tell owners by email at least 30 days before we add or replace a sub-processor. If you object, tell us before the change takes effect. If we cannot resolve the objection, you can cancel and delete your company's content, as the terms describe.

Where data is processed

Story generation sends eligible company-readable source text, goals, reviews and work-profile changes to OpenRouter for significance assessment, summarization, grounding verification and personalization. Personalization also sends the person's permitted work profile, responsibilities, role objectives, active goals and category preferences. OrgSync checks access before sending inputs and before returning results. Private drafts and raw discussion are not story-model inputs.

Stories uses OpenRouter's global API pinned to Microsoft Azure's US endpoint, azure/us, with zero data retention required, data collection denied and no provider fallback. This does not guarantee end-to-end United States residency through OpenRouter.

Company personal data is stored in the United States. Indexing and onboarding model processing may use Azure's EU endpoint only when its US endpoint is unavailable. Stories uses the global route described above. Our operator holds encrypted backup copies of the database in Canada. The list of sub-processors gives each one's location.

This draft does not include a transfer mechanism, such as the EU standard contractual clauses. If personal information you plan to share is covered by the GDPR or the UK GDPR, contact us before you share it.

Requests from people

Members can export the company's shared knowledge, delete their own drafts and the sources they shared that are still reported information, and disconnect their AI apps themselves. Owners can correct work profiles, remove members and delete the company's content.

If someone asks us directly about company personal data, we will pass the request to your owners rather than answer it ourselves, unless the law requires us to answer. We will help you answer requests where we reasonably can.

Security breaches

If we become aware of a breach of our safeguards that affects company personal data, we will tell your owners by email without undue delay. We will say what happened, what information is involved and what we are doing about it, as far as we know, and keep you informed as we learn more.

If a breach of our safeguards creates a real risk of significant harm, we will report it to the Office of the Privacy Commissioner of Canada and tell the affected people and companies as soon as feasible.

Deletion and return

• Any member can export the company's shared knowledge as JSON or Markdown from Settings › Data at any time.
• Members can export the company files they may open in a ZIP archive from Settings › Data, or download each file from the Files page, until the company's content is deleted.
• Company exports include story discussion and source references, not every Stories table. They do not include a complete copy of generated stories, preferences, selections, seen state or likes.
• Stories and discussion follow the company-content retention rules. Deleting a parent source blocks access immediately and removes its stories and discussion during cleanup. Permitted earlier-version discussion can remain inspectable while its parent record is retained. Content-free generation and accounting receipts remain separately after content deletion.
• Deleting a source or the company stops access at once. We remove active copies, aiming to finish within 7 days. Backups that contain them expire within 30 days after that.
• When paid access ends, you have 30 days to export or restart your plan. After that we delete the company's content in the same way, so it can remain in backups for up to 67 days after paid access ends.
• A company that has never had paid access, or whose free trial ended without a plan, keeps its content until an owner deletes it. OrgSync may delete a company that has gone 90 days without paid access or a free trial, after emailing its owners at least 14 days before.
• A company deletion keeps people's accounts, membership and invitation records, and content-free usage records. The recovery journal keeps identifiers, never content, permanently, so that restoring a backup cannot bring deleted content back.
• We keep billing records and minimal audit records, without the deleted content, for as long as the law requires.

Information and questions

We will answer your reasonable written questions about how we process company personal data, and give you the information you need to show that this agreement is followed. OrgSync has no independent security certification or audit report, such as SOC 2, yet.

Liability and precedence

The limits on liability in the terms apply to this agreement. If this agreement and the terms conflict about company personal data, this agreement applies.

How long this agreement lasts

This agreement lasts as long as OrgSync processes company personal data for you, including the deletion periods above. The governing law in the terms applies to it.

Details of the processing

List of sub-processors

Contact

Questions about this agreement: support@orgsync.co (Monday to Friday, 9:00–17:00 Toronto time). Based in Halifax, Nova Scotia, Canada.