Overview
TPxi Go is built by DisplayCache. We take your privacy seriously. This policy explains what data we collect, how we use it, and your rights.
What We Collect
Account Information: When you sign up for TPxi Go, we store your church's TouchPoint® domain, subscription status, and admin email address.
Authentication: Staff members sign in with their TouchPoint® username and password. A Personal Access Token (PAT) is created and stored locally on the user's device (browser storage, Outlook roaming settings, or device local storage). We never store your password on our servers.
Usage Data: We count how TPxi Go is used: daily totals for each church, and a summary for each staff username (how many searches, calls, emails, and texts, the last day they used it, and which app and version). Church administrators see these summaries on their dashboard. We do not record who was searched for or called.
Sync Status: The TPxi Go sync that runs in your TouchPoint® sends us a short status report after each scheduled run, about every 15 minutes. It says which version is running, whether the run worked, an overall health status (good, something to look at, or a problem), whether texting is set up, and your keyword settings and default campus and entry point. It contains no names, counts, contact details, notes or messages; the details stay in your TouchPoint®. Your administrators see it on the TPxi Go dashboard, and we use it to spot a sync that has stopped working.
Email Content: When a staff member manually logs an email interaction, the email subject and optionally the email body (up to 1,000 characters) are sent to TouchPoint®'s API and stored as a task note in your church's TouchPoint® database. This data is sent directly to TouchPoint®, not stored on our servers.
Texting: When your church turns on texting, the iPhone and Android apps send and read texts through tpxigo.com, and we keep a sign-up for each phone that gets text alerts. The texts themselves are not stored on our servers. See Texting below for the details.
What We Don't Collect
- We do not store contact data, church member information, text messages, pictures, or any TouchPoint® records on our servers
- We do not read or store emails unless a staff member explicitly clicks "Log as Received" or "Log as Sent"
- We do not track browsing history, keystrokes, or any activity outside of TPxi Go
- We do not sell or share data with anyone, other than the services listed under Third-Party Services that we use to run TPxi Go
- We do not use data for advertising, profiling, or creditworthiness purposes
How Our Proxy Works
TPxi Go uses a Cloudflare Worker as a CORS proxy between the browser extension / Outlook add-in and TouchPoint®'s REST API. This proxy:
- Forwards API requests to api.tpsdb.com with your authentication credentials
- Adds CORS headers so browser-based clients can make cross-origin requests
- Counts each request toward the usage summaries above (the staff username and the type of action, never who was looked up)
- Does not store, cache, or log the content of API requests or responses
Data Storage
- Your device: Login credentials (PAT token, TouchPoint® URL, username) are stored locally
- Cloudflare KV: Subscription records, usage counters, church settings, and text alert sign-ups for phones are stored in Cloudflare's global edge network
- TouchPoint®: All contact data, logged interactions, and notes are stored in your church's TouchPoint® database, managed by TouchPoint Software, Inc.
Browser Extension
The TPxi Go browser extension (Chrome/Edge):
- Uses
chrome.storage.syncto store your login credentials locally - Injects a content script on Gmail to detect the sender's email address for auto-lookup
- Reads the current tab title to extract the email subject when logging
- Optionally reads email body text when "Include email body" is checked
- All data is sent only to tpxigo.com (our proxy) and api.tpsdb.com (TouchPoint®'s API)
Outlook Add-in
The TPxi Go Outlook add-in:
- Stores credentials in Microsoft Office Roaming Settings (synced across Outlook clients via your Microsoft 365 account)
- Reads the currently selected email's sender information for auto-lookup
- Optionally reads email subject and body when a staff member explicitly clicks to log an interaction
- All data is sent only to tpxigo.com (our proxy) and api.tpsdb.com (TouchPoint®'s API)
Microsoft Teams App
The TPxi Go Teams app:
- Stores credentials in browser cookies and localStorage within the Teams client
- Provides the same contact search and interaction logging as the Outlook add-in
- Runs as a personal tab within Microsoft Teams, with no access to Teams messages, channels, or calls
iOS App
The TPxi Go iOS app:
- Stores credentials in the device's local storage
- Uses CallKit's Call Directory Extension to identify incoming callers (phone numbers are stored locally in a shared SQLite database, not transmitted to our servers)
- If Microsoft Teams is installed, offers Teams calling as an option alongside regular phone calls
- Tracks usage via a lightweight ping to tpxigo.com (domain, username, action type)
- On sign-out or uninstall, all locally stored credentials and caller ID data are removed
Briefs and Ask TP Go
On iPhones with iOS 26 and Apple Intelligence, TPxi Go can write a short brief about a person and answer questions about them. These features:
- Are written on the iPhone itself by Apple's on-device model. The details used for a brief and the answers it gives are not sent to TPxi Go servers
- Only use information the signed-in staff member can already see in TouchPoint®, under the same permissions as the app's contact card
- Give emergency contact and medical details only when asked, and only to staff permitted to see them on the card
- Use Siri when you ask by voice. Apple handles Siri voice requests under Apple's own privacy terms
- Can be turned off for a whole church on its TPxi Go dashboard
Android App OPEN BETA
The TPxi Go Android app is currently in open beta. Sign-up steps are on the homepage.
The app:
- Stores credentials in the device's encrypted SharedPreferences (app-private storage)
- Caches the church directory in an app-private SQLite database encrypted with SQLCipher (AES-256) using a per-device passphrase stored in the Android Keystore
- Cached data includes name, phone numbers, and member status only: no addresses, email content, giving, or sensitive data
- Exposes the directory to your phone's dialer via Android's read-only
ContactsContract.DirectoryAPI for caller ID, the same mechanism Truecaller and Hiya use. Directory entries are never written to your phone's Contacts app or synced to Google - Refreshes the directory daily in the background and can be manually refreshed from Settings
- Tracks usage via a lightweight ping to tpxigo.com (domain, username, action type)
- On sign-out or uninstall, the encrypted directory cache and credentials are wiped from the device
Texting
The iPhone and Android apps can send and read texts through your church's PoweredByText or Twilio account. Texting is off until a church administrator turns it on from the TPxi Go dashboard, and each person only sees the TouchPoint® texting groups they belong to.
- How texts travel: Texts and pictures you send, and the conversations you read, pass through tpxigo.com on their way between the app and PoweredByText or Twilio. tpxigo.com checks that you belong to the group, then passes the request on. It does not save texts, pictures, or phone numbers to disk or to a database. To avoid asking the texting service the same thing for every phone, it holds a church's recent conversations in memory for a few minutes at most
- Your church's texting keys: The TPxi Go sync in your TouchPoint® locks your PoweredByText and Twilio keys so that only tpxigo.com can unlock them. The apps never hold these keys
- Pictures: You pick a picture with the phone's own photo picker, so the app only sees the one you choose. It has no access to your camera or the rest of your photo library. Pictures are sent on to the texting service and not kept by us
- On your phone: Recent conversations are saved in the app's private storage so the inbox opens quickly. On Android they are encrypted with SQLCipher; on iPhone they are protected by iOS Data Protection. They are removed when you sign out or when your church turns texting off
Text alerts
When someone texts one of your groups, the texting service tells tpxigo.com, and we send an alert to the phones in that group through Apple (iPhone) or Google Firebase (Android).
- The PoweredByText webhook: For churches on PoweredByText, tpxigo.com adds its own webhook to the church's texting groups and keeps it working, using the church's PoweredByText connection, when a dashboard administrator asks it to and (if they leave it on) by itself when the webhook stops working. It changes only its own webhook; every other webhook on a group is sent back exactly as it was. We keep which groups were checked and whether each was right, never the other webhooks or any message
- An alert shows who sent the text (their name, or their number if TouchPoint® does not know them), the group, and the start of the message (up to 180 characters). On iPhone you can turn off showing the message in Settings; the alert then just says "New text"
- For each phone that gets alerts we keep its alert address from Apple or Google, the TouchPoint® username and person ID, its texting groups, and its alert choices (muted groups, quiet hours, time zone). This is removed when you sign out, or after 60 days without the app checking in
- To clear an alert once someone answers, we remember for one day that a conversation sent an alert. The message itself is not kept
Contact Data on Devices
For caller ID functionality, TPxi Go stores a subset of church contact data locally on the user's device:
- What is stored: Contact names, phone numbers, and member status, the minimum needed for caller identification
- What is NOT stored: Addresses, email addresses, giving/financial data, notes, family relationships, or any other sensitive information
- Also on the phone: Your Recent list (names of people you called, texted, emailed or opened in TPxi Go), the Resources your church shares with you, and, when texting is on, your recent text conversations (see Texting). Each is removed when you sign out or uninstall the app
- Access control: Users with restricted access in TouchPoint® (e.g., OrgLeadersOnly) only receive contacts for groups they lead
- Data removal: All locally synced contacts are automatically removed when the user signs out or uninstalls the app
- Device security: Contact data is protected by the device's built-in encryption (iOS Data Protection / Android file-based encryption) when the device is locked
Third-Party Services
- Cloudflare: Hosting and CORS proxy (privacy policy)
- Clerk: Dashboard authentication (privacy policy)
- Stripe: Payment processing (privacy policy)
- PoweredByText: Texting, for churches that use it with TouchPoint® (privacy policy)
- Twilio: Texting, for churches that use it with TouchPoint® (privacy policy)
- Apple Push Notification service: Text alerts on iPhone (privacy policy)
- Google Firebase Cloud Messaging: Text alerts on Android (privacy policy)
- Resend: Transactional emails (privacy policy)
- TouchPoint® Software: Church management platform (privacy policy)
Your Rights
You can:
- Sign out at any time to remove locally stored credentials, synced contacts, and saved texts, and to stop text alerts
- Request deletion of your subscription and usage data by contacting us
- Uninstall the extension, add-in, or app at any time, and all local data is removed
Church administrators can:
- Control which contact fields are visible to staff via the admin dashboard
- Restrict individual user access to specific groups (OrgLeadersOnly)
- Disable interaction logging per church
- Turn texting on or off for the whole church
- Revoke a user's TouchPoint® account to prevent future access (already-synced contacts remain on the device until the user signs out or uninstalls)
Security Incidents
If we learn that someone may have reached information they should not have, this is what we do and what you can expect from us.
What we hold
- Your church's TouchPoint® domain and name, your subscription status, plan, and dates, and the Stripe customer and subscription IDs for billing. Card details stay with Stripe; we never see them
- The email address of your dashboard owner and of any staff they add to the dashboard
- Your church's TPxi Go settings
- The usage summaries described above, including staff usernames
- A record of the emails we send to church administrators
- For churches using text alerts, each phone's alert sign-up, described under Texting
We do not hold member records, contact details, notes, giving, text messages, or TouchPoint® passwords. Sign-in tokens and texts pass through our service on their way to TouchPoint® or your texting service but are not stored by it.
What counts as an incident
Anyone reaching the information above without permission, anyone tampering with our service or proxy, or a flaw we find that could have allowed either, even when we see no sign that it was used.
What we do
- Stop it. Close the hole, replace any keys that could be affected, and keep the service safe for churches while we look.
- Find out what happened. Which information could be reached, for which churches, and for how long. If our records cannot tell us whether something was used, we say so plainly rather than assume it was not.
- Tell you. We email the dashboard owner of every church affected within 72 hours of confirming an incident. For a flaw that could have exposed information but shows no sign of use, we tell affected churches within 7 days of fixing it.
- Follow up. If we learn more after the first notice, we send it.
Every notice says what happened and when, which information was involved, what we have done about it, what we recommend you do, and who to contact. Where the law sets a shorter deadline or requires us to tell anyone else, we follow the law.
What you can do
- Report anything that looks wrong to support@tpxigo.com. We reply within one business day.
- When staff leave, remove their phone's access with the Access Audit report in TouchPoint®. Their phone can then no longer reach your church's information through TPxi Go.
- Shorten how long a sign-in lasts under Phone Sign-in on your TPxi Go dashboard.
Changes
We may update this policy as our services evolve. Significant changes will be communicated via email to registered administrators.
Contact
Questions about this policy? Email support@tpxigo.com.