ContactCore
ContactCore privacy
This notice explains the privacy practices specific to ContactCore, including its website service and native iPhone and iPad app.
What ContactCore does
ContactCore helps organizations receive, protect, organize, review, and act on messages submitted through approved website forms. Organization owners and administrators manage Forms, access, and configuration on the web. The iOS app is a focused companion for reviewing authorized submissions and receiving new-submission notifications.
Information handled by ContactCore
ContactCore may process account and organization access information; Form names and configuration; submitted form content such as names, email addresses, phone numbers, addresses, message text, and other fields a customer chooses to request; spam and security signals; and delivery or audit information needed to operate the service.
For example, a name or email address in a submission normally belongs to the person who sent the message, not to the signed-in ContactCore app user.
ContactCore for iOS
The app uses the Accounts web sign-in flow to authenticate an existing Life View account. It synchronizes only Forms and submissions the signed-in user is authorized to access. The app may keep a local cache so authorized content remains available while the device is temporarily offline.
When a user permits notifications, the app registers an APNs device token with ContactCore to deliver visible alerts and background notifications for synchronization. Notifications are for service activity, not advertising or marketing.
What the app does NOT do
The ContactCore app does not display ads, use behavioral tracking, use an advertising identifier, process in-app payments, or include analytics or crash-reporting SDKs in this release. Account creation and full service management happen on the web. Billing and payment terms are available in our Billing, Refunds, and Payment Disputes information.
Form and submission retention
The implemented deletion lifecycle described here applies to a ContactCore Form and its submissions; it is not a promise that every organization record is deleted on the same schedule. An inactive Form remains until an authorized Owner or Administrator manually deletes it. Submissions are automatically deleted 730 days after receipt. An authorized Owner or Administrator may instead start manual deletion by confirming the exact Form name. Requesting deletion makes the Form inactive and starts the five-day safety lock. Successful activation cancels the request; a later request starts a new five-day lock. Failed activation preserves the request and deadline. After the lock ends, an authorized Owner or Administrator must return and complete the final deletion; ContactCore does not finalize it automatically during that manual path.
Final deletion removes the Form and its submissions from ContactCore, which does not provide a way to restore them. Operational backups may temporarily retain copies; deletion does not immediately remove a record from every backup. Organization, audit, security, or legally required records may follow separate retention obligations.
Sharing and deletion
A user may share a submission only by choosing the system share action. The chosen destination’s privacy practices then apply. Authorized owners and administrators can delete submissions and manage Form deletion through the ContactCore web service.