Open source

Yes. Ozzie's app and core are open source under the Apache License 2.0, in a public repository at github.com/tribett/ozzie. Anyone can read the code, build the Mac app, and run it without paying. Every safety check Ozzie relies on lives in that open code, so a church running its own copy gets the same protections.

Project

Ozzie by FlockConnect, a Mac app for church staff

License

Apache License 2.0

Repository

github.com/tribett/ozzie

Published

November 14, 2026

Copyright

2026 FlockConnect

Languages

TypeScript, Rust and Swift

Runs on

macOS 14 or later on Apple Silicon

Supported

The latest commit on the main branch

Name and logo

Not covered by the license. The NOTICE file allows them only to describe where the work came from.

The Mac app, its shared core, the never-list and every safety check are in the public repository, and everything there works without a paid service. The hosted pieces are separate: the ozzie.church website and Ozzie managed, a paid service that is invite-only for now.

In the repository

The desktop app, the shared logic and its tests, the native checks that run before any request leaves the app, the small read-only server that lets another AI app on the same Mac read Ozzie's last check (off by default), and the never-list.

Hosted, not in it

Ozzie managed: accounts, setup, support, and a hosted AI route that requires zero data retention on every request. The app refuses any reply on that route that lacks the provider's zero-retention confirmation.

Without the service

Use your own AI provider, use a model on your own Mac, or use no AI at all. Every check and draft still works.

No. FlockConnect, the Church Relationship Manager, is closed source and runs as a hosted service at flockconnect.com. Ozzie is the company's open-source project. The two are separate products, and Ozzie is a standalone Mac app credited as Ozzie by FlockConnect to show who makes it.

Open an issue on GitHub before starting anything larger than a small fix, so the approach can be agreed first. Use fixed, fictional data in tests, issues and screenshots, never a real person's details. Contributions are licensed under Apache-2.0, and a change that weakens one of Ozzie's safety rules will not be merged.

The rules that are not up for change:

• Ozzie only reads Planning Center. There is no write path and no tool that sends a message.
• The names Ozzie reads never go to an AI model. Background-check facts never go to a model at all, even as placeholders.
• No scoring or ranking of people, and no labels such as "at risk".
• No generated prayers, sermons, devotionals or scripture, and nothing that speaks to a church member as if it were a pastor or a friend.
• No secrets in the repository.
• Every safety check lives in the open repository.

Before a pull request, run the checks CI runs: the type check, lint, the TypeScript tests and the native tests. A change to what Ozzie reads from Planning Center, to what is sent to a model, or to any rule above needs a second, independent review. Start at the project's issues.

Email [email protected] and keep the report out of public issues. Include what you found, how to reproduce it, and which version or commit you used, with fictional data in place of a real person's details. Ozzie is an early project maintained by a very small team, so there is no bug bounty.

Reports in these areas are especially welcome:

• any way Ozzie could change or send something in Planning Center or another church system;
• any way a name Ozzie read, a contact detail or a background-check fact could reach an AI model or another app;
• any way text inside church data, such as an email, a note or a plan title, could be followed as an instruction;
• sign-in, token storage in the macOS Keychain, and the connection between the Mac app and ozzie.church.

For FlockConnect itself, the same address applies, and the reply times are in its vulnerability disclosure policy.