Teryli Systems LLC · Mobile app

Teryli App Privacy Policy

Last updated September 23, 2026

Release covered: This policy describes Teryli for iOS version 1.0.1, prepared for App Store review. Version 1.0.1 adds the AI-permission and chat controls described below, including a permission step before the Relationship Brief profile lookup, and adds Google Cloud (Gemini) as a Fred provider for real-estate partnership workspaces. Earlier versions may not include these controls; for example, earlier versions can run the profile lookup without first asking for AI-processing permission. Version 1.0.1 is not available to download until Apple approves and releases the update.

Teryli Systems LLC operates the Teryli mobile app. This policy explains how information is handled when you use the app to manage professional contacts, research providers and organizations, scan business materials, plan field work, and prepare follow-ups.

This app is intended for professional relationship and business-development work. It is not an electronic health record. Do not enter patient records, identifiable clinical information, insurance member numbers, or other sensitive health information into Fred, scans, research requests, or business-contact notes.

For privacy questions or requests, contact [email protected].

Information used by the app

Account and workspace information. We use your sign-in information, account identifier, name, email address, organization membership, role and preferences to authenticate you, provide the appropriate workspace, and control access. Google Firebase provides the app's authentication and cloud data services.

Business contacts and work records. Information you enter, import or save may include a professional's name, employer, job title, work email and telephone number; organization details; business notes and tags; follow-up tasks; and records of your professional interactions. Public-source research and Program Directory results may add information for you to review. Saved Book records and organization workspace records can be stored in Firebase. Which records you can access depends on the workspace and account permissions.

Camera images, imported photos and documents. When you choose a scan or import action, the app uses the images or files you select, including business-card fronts and backs, brochures and other professional materials. Those images can contain the printed names and contact details of other people. Camera access is used for capture. Selected images can be sent for AI reading when you permit AI processing. The app also keeps local originals, thumbnails, scan results, review drafts and source-page links to let you review or continue your work. Local document storage does not mean a page stays entirely on the device if you choose to send it for reading.

Fred conversations and profile answers. Fred uses the messages you send, relevant conversation context, the professional profile answers you choose to provide, and selected business information retrieved to answer your request. For example, a request about follow-ups can supply relevant contact and task fields; a provider search can supply your search criteria and returned Directory information. Saved chat history is stored on the device and separated by account and organization. When you resume a chat, an excerpt of that history can become context for a new AI request. Profile answers are stored with your private account profile. Historical action summaries are not permission to repeat an action.

Optional location and mileage. With your permission, location can help center the map, find nearby programs and calculate distance. You can also enter a location manually. If you start mileage tracking, the app uses location readings to estimate a trip and keeps trip details, distance and tracking state on the device. Turning off location permission or stopping tracking prevents further location collection through that feature. It does not erase trip records already saved. The current release does not enable cloud synchronization of the mileage log.

Technical and support information. The app and the services it connects to process technical information needed to operate, authenticate requests and troubleshoot failures. This can include request timing, service errors and network information such as an IP address. The app keeps a local diagnostic log with limited error and workspace context. If you contact support, we also receive the information you include in your message. Do not send passwords or sensitive health records to support.

AI processing and your choice

AI features include Fred, reading cards or brochures, professional research and follow-up drafting. Before using these features, the app asks whether you allow the relevant content to be sent for AI processing. You can decline and continue using available manual contact and record-management features. Camera or photo permission alone is not permission to send content to an AI provider.

Teryli's processing service runs on Cloudflare. AI request content may be processed by OpenAI, Anthropic, or Cloudflare Workers AI, depending on the feature and active provider configuration. Content sent can include selected scan images, your messages, relevant conversation context, professional profile answers, business-contact fields, public-source research and follow-up text needed for the requested action. These services may also process technical request information.

Relationship Brief profile lookup. In every workspace, when you build or refresh a contact's Relationship Brief, Teryli's Cloudflare service may look for the contact's public LinkedIn profile using Serper (Google search results), a search service provided by serper.dev. The search sends Serper the contact's name and, when available, the organization or program name and city. Serper returns public search results, such as profile addresses, headlines and short excerpts, which the app shows for your review. The app skips this lookup when a LinkedIn address is already on the contact's card, and runs it only after you allow AI processing.

NPI registry check. When you run a registry check on a contact in the Relationship Brief, Teryli's Cloudflare service searches the public NPPES NPI Registry, operated by the U.S. Centers for Medicare & Medicaid Services, using the contact's name and location. It then compares the registry results with the contact's details, such as street address and phone number, to judge whether a public provider record matches. The results are shown for your review; a registry match is not a license or credential verification.

Fred in real-estate partnership workspaces. When Teryli turns it on for a real-estate partnership workspace, Fred conversations in that workspace can be answered by Teryli's Fred service on Google Cloud, which uses Google's Gemini models. For each request, the app sends that service your Fred messages, Fred's earlier replies in the conversation, the business information Fred looked up for the request (for example, matching contacts, accounts, follow-up tasks or Directory results), your saved Fred profile answers (territory, business goal, and writing and follow-up preferences), and identifiers for your organization and the conversation, together with your sign-in token so the service can confirm your account and workspace. The app sends Fred content to Google Cloud only after you allow a permission request that names Google Cloud (Gemini). If that service is unavailable, the same request can be answered through Teryli's Cloudflare service and the providers listed above, which that permission also names. Fred in other workspaces, including behavioral-health workspaces, does not use Google Cloud; it uses OpenAI, Anthropic or Cloudflare Workers AI.

The permission request lists the services a request can use. If a feature would use a service that your earlier permission did not name, the app asks for your permission again before sending anything to that service. For example, the first time Fred uses Google Cloud in a real-estate partnership workspace, you are asked again even if you have already allowed AI processing.

You can withdraw AI-processing permission using the app's AI-processing control. Withdrawal stops new AI submissions through that permission gate; it does not recall requests already submitted or delete information already held by a processing service. Contact us if you want help with a deletion request relating to previously submitted content.

Review extracted information and generated text before saving or sending it. An AI-generated suggestion is not a clinical judgment or a verified statement about a person or provider.

We use Google Firebase for authentication and stored account/workspace data, and Cloudflare for application services and AI-request handling. In real-estate partnership workspaces where Teryli turns it on, Fred requests are handled by Teryli's service on Google Cloud, as described above. Organization records are available according to the workspace's permissions; an organization record and a record in your private Book are not the same thing.

Map display and place lookup use OpenStreetMap services, including map tiles and Nominatim place search. These requests can disclose the map area or location query and technical network information to those services. Opening directions in Google Maps or another navigation app passes the selected destination to that service.

If you choose to send a follow-up, export information, share a document, open a website or use another app, the selected information is passed to the recipient or service involved in that action. Their handling of information is governed by their own policies. Information already delivered to a recipient is not removed by deleting its copy in Teryli.

Storage, retention and deletion

Account, profile, Book and workspace records support your ongoing use of the service. Saved records can remain until you remove them through an available control or an account/workspace deletion process applies. Organization-controlled records can remain in the organization's workspace after your individual account is removed.

Local drafts, documents, cached records, mileage and saved Fred chats have separate storage and deletion controls. Deleting a local copy is different from deleting a cloud record or information sent to a provider. Signing out is not a request to delete all server records. Do not rely on signing out alone to erase saved chats or every copy of imported material.

Use Settings → Delete account to initiate permanent account removal. The app asks you to confirm and explains that organization-owned records may remain. If you cannot use that control, or want to request access, correction or deletion of information that is not covered by an in-app control, email [email protected]. Include enough information to identify the account and request, but do not send your password. We may need to verify your identity and determine whether a record is controlled by your organization before acting on a request.

Provider-held logs, backups and previously delivered information are separate from the app's visible records. Contact us for assistance identifying what a deletion request covers; removing a record from the app is not a promise that every external copy is immediately erased.

Your device choices

You can change camera, photo and location permissions in your device settings. You can decline AI processing, stop an active mileage session, edit or remove records where the app provides those controls, and manage saved Fred chats from the chat-history interface. Disabling a permission can make the related feature unavailable while leaving other available features usable.

Changes and contact