How we handle your information.

Technology In Ministry LLC (“TIM”, “we”, “our”) is a software and infrastructure firm based in Indianapolis, Indiana, serving mission-driven organizations — faith-based organizations and denominational bodies, women’s funds, youth organizations, foundations, and nonprofits of every kind. We build, deploy, and operate software platforms on behalf of those organizations.

For questions about this policy: company@technologyinministry.com.

This Privacy Policy describes our information practices in two distinct contexts:

1. Website visitors — anyone browsing technologyinministry.com or submitting our contact form.
2. Recipients of SMS messages we deliver on behalf of client organizations — where TIM acts as a contracted processor and the organization is the data controller. See the vendor disclosure for the canonical statement of that relationship.

This policy does not cover the websites, apps, or operations of our client organizations themselves. Those organizations publish their own privacy policies; reach out to them directly for member-data questions outside the SMS delivery context.

From website visitors. When you visit this site, our server collects standard request telemetry through Azure Application Insights — IP address, user agent, requested URLs, response times, and error traces. We use this for operational monitoring and performance work. We do not deploy third-party analytics (Google Analytics, Segment, Mixpanel, Heap, or similar) on this site.

When you submit the contact form, we receive the fields you fill out (name, email, organization, role, message) so we can respond. The submission is delivered to us by email through Azure Communication Services and is retained for the duration of any resulting engagement plus our internal records-retention window.

As a processor for client organizations. When TIM operates an SMS messaging platform on behalf of an organization, the data we handle on the organization’s behalf includes: phone numbers and any associated member metadata the organization provides; timestamped opt-in records (including the source page or workflow that captured the consent); message content authored by the organization; and the carrier delivery receipts that result from each send. We hold this data as a processor under the organization’s instructions.

We use data solely to deliver the contracted service. For website visitors, that means responding to inquiries and operating the site. For SMS recipients, that means delivering the messages the client organization has authorized, retaining the consent and delivery records required by TCPA, and operating the platform.

We do not use member data for marketing on our own behalf. We do not sell, rent, monetize, or analytically profile member data for any purpose outside the contracted service. We are contractually prohibited from doing so, and we have no business model that depends on doing so.

We share data only with the sub-processors required to deliver the service, and only to the minimum extent each one needs to perform its function:

• Microsoft Azure — application hosting, Managed Identity, secrets in Key Vault, Application Insights telemetry, and Blob/database storage. Microsoft’s Trust Center (trust.microsoft.com) is the canonical reference for its attestations.
• Azure Communication Services — email delivery for the contact form, and SMS delivery for Member Messaging campaigns. Operates inside Microsoft’s trust boundary.
• US Tier-1 wireless carriers — Verizon, AT&T, T-Mobile, and their MVNO partners — for last-mile delivery of every SMS message and the resulting carrier delivery receipt.

Beyond those sub-processors, we disclose data only when legally required (court order, subpoena, or other binding government request), and we will notify the client organization before responding unless prohibited by law.

For SMS we deliver on behalf of client organizations, we maintain a TCPA-compliant posture:

• Documented opt-in capture, with the consent timestamp and source preserved.
• Automatic STOP and HELP keyword handling on every campaign — opt-out takes effect immediately and across all current and future campaigns for that recipient.
• Message-frequency disclosure provided at the point of opt-in.
• Sender identification carried in every outgoing message.
• Enrollment in The Campaign Registry (TCR), with brand and campaign verification before any traffic reaches a carrier.

We retain SMS opt-in records, message logs, and carrier delivery receipts for a minimum of four years, the statute-of-limitations window for TCPA claims. Beyond that minimum, retention is set by the client organization’s instructions and the contracted scope of the engagement.

Contact-form submissions and email correspondence are retained for the duration of any resulting engagement plus our internal records-retention window. Application Insights telemetry is retained per Microsoft’s default retention policy for the relevant resource.

If you are an SMS recipient. The organization that authorized the message is the data controller for your contact information; data access, correction, and deletion requests should be addressed to that organization directly. We will work with the organization to honor any valid request that reaches us.

To opt out of further messages immediately, reply STOP to any message — the unsubscribe is processed automatically and across all current and future campaigns. Reply HELP for sender identification and contact information.

If you submitted a contact form on this site. Email company@technologyinministry.com to request access to, correction of, or deletion of the information you submitted.

Our platforms run on Microsoft Azure. Production authentication uses Managed Identity exclusively — there are no service credentials stored in environment variables or source control. Secrets are kept in Azure Key Vault, with access granted to Managed Identities rather than to individual humans. Data is encrypted in transit (TLS) and at rest (Azure-managed encryption keys, with customer-managed keys available for engagements that require them).

We are not a SOC 2 audited organization today. Our platforms inherit the controls of the Microsoft services they run inside, and an organizational SOC 2 attestation is on our roadmap rather than currently held. See the Compliance page for the precise current state.

Our website and the SMS platforms we operate are not directed at children under 13. We do not knowingly collect personal information from a child under 13. If you believe a child has provided information to us, contact company@technologyinministry.com and we will delete it.

We update this policy when our practices change. Material changes will be reflected in the effective date at the top of the page, and — for any change that affects how member data is handled under an active SMS engagement — communicated directly to the relevant client organization before taking effect.

Technology In Ministry, LLC
Indianapolis, Indiana
company@technologyinministry.com
(317) 752-6944