01Information used to provide a txti
Depending on the request, txti.link may process organizer-entered questions, options, recipient names and phone numbers, reply content, timestamps, delivery-handoff state, campaign lifecycle settings, and owner or account identifiers. This information is used to prepare recipient links, collect replies, show the owner dashboard, and operate the requested coordination flow.
02Private links are credentials
Owner, recipient, view, action, recap, and handoff links can grant access without a password. They are scoped for different jobs and should not be forwarded, posted publicly, included in analytics, or sent unredacted to support. Anyone with an active link may be able to use the access it grants.
03Public previews and sensitive mode
Messaging clients and crawlers may fetch and cache public preview metadata. Sensitive mode uses generic metadata and reduces exposed context, but it cannot make a public or forwarded link confidential.
04Accounts and purchases
Optional accounts may store name, email, sign-in identifiers, saved groups, templates, notification preferences, support state, and purchase history. Apple, Stripe, RevenueCat, identity providers, and messaging providers may process information required for the service you choose. txti.link does not receive payment-card numbers from the app stores.
05Logging, security, and abuse prevention
The service uses rate limits, content and URL checks, webhook verification, token redaction, and limited security logs. Logs and support notes are designed not to contain full private tokens, raw message bodies, full phone numbers, or raw provider payloads.
06Retention, export, and deletion
One-off pages expire according to their lifecycle. Owner deletion revokes private links and removes or anonymizes campaign content as the current product flow describes. Account-backed data may remain until the account or related record is deleted, and limited billing, security, suppression, or legal records may be retained when necessary.