Tend Privacy Policy
1. Who we are
Tend is a church budget and finance app from Tend, a church tech company owned by Stephen Riggs. In this policy, "Tend," "we," and "us" means that company.
Tend helps a church see its budget, review spending, and keep ministry plans in one place. The first church using Tend in beta is Eden Church Houston. Accounts are given by invitation. The app is not a public sign-up product.
If you have questions about this draft, write to sriggs9114@gmail.com.
2. What this policy covers
This policy covers the Tend iOS app (the first store build) and the Tend web app that the iOS app wraps. It covers information we collect when a church staff member signs in and uses Tend.
It does not cover websites or services that a church connects on its own, such as Plaid, Intuit QuickBooks, Planning Center, or Ramp, except for the data those services send to Tend after the church connects them. Those services have their own privacy policies.
3. Information we collect
We collect only what we need to run Tend for the church that invited you. We do not sell this information. We do not use it for advertising.
Account and profile information
When a church invites you and you sign in, we collect:
- Your email address
- Your password (checked at sign-in; stored in hashed form by our authentication provider, not in plain text)
- Your name, if the church or you provide it
- The role the church assigns you (for example finance, ministry lead, operations, lead pastor, or a read-only role)
- Cardholder names the church links to your account, so you can see charges on "your" card
Church financial information
Depending on what the church connects, we store financial records for that church, including:
- Bank transaction data received through Plaid, such as dates, amounts, payees, memos, account names or identifiers, and cardholder names
- QuickBooks data, such as expenses, accounts, classes, and related bookkeeping records the church syncs
- Ramp card transaction data, when that feed is connected, such as dates, amounts, payees, memos, and cardholder names
- Budget areas, budget line items, and planned amounts, including edits staff make in Tend
- Category assignments, optional notes on a transaction (up to a short character limit), and "always categorize this payee this way" rules
- Review flags (for example, a charge that still needs a category, a possible duplicate, or a difference from QuickBooks)
- Sync status, such as when a source last synced and whether a sync failed
Planning Center giving and people data
When a church connects Planning Center, we may receive giving records and people records the church already keeps there. That can include names, contact details (such as email, phone, or address, if present in the church's Planning Center records), giving amounts, funds, and dates.
The Giving screen in the current web app still says "Coming soon," so this data may be stored before a full giving view ships in the app. A lawyer and the product team should confirm what is stored at the time this policy goes live, and this section should be updated if the connected fields change.
Device and sign-in information
For the first App Store build we also collect or use:
- Device push tokens, so we can send alerts when spending crosses a budget threshold the church or you have reason to be notified about
- Session tokens, stored on the device, so you stay signed in
- Standard server logs, such as IP address, app or browser type, and the time of a request, used to operate and secure the service
Face ID (or another device biometric, such as Touch ID) is used only on your device to unlock Tend after you have signed in. We do not receive or store your face or fingerprint. That data stays on the device and is handled by Apple.
Agent access keys (church admins only)
A church admin can create a read-only access key so an AI assistant the church chooses can read the same budget and transaction information that admin can already see in Tend. The key cannot change data. We store the key name, a prefix, when it was last used, and a log of requests (for example, a recent request count). The full key is shown once when it is created. If an admin shares a key with a third-party assistant, that assistant's own privacy policy also applies. The church controls when a key is created or revoked.
We do not currently ask you to upload receipt photos. Receipt upload is not part of the first store build.
We do not knowingly collect precise device location, contacts from your phone's address book, or advertising identifiers.
4. How we use this information
We use this information to:
- Sign you in and keep your session secure
- Show the church's budget, spending, and (when available) giving in the app
- Calculate weekly and monthly budget figures, including what is left this week after fixed bills are set aside
- Let authorized staff categorize transactions, edit budget plans, and review items that need attention
- Enforce role-based access, so people see what their role allows
- Send push alerts about budget thresholds, if you allow notifications
- Offer Face ID as a convenient way to unlock the app on your device
- Operate the optional read-only agent interface, if a church admin turns it on
- Diagnose sync problems and keep the service reliable and secure
- Respond to support requests you or your church send us
We do not use this information to show you third-party ads. We do not use it to track you across other companies' apps or websites.
5. How we share information
We share information only as described here.
With your church. Tend is a church workspace. Other staff at your church may see financial and, when connected, giving or people data, according to the role the church assigned them. A lead pastor, finance staff member, or admin may see more than a ministry lead or a read-only user.
With service providers that help us run Tend. We use companies that host or process data on our behalf, including:
- Our database and authentication provider (currently Supabase), which stores account and church records under access rules we configure
- Apple, for App Store distribution, push delivery, and on-device Face ID
- Hosting for the app and its API
These providers are allowed to use the data only to provide their service to us.
With connections the church chooses. If the church connects Plaid, QuickBooks, Planning Center, or Ramp, those providers send data to Tend and may receive the credentials or tokens needed to keep the connection working. We do not sell that data to them. Their use of data is also governed by their own policies and by the church's agreement with them.
With an AI assistant, only if a church admin creates a key and shares it. The assistant can then read the data that key is allowed to see. We do not send your church's data to an assistant unless the church sets that up.
If the law requires it, or to protect rights and safety. We may disclose information if we believe in good faith that we must do so to comply with the law, a valid legal request, or to protect Tend, our users, or the public.
If the business is transferred. If Tend is sold, merged, or transferred, this information may move with the product, still subject to this policy or a successor policy.
We do not sell personal information. We do not share it for cross-app or cross-site advertising.
6. Access, roles, and security
Access to church data is role-based. The church decides who is invited and what role they have. People without a role should not see church records. Technical access rules (row-level security) are used so a signed-in user only receives rows they are allowed to see.
Agent access keys are also limited: a key sees what its creator can see, and it cannot change records.
We use industry-standard measures such as encrypted connections (HTTPS), hashed passwords, and access rules in the database. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.
7. Retention
We keep account and church records for as long as the church uses Tend and the account stays active, and for a reasonable period after that if we need the records for security, legal, or bookkeeping reasons.
- A church admin can revoke an agent key. After that, the key stops working. We may keep a record that the key existed.
- If you leave the church's staff, ask your church admin to remove your access. You may also write to sriggs9114@gmail.com.
- If a church wants its Tend workspace deleted, it should write to sriggs9114@gmail.com. We will work with the church on deletion, subject to any legal retention need.
Exact retention periods should be confirmed before this policy is published.
8. Your choices
You can:
- Sign out in the app
- Turn off push notifications in iOS Settings
- Turn off Face ID for Tend in the app or in iOS Settings (you can still sign in with your email and password)
- Ask your church admin to change your role or remove your account
- Ask us for a copy, a correction, or deletion of personal information we hold about you, at sriggs9114@gmail.com
If you are in a place with additional privacy rights (for example, certain U.S. states or the European Economic Area), you may have the right to access, correct, delete, or export your information, or to object to or restrict certain uses. We will honor applicable rights. Because Tend holds church records, some requests may need to go through the church that invited you, especially when the data belongs to the church (such as its books or its donor records).
To appeal a request or ask a question, write to sriggs9114@gmail.com.
9. Children
Tend is built for church staff, not for children. It is not directed at children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has an account, write to sriggs9114@gmail.com and we will delete it.
10. International users
Records may be stored and processed in the United States. If you use Tend from another country, you understand that your information is transferred to the United States, which may have different data-protection rules than your country. Legal transfer terms, if required, should be added after lawyer review.
11. Changes to this policy
We may update this policy. If we make a material change, we will post the updated policy and change the effective date, and we may also notify the church's admin or in-app users. Continued use after an update means you accept the revised policy, to the extent the law allows.
12. Contact
Tend
Attn: Privacy
873 Wakefield Drive, Houston, TX 77018
Open items for lawyer and product review
Remove this section before publishing:
- Confirm the legal entity name and whether the publisher (Stephen Riggs, individual Apple Developer account) should be named here.
- Confirm mailing address and privacy email.
- Confirm every field stored from Plaid, QuickBooks, Planning Center, and Ramp at launch, including whether account or card numbers (full or masked) are stored.
- Confirm whether Planning Center people records include phone numbers, addresses, or membership status, and whether any of that should be treated as sensitive information (for example, religious affiliation).
- Confirm retention periods and the deletion process for a church workspace.
- Confirm whether any analytics or crash-reporting tool will be added before launch. This draft assumes none, other than ordinary server logs and whatever Apple itself collects through the App Store.
- Confirm the agent-access wording against the final API.
- Add state or international disclosures if a lawyer advises them (for example, a California notice).