Last updated: 2026-10-21
Thank you for using Typelet (the "App"). We take your privacy seriously. This Privacy Policy explains how the App handles your data.
The developer does not operate a server for your template library or provide an account-based sync service. Templates, folders, saved variables, local usage records and preferences are stored on your device. Apple processes purchases, and website requests, support correspondence and files you choose to share are handled as described below.
Typelet ships an iOS keyboard extension for quickly inserting your saved text templates. Note:
The App does not integrate any third-party SDKs (no analytics, no ads, no crash reporting).
Version 1.3’s in-app paywall offers a yearly auto-renewing subscription and a one-time non-consumable Lifetime purchase through Apple StoreKit. Existing Monthly subscriptions remain recognized for access, renewal and purchase restoration; earlier installed versions may present Monthly for purchase. Loading products, checking offer eligibility, purchasing, restoring and verifying access communicate with Apple. The app reads verified product and entitlement information, including expiration or revocation status where applicable, and keeps local access state. Apple processes payment; Typelet does not receive your payment-card details or Apple Account password. Current and supported historical purchase access depend on verified transactions, including subscription access Apple grants during a billing grace period. An introductory offer is displayed only after StoreKit confirms account eligibility and returns an applicable offer. Unknown or ineligible status does not promise a free trial. See the Typelet terms for the available plans and subscription handling.
The App is not directed at children under 13 and does not knowingly collect any information from children.
If we make material changes, we will update the date on this page and describe the changes.
Contact & Support
For privacy questions, please email captainlongevity@gmail.com.
Deleting folders through the App first moves their templates to the selected remaining folder, then deletes the folders in the same database transaction. The reachable control does not intentionally cascade-delete those templates. Deleting selected templates removes their saved text and variable definitions from the active library after a successful save. Separate insertion events contain snippet identifiers and use times; these events and aggregate usage totals are not automatically erased when their template is deleted. Saved reusable variables, preferences and recovery copies are separate from template deletion.
There is no Recently Deleted snapshot flow that promises to restore a deleted folder and all its children. A usable JSON file can restore the fields it contains; exported files, recipient copies and device backups require separate management. Device-backup recovery depends on a usable completed backup, and the developer has no library archive to retrieve.
These Typelet legal pages are served by Vercel. Opening a page sends ordinary request information, such as IP address, browser information and the requested URL, to the host for delivery and security; see Vercel's Privacy Notice. These pages contain no advertising or analytics scripts. If you email support, we receive the address and information you choose to send to answer your request. Avoid including sensitive records that are not needed for that request.
Data Management is a Pro feature. It exports readable, unencrypted JSON containing folders, templates, their variable definitions, saved reusable values and supported ordering or usage-summary fields. It is not a complete copy of detailed insertion events, every preference or unfinished form input. Review the destination and protect the file before sharing.
For current-format files, Merge adds missing identifiers and updates supported fields and folder relationships on matching records; local records absent from the file remain. Existing ordering is generally retained unless a template moves to another folder. Legacy files match folder names and template titles: identical templates are skipped, and same-title conflicts are reported without guessing which record to overwrite. Saved reusable variables match by identifier; an incoming new variable whose placeholder is already used is skipped. Validation can reject the import before records are changed.
Replace All replaces the active template and folder collection and saved reusable values after confirmation. It first requires a successful JSON safety copy in the App’s temporary directory; the system may later purge temporary files. Separate insertion-event history and unrelated preferences are not a full replacement target. Database writes and saved-variable preferences are separate operations, so they are not a single cross-store atomic backup or erase.
The storage-recovery screen validates a staging database before archiving previous local database files and activating a replacement. Archived stores may retain prior records and history. Cleanup and rollback attempts can fail, leaving staging or recovery files, and the App does not promise a timed automatic purge or guaranteed recovery from those files. A successful database change does not prove every copy was erased. Exported files and device backups remain separate. Restore Purchases restores eligible Apple entitlements, not templates.
Template and folder changes remain in the current form until the page’s Save succeeds. Custom variable configuration belongs to that template draft; dismissing the keyboard does not save or submit it. Version 1.3 keeps a failed template or folder save open for retry. Form input is not a guaranteed restart-restorable draft. Reusable values explicitly confirmed in the variable library and pinned-variable choices are saved separately in App Group preferences, even if a surrounding template edit is later canceled. Onboarding completion, sort order preferences, keyboard appearance, smart-spacing preference, review-request milestones and extension caches also use local preferences outside the main database. The keyboard cache can include saved template text, variable definitions and default values, folder labels and usage summaries; it is not a general typing history or a complete backup. Templates with unresolved required variables are not silently inserted with blank values. A JSON export does not include all those settings.