Terms of Service

These Terms of Service ("Terms") are an agreement between [COMPANY LEGAL NAME], a [STATE] [ENTITY TYPE] with its principal office at [ADDRESS] ("Missionary Lane", "we", "us"), and the church, ministry or other organization that signs up for the hosted Missionary Lane service ("the Church", "you"). They govern your use of the hosted service at missionarylane.org, its subdomains and any custom domain connected to it.

Please read them carefully. They include a limit on our liability (section 26) and rules about how disputes are resolved (section 28).

1. About these Terms #

1. 1.1 Who the customer is. Our customer is the Church, not the individual who signs up. The people your Church lets into the admin are your "Authorized Users". You are responsible for them and for everything done under your account.
2. 1.2 Who else uses the service. Visitors browse your public gallery. Givers may sign in to My missions to see their own giving (section 12.9). Visitors and givers are not parties to this agreement with us, except that section 12.9 and the Acceptable Use rules in section 9 apply to anyone who uses the service.
3. 1.3 What makes up the agreement. The agreement consists of these Terms, the plan, add-ons and prices you choose in the service or on our pricing page, our Privacy Policy, and, where it applies, our Data Processing Addendum (the "DPA"). If they conflict, the DPA controls on the protection of personal data, then these Terms, then the pricing page.
4. 1.4 Self-hosting is separate. Running Missionary Lane on your own accounts is governed by the separate Missionary Lane Self-Hosting License, not by these Terms (section 31).

2. Definitions #

3. Accounts and authority #

1. 3.1 Authority to accept. The person who creates a church on the Service, or who later accepts these Terms for it, confirms that they are at least 18 years old and have authority to bind the Church. If they do not have that authority, they are personally bound instead, and may not use the Service for the Church.
2. 3.2 Owners and roles. The person who creates a church becomes its first owner. A church must always have at least one owner. Owners manage billing and may grant the Finance capability. Admins manage settings, keys and members. Editors manage content. You decide who receives each role, and you are responsible for removing people who should no longer have access.
3. 3.3 Two-step sign-in. Every Authorized User must sign in with a password and a one-time code from an authenticator app. The Service refuses staff actions from a session that has not completed both steps. Keep passwords, authenticator devices and recovery steps secure, and reset another member's two-step sign-in only after confirming who is asking.
4. 3.4 Accurate information. Keep your church name, owner contact email and billing details accurate. We send notices about your account to the email addresses of your owners.
5. 3.5 Limits. One person may own up to [3] churches unless we agree otherwise. Each Church's web address must not imitate another organization or person.
6. 3.6 Our access. Our operator staff can see your account in an operator console, to provide support, investigate abuse, resolve billing or comply with law. Those actions are logged.

4. The Service #

1. 4.1 What we provide. During your subscription we will make the Service available to you under these Terms, including a gallery at <your-name>.missionarylane.org, and on paid plans the option to connect your own domain.
2. 4.2 Changes. We improve the Service over time and may add, change or remove features. If we remove a feature that is material to a paid plan you are on, we will give you at least [30] days' notice by email, and if the change materially reduces the value of your plan, you may cancel and receive a pro-rated refund of any prepaid fees for the remaining period.
3. 4.3 The demo. demo.missionarylane.org shows a fictional church. Its missionaries, givers and amounts are made up. Do not enter real information about real people into the demo.

5. Plans, trials, billing and usage #

1. 5.1 Plans. Plans, their prices, included missionaries, included credits, add-ons and limits are shown on our pricing page and in the admin under Billing. At the date of this draft they are: Starter, US$29 a month, up to 25 missionaries and 500 credits a month; Growing, US$59 a month, up to 75 missionaries and 1,500 credits a month; Church, US$99 a month, 200 missionaries included and 3,000 credits a month. If the pricing page and this paragraph differ, the pricing page in effect when the charge is incurred controls.
2. 5.2 Free trial. A new church starts with a 30-day free trial: up to 25 missionaries, 200 credits given once, and the features described on the pricing page. There is no pay-as-you-go during a trial; when its credits run out, AI and voice work paid with our credits stops. If you have not chosen a paid plan when the trial ends, your gallery is paused: visitors can no longer see it, and your content is kept as described in section 20. We do not charge you at the end of a trial unless you have chosen a paid plan.
3. 5.3 Subscriptions and renewal. Paid plans are billed monthly in advance through our payment processor, Stripe, and renew automatically each month until you cancel. By choosing a plan you authorize us, through Stripe, to charge the payment method on file for the plan, the add-ons you choose and the usage charges described below. Only owners can choose or change a plan.
4. 5.4 Add-ons and setup services. Add-ons, such as building venues and Giving & My missions, are monthly charges added to your subscription and are pro-rated when you start or stop them. Some add-ons are included in some plans. One-time setup services, where offered, are charged once at the price shown when you order them.
5. 5.5 Credits.
   1. (1) One credit is US$0.01 of usage on the hosted Service, priced at our published rates, which are based on the list prices of the vendors that do the work, plus 20%.
   2. (2) A paid plan's included credits renew each calendar month (UTC) and do not roll over. The trial's credits are given once.
   3. (3) Credits have no cash value, cannot be transferred or exchanged, and expire when your subscription ends.
   4. (4) Credits are used only when your Church chooses Use Missionary Lane credits. When you use your own AI and voice keys, your provider bills you directly and no credits are used (section 10.5).
   5. (5) Hosting meters (storage, gallery traffic, venue views and similar) are recorded as usage at our published rates plus 20% and draw on included credits on paid plans.
6. 5.6 Usage charges (pay as you go). On a paid plan, usage beyond your included credits is billed at our published rates, based on vendors' list prices, plus 20%, on a later invoice, itemized by kind of use. On the Church plan, each missionary above 200 adds that missionary's share of the Church's usage for the month at those rates, plus 20%. Views of the 360° building tour or 3D scan beyond an add-on's monthly allowance are billed the same way.
   1. (1) Some usage is measured from estimates rather than exact counts. For example, gallery traffic is estimated from the number of gallery, kiosk and tour visits multiplied by a typical size per visit. The methods and rates are described in our documentation. Estimated amounts are final unless they contain an obvious error.
   2. (2) Our rates are not our actual cost for your Church. They are based on vendors' published list prices, which can change, and they apply to all of your measured or estimated use, including use that our own plan with a vendor covers at no extra cost to us. We will update our rates when a vendor's list price changes and show current rates in our documentation.
7. 5.7 Monthly cap. An owner sets a monthly limit on pay-as-you-go charges (US$25 unless the owner changes it, from US$0 to US$10,000). We will not bill pay-as-you-go charges for a calendar month above the cap. When the cap is reached, AI and voice work paid with our credits pauses and the heavy venue modes fall back to the virtual hall until the next month; your gallery keeps working. The cap does not limit your base subscription, add-on prices, setup services or taxes.
8. 5.8 Taxes. Prices exclude taxes. You are responsible for sales, use, value-added and similar taxes on your purchases, other than taxes on our income. If your Church is exempt from a tax, give us a valid exemption certificate and we will apply it to future invoices where the law allows.
9. 5.9 Failed payments. If a payment fails, Stripe may retry it, your account is marked past due, and owners and admins see a notice in the admin. If your account is still past due 14 days after it was first marked past due, your gallery is paused: visitors see a message that the gallery is paused, and owners and staff can still sign in to the admin, so an owner can update the payment method. The gallery reopens when the payment succeeds. Pausing does not delete content.
10. 5.10 Cancellation. An owner can cancel at any time under Billing → Manage payment & invoices. Cancellation takes effect at the end of the current billing period, and the Service stays available until then. Usage charges incurred before the end of the period remain payable.
11. 5.11 Refunds. Except where these Terms say otherwise or the law requires, fees are non-refundable, and we do not give refunds or credits for partial months, unused credits or unused add-ons. [OPTIONAL GOODWILL REFUND POLICY.]
12. 5.12 Downgrades. If you move to a plan with a lower missionary limit, you must remove or hide missionaries to fit the new plan before you can add more.
13. 5.13 Price changes. We may change prices by giving owners at least [30] days' notice by email. A change applies from your next billing period after the notice period ends. If you do not agree, you may cancel before it takes effect.
14. 5.14 Billing questions. If you believe a charge is wrong, tell us at richard@missionarylane.org within [60] days of the invoice. We will review it in good faith and correct confirmed errors.

6. Your content #

1. 6.1 You own your content. As between you and us, the Church owns its Customer Content, including Outputs generated for it. These Terms do not give us ownership of it.
2. 6.2 Licence to us. You grant us a worldwide, non-exclusive, royalty-free licence, for the term of the agreement and the deletion period after it, to host, store, copy, process, transmit, display and adapt Customer Content, including creating Outputs from it, only as needed to provide, secure and support the Service for you, to follow your instructions and to comply with law. This includes publishing in your public gallery the content you choose to make public, and sending content to the Third-Party Services described in section 11 and our Privacy Policy.
3. 6.3 No training on your content. We do not use Customer Content to train AI models, and we do not sell it. For the AI and voice providers we choose, we use only services whose terms say they do not train on customer content, or on which we have turned that use off (section 10.6).
4. 6.4 Public content is public. Content you publish in your gallery can be seen, copied and shared by anyone, including people in countries where your missionaries serve. Photos, recordings, letter pages and other files the gallery shows are served from public web addresses so that visitors' browsers can load them (section 8.5).
5. 6.5 The missionary directory. Unless you leave it, the Service keeps one central record for each missionary you add whose kiosk is Draft or Public, and asks your staff to confirm when a kiosk matches a family already in the directory (how it works). For a kiosk you have linked, you grant us and the other churches linked to the same missionary a non-exclusive, royalty-free licence to copy, adapt and display, in their own galleries and accounts, the letters you publish for that kiosk, for as long as they stay shared; and you may display in your gallery what other churches and the missionary share through the directory, subject to their own rights. You must confirm a match only when you know it is the same family. For missionaries serving in the EU/EEA, the UK or Switzerland, nothing is shared through the directory unless the missionary has given their own consent in the missionary portal. You can leave the directory for one kiosk or for all of them at any time (the admin's Newsletters step and Settings); leaving withdraws what you shared from the other churches and removes what came in, except items your staff edited, which stay as yours. Missionary Lane is the controller of the directory, as described in our Privacy Policy section 3.11.
6. 6.6 Your responsibility for content. You are responsible for your Customer Content and for having all the rights and permissions needed to submit and publish it, including copyright in photos, letters, music and video, and the permissions described in section 7.

7. Missionaries, families and consent #

The Service exists to show information about real people, some of them children and some of them serving where being identified can be dangerous. The Church controls what is entered and published, and is responsible for doing so lawfully and with care.

1. 7.1 Consent and permission. Before you add or publish information about a missionary, you must have the missionary's permission for what you publish, and for each family member. For a child, that permission must come from the child's parent or legal guardian. Ask each missionary what is safe to show, and record their answer.
2. 7.2 Children. Family records can include children's names and birthdays. They start private: a family member, and a birthday, appear in the gallery or the birthday ticker only when an editor switches them on. Publish a child's name, photo or birthday only with a parent's permission, and publish no more than needed.
3. 7.3 Visibility settings. Each missionary has a visibility (Draft, Public, Limited or Hidden), and each field has its own switch. Phone numbers, mailing addresses, support amounts, support and visit dates, and staff notes start private. You are responsible for choosing settings that match each missionary's wishes and safety, and for checking the gallery after you change them.
4. 7.4 Requests from missionaries. If a missionary or family member asks you to correct, hide or remove information about them, you must act on the request promptly. We will help where the Service's tools are not enough.
5. 7.5 Sensitive information. Prayer requests, praises and letters can contain sensitive information, such as health conditions, family difficulties or the faith of local people. Publish such details only with the permission of the people concerned. Do not enter government identification numbers, full payment card numbers or bank login credentials anywhere in the Service.
6. 7.6 Lawful basis. Where data protection law applies to your Church, such as the GDPR or UK GDPR, your Church is the controller of missionary and giver information and must have a lawful basis, and where needed explicit consent, for the processing the Service performs on your instructions. Our DPA sets out our obligations as your processor.

8. Restricted missionaries #

1. 8.1 What Limited does. When you set a missionary to Limited, the Service shows that missionary publicly only by the alias you choose (or "A family serving in" the region) and the region. The public gallery, the API and the MCP server leave out their real name, exact place, photos, portrait, letter text and pages, family, dates, contact details, support details and place briefing. Their kiosk's web address becomes an opaque code, their map pin is placed only roughly, and they never get a field view or a Support button. AI-written words and narration are shown for them only when written under restricted rules, and earlier AI text and recordings are withdrawn when a missionary becomes Limited. Givers see them only by alias, and the public Our missions page adds their support together without names or amounts.
2. 8.2 Never in the directory. A Limited or Hidden missionary is never placed in or matched through the missionary directory (section 6.5). Making a kiosk Limited or Hidden takes it out of the directory and withdraws what your Church shared for it.
3. 8.3 Your responsibilities. Limited protects only what the Service controls. You must:
   1. (1) set a missionary to Limited before adding identifying details, and keep them Limited for as long as their safety requires;
   2. (2) choose an alias and region that do not identify them, and keep identifying words out of fields that are shown for restricted missionaries, such as the alias, region and announcements;
   3. (3) consider recording only a region, not a city, as their place, because some processing uses the recorded place (section 8.4);
   4. (4) control who in your Church has access to the admin, because staff with access see restricted missionaries' real details, and Finance members see their real names on the payments screens; and
   5. (5) never publish restricted missionaries' details anywhere else, such as in a newsletter PDF on a public kiosk, an announcement or the church's own website.
4. 8.4 Letters and the AI. By default the Service does not send a restricted missionary's letters to an AI provider: your staff type the letter's public summary, prayer requests and praises themselves. If an administrator turns on AI reading of restricted missionaries' letters in Settings, the letter's pages are sent to your AI provider, with instructions to write only alias-and-region text, and are processed by that provider under the safeguards in our Privacy Policy. No place briefing is prepared for a restricted missionary.
5. 8.5 Files. Uploaded files are kept in private storage. Visitors' browsers can load a file only while the public gallery shows it, through a link that expires after one hour. Files uploaded to a restricted missionary's record are never served to visitors, except narration recorded from text written under the restricted rules. A link already given out for a file you later withdraw can keep working for up to an hour.
6. 8.6 Anonymity is your Church's responsibility, not ours. Your Church alone decides which missionaries need protection, whether to show them at all, and what is entered and published about them. Limited and the other protections in this section are tools we provide; we do not review Customer Content, decide which missionaries are at risk, or check that anyone is anonymized, and we have no obligation to do any of these. No system can guarantee that a person cannot be identified, for example from what visitors already know, from what others publish, or from mistakes in data entry. To the extent the law allows, we are not responsible for the identification or location of, or any harm to, a missionary, their family or the people they serve that results from Customer Content, from your Church's settings or choices (including not setting a missionary to Limited), or from your Church's use of the Service, and you indemnify us for such claims under section 27.1.
7. 8.7 Reporting exposure. If you believe a restricted missionary's identity has been exposed through the Service, contact us immediately at richard@missionarylane.org and we will help you remove it as quickly as we can.

9. Acceptable use #

You and your Authorized Users, and anyone else who uses the Service, must not:

1. 9.1 publish or disclose information that could endanger a missionary, their family, local believers or colleagues, including the exact location, real identity or travel of a restricted missionary;
2. 9.2 try to identify, de-anonymize or locate a restricted missionary, or combine data from the Service with other data for that purpose;
3. 9.3 scrape, crawl, harvest or bulk-download content from galleries, the API or the MCP server, except a Church's own content through its own API keys within their limits, or ordinary search-engine indexing of public pages;
4. 9.4 get around, probe or test our security, access controls, rate limits, privacy masking or plan limits, except through a responsible-disclosure report to richard@missionarylane.org;
5. 9.5 access another church's data, or use another person's account, password, authenticator or API key;
6. 9.6 upload content that infringes others' rights, is unlawful, defamatory, harassing, sexually explicit or hateful, or contains malware;
7. 9.7 create synthetic voices, recordings or images that imitate a real person, including a missionary, without that person's written permission;
8. 9.8 use the Service to mislead givers about how gifts are used, or to solicit funds for a purpose the Church does not control;
9. 9.9 send unsolicited bulk messages through the Service or misuse the email-in address;
10. 9.10 overload the Service, or use it in a way that harms its operation for others;
11. 9.11 resell, sublicense or provide the Service to another organization, or use it to build a competing product; or
12. 9.12 use the Service in violation of law, including export control and sanctions laws (section 32.6).

We may remove content or suspend access that breaches this section, as described in section 18.

10. AI features #

1. 10.1 What the AI does. The Service uses AI models to read newsletters (titles, summaries, highlights, prayer requests, praises, verses and text), suggest profile details found in a letter, design kiosks and write narration scripts, prepare place briefings from news headlines and country facts, and read payment documents such as bank statements and cheque registers. Voice services turn narration scripts into recorded audio.
2. 10.2 Outputs can be wrong. AI output can be inaccurate, incomplete, out of date or inappropriate. It can misread a letter, a name, a date or an amount, or misjudge which news matters. You must review Outputs before you rely on them or make them public. The admin asks staff to approve prayer requests and praises before they appear, and payment-document lines are not saved until a treasurer checks and applies them.
3. 10.3 No advice. Outputs, including place briefings and travel advisories, are information to help you, not safety, security, legal, tax, financial or travel advice. Do not rely on a briefing for decisions about a missionary's safety; use the official sources it links to and your mission board's guidance.
4. 10.4 Synthetic voice and AI text. Narration is recorded with synthetic voices. The gallery labels narration "AI voice" (on the narration controls, the kiosk's listen buttons and the World Tour captions), and marks letter summaries and prayer requests that the AI read from a letter "AI-assisted summary, reviewed by the church". You are responsible for reviewing that text before it is published, and for any further disclosure the law requires in your gallery or elsewhere you use the Outputs.
5. 10.5 Your own keys or our credits. For AI and voice you may use your own provider account ("own keys") or Missionary Lane credits ("platform keys").
   1. (1) With own keys, you choose the provider and model, your agreement with that provider governs its handling of the data we send it on your instructions, and you are responsible for choosing a provider and plan suitable for personal information. For example, some providers' free tiers allow them to use submitted content to improve their products.
   2. (2) With platform keys, we choose the provider under our own agreement with it, and the costs are charged as credits.
6. 10.6 Provider terms. For platform keys we use providers whose commercial API terms say they do not train their models on content submitted through the API, or where we have opted out of such use. Our Privacy Policy lists the providers we use and links to their terms.
7. 10.7 Availability. AI features depend on Third-Party Services and may be slow, limited or unavailable. They pause when trial credits run out or when your monthly cap is reached.

11. Third-Party Services and connectors #

1. 11.1 You choose and supply them. Some features use Third-Party Services that you choose and connect by supplying credentials, such as API keys for AI and voice providers, map keys, giving-platform tokens, and DNS records for a custom domain. You authorize us to use those credentials to call those services on your behalf, as needed to provide the features you turn on.
2. 11.2 Your agreements with them. Your use of a Third-Party Service is governed by your agreement with its provider, and you are responsible for its fees and for keeping your account in good standing. We are not responsible for Third-Party Services, their availability, changes to their interfaces or their handling of data under your agreement with them.
3. 11.3 Keys. We store your keys encrypted in Supabase Vault. They are write-only from the admin and are read only by our server functions when they need to call the service. Map keys for CARTO and Google Maps are browser keys: they are served to visitors' browsers so the map can load, so you should restrict them by web address with the provider.
4. 11.4 Giving connectors are read-only. Connections to Planning Center, Breeze, Rock RMS, MinistryPlatform and Pushpay only read gifts, funds and donor names and email addresses. They never create, change, refund or move anything in your giving platform. Give each connector the least access its provider allows. Some connectors were built from vendors' public documentation and have not yet been tested against every live account; treat new connections as beta (section 14) and check the first imports.
5. 11.5 Brand import. If you ask us to import your look from your website, we fetch the public pages, stylesheets and images at the address you give. You confirm that you may use that site's logos and images.
6. 11.6 Custom domains. You are responsible for owning and keeping the domain you connect and its DNS records. We add and remove your domain with our hosting provider on your instructions.

12. Missions giving #

1. 12.1 What giving is. The Giving & My missions feature shows a Church's givers where their missions gifts went. It reads gifts from your giving platform, spreadsheets or entries you type, reads the payments your Church reports making to missionaries, and allocates gifts to payments by date. It is an information and reporting tool.
2. 12.2 We never hold or move money. Missionary Lane is not a bank, payment processor, money transmitter, escrow agent or trustee. We do not receive, hold, transfer or disburse gifts or missionary support. Gifts go to your Church through your own giving platform, and your Church pays its missionaries itself.
3. 12.3 The Church decides every payment. Givers give to your Church's missions fund. The Service never asks a giver to choose a missionary and does not accept instructions from givers about where their money goes. Your Church keeps full control and discretion over how its funds are used, including any gift a giver has asked to be used for a particular purpose. My missions describes, after the fact, which of the Church's payments a giver's money is allocated to under the method in our documentation.
4. 12.4 An allocation model, not your books. The tracing method ("Traced", "Estimated", "Pledge") is a consistent model for explaining where money went. It is not an accounting, audit or legal determination. Your Church's own books and its giving platform are the official record. If they differ from the Service, your records govern, and you should correct the data in the Service.
5. 12.5 Accuracy depends on your data. Figures are only as accurate as the gifts, funds, missions shares, payments and giver matches your Church provides and confirms. You are responsible for mapping funds, confirming each month's payments, matching givers to the right records and checking imported and AI-read data.
6. 12.6 Not tax, legal or accounting advice. The Service does not issue tax receipts or contribution statements, and My missions and Our missions are not receipts. Nothing in the Service, our documentation or our support is tax, legal or accounting advice. Ask your own adviser how giving should be described to your givers and how your missions fund keeps gifts deductible; our documentation's note on taxes lists questions to take to them.
7. 12.7 Who can see giving. Only owners and members your owners mark as Finance, signed in with two-step sign-in, can see your Church's giving records. A signed-in giver sees only their own gifts. You are responsible for granting Finance only to people who should see givers' information, and for the wording you show givers beside the Support button.
8. 12.8 Payment documents and the email-in address. Treasurers can upload or email in bank statements, cheque registers and remittances for the AI to read. Remove unrelated pages and account numbers where you can. Anyone who knows your Church's email-in address can send documents to it, so keep it private and replace it if it leaks.
9. 12.9 Terms for givers. If you sign in to My missions:
   1. (1) you use it as a supporter of the Church, which controls your giving records and is responsible for them; questions about your gifts, receipts or how the Church used them go to the Church;
   2. (2) you must be at least [13] years old, and use only an email address that is yours;
   3. (3) you are matched to gifts by your confirmed email address and, where the Church's treasurer matches you, by the treasurer's choice; if you see giving that is not yours, tell the Church;
   4. (4) the page shows the Church's allocation of your gifts, not a choice you made, and is not a receipt;
   5. (5) you can download your giving records and delete your My missions account on the My missions page; deleting it removes your sign-in and your name and email from the Church's giver record, and the Church keeps the gift amounts, without your name, for its books; and
   6. (6) section 9 (Acceptable use), section 25 (Disclaimers), section 26 (Limitation of liability) and section 28 (Disputes) apply to you, but you owe us no fees.
10. 12.10 Built-in giving (future). We plan a later phase in which givers can give in the gallery through your Church's own Stripe account. If we offer it: your Church will be the merchant of record, receive the funds directly from Stripe, and be responsible for receipts, refunds, disputes and compliance; Stripe's own terms will apply between your Church and Stripe; and Missionary Lane will still not receive or hold the funds. Additional terms will apply before you can turn it on.

13. API and MCP server #

1. 13.1 Keys. Owners and admins can create API keys for the REST API (/api/v1) and the MCP server (/mcp). Each key belongs to one Church, carries the scopes chosen when it was created, and is shown once. A Church can have up to 25 active keys. Treat keys like passwords: keep them out of browsers, public code and shared documents, and revoke any key that may have been exposed. You are responsible for everything done with your keys.
2. 13.2 Scopes and privacy. Use only the scopes you need. Keys with giving scopes reach givers' information; call giving endpoints only from a server. You must not use the API or MCP server to circumvent the Service's privacy controls, including the masking of restricted missionaries, and you must not store, combine or republish API data in a way that exposes what the gallery keeps private.
3. 13.3 Rate limits. Each key may make up to 120 requests a minute unless we tell you otherwise. We may change limits, and throttle or suspend a key that threatens the Service.
4. 13.4 Your applications and AI assistants. If you connect an application or AI assistant to the API or MCP server, it acts for your Church. Data it retrieves leaves the Service and is handled under your own arrangements with that application's provider. Writes made with a key are recorded in an audit log.
5. 13.5 Changes. We version the API. We will give at least [90] days' notice before removing or making a breaking change to a stable endpoint, except where needed for security or by law.
6. 13.6 No other licence. Apart from using the API and MCP server with your own keys under these Terms, these Terms grant no licence to our software.

14. Beta and planned features #

Features we label beta, planned or "coming soon", such as the 3D scan, some giving connectors and presets, uploaded-video streaming and built-in giving, are offered for evaluation. They may be incomplete, change, or be withdrawn without notice, they are excluded from any service commitments, and they are provided "as is". Do not rely on a beta feature for anything critical, and check its results.

15. Availability and support #

1. 15.1 Availability. We aim to keep the Service available at all times, but we do not promise uninterrupted or error-free service unless we agree a service level in writing. The Service depends on hosting, database, payment, AI, voice, map and other providers. We may carry out planned maintenance and will try to do so at quiet times.
2. 15.2 Support. Support is by email at richard@missionarylane.org and through the feedback form in the Service, during [SUPPORT HOURS]. We aim to respond within [2] business days.
3. 15.3 Feedback form. Anyone may send a bug report, idea, question or thanks through our feedback form. Do not include sensitive information about other people in feedback.

16. Security #

1. 16.1 Our part. We maintain technical and organizational security measures appropriate to the Service, described in our Privacy Policy, our security documentation and the DPA, including tenant isolation enforced in the database, required two-step sign-in for staff, encrypted storage of keys and secrets, and audit logging of sensitive actions. We will notify you of a personal data breach affecting your Customer Content as set out in the DPA.
2. 16.2 Your part. You are responsible for the security of your Authorized Users' accounts and devices, giving people the least access they need, removing people who no longer help, keeping API keys, exported files and the email-in address private, and the security of the Third-Party Service accounts you connect.
3. 16.3 Reporting. Report suspected vulnerabilities or incidents to richard@missionarylane.org. We will not take legal action against good-faith security research that follows our disclosure guidelines and avoids harm to people and data.

17. Privacy and data protection #

Our Privacy Policy explains how we handle personal information. For personal information in Customer Content and givers' records, we act as your processor or service provider: we process it only on your instructions to provide the Service. For information about your Authorized Users' accounts, billing, our website and feedback, we act as a controller. The DPA forms part of these Terms for any Church that is subject to the GDPR, the UK GDPR, the Swiss FADP or a US state privacy law that requires processor terms, or that asks for it.

18. Suspension #

1. 18.1 When we may suspend. We may suspend all or part of the Service for your Church, a user or a key, if:
   1. (1) an amount is overdue as described in section 5.9;
   2. (2) you or your users breach section 9 or section 13, or we reasonably believe that continued access threatens the safety of a missionary or anyone else, the security of the Service, or other customers;
   3. (3) we must do so to comply with law or a binding order.
2. 18.2 How. Where practicable we will notify your owners first, give you a chance to fix the problem and limit the suspension to what is needed. In an emergency involving someone's safety we may act first and notify you as soon as we can.
3. 18.3 Effect. A suspended gallery is hidden from visitors. Suspension does not delete content, and we will restore access promptly once the reason is resolved. A Church that stays suspended for more than 90 days is deleted as described in section 20.3.

19. Term and termination #

1. 19.1 Term. The agreement starts when you accept these Terms and continues until it ends under this section.
2. 19.2 By you. You may end it at any time by cancelling your subscription (section 5.10) or, during a trial, by asking us to delete your Church.
3. 19.3 By us. We may end it:
   1. (1) if you materially breach these Terms and do not fix the breach within [30] days after notice, or immediately for a breach of section 9 that endangers people;
   2. (2) on at least [60] days' notice for any other reason, in which case we will refund prepaid fees for the period after termination.
4. 19.4 What survives. Sections that by their nature should survive, including 5 (for amounts owed), 6.1, 12.4 to 12.6, 20 and 22 to 32, survive termination.

20. Data export and deletion after the agreement ends #

1. 20.1 During the agreement. You can view and change your content in the admin at any time, read it through the API, and delete missionaries, letters, files, giving connections and imports. Deleting a giving connection deletes the gifts imported through it.
2. 20.2 Export. At any time during the agreement, and during the 90 days in section 20.3, an owner can download all of your Church's data in the admin under Settings → Legal and your data: one machine-readable (JSON) file with every record we hold for your Church, and a list of its stored files with download links that work for 7 days. If an owner can't use it, ask us at richard@missionarylane.org and we will provide the export within [30] days of the request.
3. 20.3 After a trial ends or a subscription is cancelled. Your Church is suspended: your gallery is paused and your content is kept for 90 days from the day it was suspended, so that you can come back or export it. After those 90 days, or sooner if an owner asks us to delete the Church, we delete the Church and its Customer Content, including its stored files, from the live Service. This happens automatically, normally within a day and at most within [30] days, and data in backups is deleted as backups expire within a further [BACKUP RETENTION PERIOD]. We keep billing statements and security audit logs for 7 years, and acceptance records as described in our Privacy Policy, because we must keep them by law or need them for our legitimate business needs, and anonymous usage totals that do not identify anyone.
4. 20.4 Third-Party Services. Deletion in the Service does not delete data held in your Third-Party Service accounts, such as your giving platform or your own AI provider.

21. Our intellectual property #

We and our licensors own the Service, its software, design, documentation and the Missionary Lane name and marks. Subject to these Terms, we grant you a non-exclusive, non-transferable right during the agreement to use the Service for your Church's own ministry. You may use the embed script and the WordPress plugin only to show your own gallery. We reserve all rights not expressly granted.

22. Feedback #

If you send us ideas, suggestions or bug reports, we may use them without obligation to you. This does not give us any right to your Customer Content.

23. Confidentiality #

Each party will protect the other's non-public information that it receives under the agreement, using reasonable care, and use it only for the agreement. Your Customer Content, and our non-public security and product information, are confidential. This does not apply to information that is or becomes public through no fault of the receiving party, was already known to it, is independently developed, or is lawfully received from someone else. A party may disclose confidential information when required by law, after giving the other party notice where lawful and reasonable, so that it can seek protection.

24. Copyright complaints #

1. 24.1 Notices. If you believe content in the Service infringes your copyright, send a notice to our designated agent with: your signature; identification of the work; identification of the material and where it appears (for example the gallery address); your contact details; a statement that you have a good-faith belief that the use is not authorized; and a statement, under penalty of perjury, that the notice is accurate and that you are the owner or authorized to act for the owner.
2. 24.2 Designated agent. [DMCA AGENT NAME], [COMPANY LEGAL NAME], [DMCA AGENT ADDRESS], richard@missionarylane.org. [REGISTER AGENT WITH THE U.S. COPYRIGHT OFFICE.]
3. 24.3 What we do. We will remove or disable access to material identified in a valid notice, tell the Church that posted it, and process valid counter-notices as the law provides. We will terminate, in appropriate circumstances, the accounts of repeat infringers.

25. Warranties and disclaimers #

1. 25.1 Mutual. Each party confirms that it has authority to enter into the agreement.
2. 25.2 Yours. You confirm that you have the rights and permissions described in sections 6.6 and 7 for your Customer Content.
3. 25.3 Disclaimer. EXCEPT AS EXPRESSLY STATED IN THESE TERMS, THE SERVICE, OUTPUTS AND BETA FEATURES ARE PROVIDED "AS IS" AND "AS AVAILABLE". TO THE EXTENT THE LAW ALLOWS, WE DISCLAIM ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. WE DO NOT WARRANT THAT OUTPUTS WILL BE ACCURATE, THAT GIVING FIGURES WILL MATCH YOUR RECORDS, THAT THE SERVICE WILL BE UNINTERRUPTED OR ERROR-FREE, OR THAT ANY PROTECTION WILL PREVENT A PERSON FROM BEING IDENTIFIED.

26. Limitation of liability #

1. 26.1 Excluded damages. TO THE EXTENT THE LAW ALLOWS, NEITHER PARTY IS LIABLE UNDER OR IN CONNECTION WITH THE AGREEMENT FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR PUNITIVE DAMAGES, OR FOR LOST PROFITS, LOST DONATIONS, LOST DATA OR LOSS OF GOODWILL, EVEN IF ADVISED OF THEIR POSSIBILITY.
2. 26.2 Cap. TO THE EXTENT THE LAW ALLOWS, EACH PARTY'S TOTAL LIABILITY UNDER OR IN CONNECTION WITH THE AGREEMENT IS LIMITED TO THE GREATER OF (A) THE AMOUNTS YOU PAID US FOR THE SERVICE IN THE 12 MONTHS BEFORE THE EVENT GIVING RISE TO THE CLAIM AND (B) [LIABILITY FLOOR, e.g. US$100]. For givers and visitors, who pay us nothing, our total liability is limited to [LIABILITY FLOOR].
3. 26.3 Exceptions. The limits in this section do not apply to your obligation to pay fees, to either party's indemnity obligations, to a party's breach of section 23, to your breach of section 9, or to liability that cannot be limited by law, such as liability for fraud or, where applicable, gross negligence or wilful misconduct. [COUNSEL TO SET EXCEPTIONS AND ANY SUPER-CAP FOR DATA BREACHES.]

27. Indemnity #

1. 27.1 By you. You will defend us and our officers and contractors against any third-party claim arising from your Customer Content, your publication of information about missionaries or their families, your use of Third-Party Services, your giving practices or communications to givers, or your breach of these Terms, and pay the resulting damages, costs and reasonable attorneys' fees awarded or agreed in settlement. This includes any claim that a missionary, a member of their family or a person they serve was identified, located or harmed because of information your Church entered, published or did not restrict, whether or not that missionary was set to Limited (section 8.6).
2. 27.2 By us. We will defend you against any third-party claim that the Service, as we provide it and excluding Customer Content and Third-Party Services, infringes that party's intellectual property rights, and pay the resulting damages, costs and reasonable attorneys' fees awarded or agreed in settlement. If such a claim arises we may modify the Service, get you the right to keep using it, or end the affected part and refund prepaid fees for it.
3. 27.3 Process. The party seeking defence must notify the other promptly, give it control of the defence and settlement (no settlement may impose an obligation on the defended party without its consent), and cooperate reasonably.

28. Governing law and disputes #

1. 28.1 Governing law. These Terms are governed by the laws of the Commonwealth of [STATE, likely Virginia] and applicable US federal law, without regard to conflict-of-law rules. The UN Convention on Contracts for the International Sale of Goods does not apply.
2. 28.2 Talk to us first. Before starting a formal proceeding, a party must send the other a written description of the dispute and try in good faith to resolve it for [30] days.
3. 28.3 Forum. [OPTION A: Any proceeding must be brought exclusively in the state or federal courts located in [COUNTY OR CITY], [STATE], and each party consents to their jurisdiction.] [OPTION B: Binding arbitration administered by [ARBITRATION PROVIDER] under its commercial rules, seated in [CITY], [STATE], before one arbitrator, with a small-claims exception and a class-action waiver.] [COUNSEL TO CHOOSE: see reviewer memo item P2-1.]
4. 28.4 Injunctive relief. Either party may seek urgent injunctive relief in any court of competent jurisdiction to protect people's safety, confidential information or intellectual property.

29. Changes to these Terms #

We may update these Terms. We will post the new version with its date and, for a material change, email your owners at least [30] days before it takes effect. The change applies from your next billing period after it takes effect, unless it is needed sooner for legal or security reasons. If you do not agree, you may cancel before it takes effect and we will refund any prepaid fees for the period after that date. Where the law or the change requires it, we will ask an owner to accept the new version in the admin.

30. Notices #

We send notices to the email addresses of your Church's owners, or show them in the admin. You send legal notices to richard@missionarylane.org and, for notices of breach, termination or disputes, also by post or courier to [COMPANY LEGAL NAME], [ADDRESS]. Notices by email are received when sent, unless the sender receives a delivery failure.

31. Self-hosting, the desktop app and integrations #

1. 31.1 Separate license. Running Missionary Lane on your Church's own accounts, including with the desktop app, is available only by our approval and is governed by the Missionary Lane Self-Hosting License, which is shown in full, with its version and fingerprint, before you sign it at app.missionarylane.org. These Terms do not apply to a self-hosted gallery, except to your use of our hosted services that support it, such as the license check, downloads and updates, and our documentation.
2. 31.2 Consistency. The Self-Hosting License does not permit selling, hosting or operating Missionary Lane for others; nothing in these Terms changes that. If a Church uses both the hosted Service and a self-hosted gallery, each is governed by its own agreement.
3. 31.3 Integrations. The WordPress plugin and the embed script are provided so you can show your hosted gallery on your own website. Members of a hosted Church may download the plugin under these Terms. Your website and its host are your responsibility.

32. General #

1. 32.1 Entire agreement. The agreement described in section 1.3 is the entire agreement between the parties about the hosted Service and replaces earlier understandings about it. Purchase orders or other terms you send us do not apply.
2. 32.2 Assignment. Neither party may assign the agreement without the other's consent, except to a successor in a merger, acquisition or sale of substantially all of its relevant assets, with notice. We will require any successor to honour our obligations for Customer Content.
3. 32.3 Subcontractors. We may use subcontractors and sub-processors to provide the Service, as described in the Privacy Policy and DPA, and remain responsible for their performance.
4. 32.4 Force majeure. Neither party is liable for delay or failure caused by events beyond its reasonable control, such as natural disasters, war, unrest, government action, or failures of the internet or of third-party hosting, other than payment obligations.
5. 32.5 Independent parties. The parties are independent contractors. Nothing in the agreement creates a partnership, agency, fiduciary or employment relationship, or makes us part of your Church's giving or financial operations.
6. 32.6 Export and sanctions. You must not use the Service in violation of US export control or sanctions laws, or let it be used by a person or in a place where that is prohibited. You are responsible for your Church's compliance with sanctions laws in its missionary work. [COUNSEL TO REVIEW: see reviewer memo item P1-9.]
7. 32.7 No waiver; severability. Failing to enforce a term is not a waiver. If a term is unenforceable, it is modified to the minimum extent needed and the rest remains in effect.
8. 32.8 Third parties. There are no third-party beneficiaries of the agreement.
9. 32.9 Electronic agreement. You agree that these Terms may be accepted electronically and that electronic notices and records satisfy any requirement that they be in writing.
10. 32.10 Language. If these Terms are translated, the English version controls.

Contact #

[COMPANY LEGAL NAME] · [ADDRESS] · richard@missionarylane.org