Templit

Templit Privacy Policy

Effective date: July 24, 2026

Developer display name updated: September 11, 2026

Templit (the “App”) respects your privacy. This policy explains what information the App processes, where it is stored, and how advertising, purchases, and privacy choices work.

1. Information stored on your device

The App stores the following information locally on your device:

This information is processed to provide the App’s core features and is not transmitted to a Templit-operated server. The App does not create user accounts or synchronize templates and clips to the cloud. Android backup is disabled.

2. Clipboard access

The App does not monitor or automatically collect clipboard changes in the background.

Clipboard content is retained in the App’s local database only when you choose to save it.

3. Protection, biometric authentication, and encryption

App lock and protected-item authentication use Android’s system biometric authentication or device credentials. The App does not directly access or store fingerprints, facial images, or raw biometric data. It receives only the authentication result.

The body of a protected clip and the primary payload of a protected template are encrypted locally using AES-GCM with keys managed by Android Keystore. Titles and certain metadata required to display and sort lists may remain unencrypted on the device. Protection is intended to reduce unauthorized access within the device; it cannot protect information that you expose on an unlocked device or place on the system clipboard.

App lock and the ability to enable protection for an item are Templit Pro features. If a successful Google Play ownership check changes the entitlement from Pro to Free, app lock is disabled immediately and new protection cannot be enabled. The transition does not automatically decrypt or delete existing protected items. An item that remains protected continues to require device authentication when it is accessed.

If the number of stored templates or clips exceeds the applicable Free-plan limit, every item in that library becomes inactive until you choose which items to activate within the limit. When you activate an inactive protected item, its per-item protection and encryption are removed after final confirmation and its primary payload is stored as ordinary local data on the device. The stored item itself is not deleted during this process.

4. Advertising, analytics, crash reporting, purchases, and Google services

The App uses the following Google services for advertising, product measurement, reliability, and purchases:

For advertising, measurement, analytics, and fraud prevention, the Google Mobile Ads SDK may automatically collect or share with Google:

Google encrypts transmitted data using TLS. Google’s policies govern the detailed processing and retention of advertising data.

Google Analytics for Firebase may automatically collect app interactions, session and app-instance information, approximate location, and device or account identifiers. When a Google Play purchase occurs, it may also automatically collect an in-app purchase event containing the product ID, product name, and price. Templit sends only a fixed allowlist of custom product events with predefined low-cardinality values, such as whether an action concerned a protected item or where a Pro prompt was opened.

Firebase Crashlytics may automatically collect crash and ANR stack traces, app and device state, operating-system and app version information, installation identifiers, and related diagnostic data needed to identify and fix reliability problems.

When you start a Templit Pro purchase, Google Play processes the payment, Google account, and transaction. The App temporarily processes purchase information supplied by Google Play to check the product ID and purchase state and to acknowledge the purchase. The App does not directly collect payment card details or billing addresses, and it does not persist purchase tokens, order identifiers, or payment information on the device or send them to a Templit-operated server. Only the last verified Free or Pro entitlement state is stored locally and is updated by a later successful Google Play ownership query.

Templit does not include template or clip identifiers or content, search queries, variable names or values, custom formats, purchase tokens, or order identifiers in its custom analytics events or ad requests.

Related policies:

5. Advertising consent choices

UMP may display an advertising privacy choices form in regions where it is required.

Choosing “Do not consent” does not disable the App’s template or clip features, and the App does not delete templates or clips because of that choice. When required, the App provides a privacy entry point in Settings so that you can review or change your choices.

UMP choices apply to advertising. They do not disable the App’s Firebase Analytics product measurement or Crashlytics reliability reporting.

If a limited ad is shown, technical information such as an IP address may be used to deliver it to the device. Depending on the publisher’s configuration, limited local storage may also be used for invalid-traffic protection.

6. Android permissions and platform capabilities

The installed app package declares the following Android permissions or platform capabilities, either directly or through included Google SDK and Android components:

These declarations do not give Templit access to call contents, phone numbers, contacts, photos, the camera, the microphone, or precise location. The App does not request access to that information.

7. Retention and deletion

The App has no server account, so there is no Templit server account data to request for deletion. You can reset or delete the advertising ID in Android settings.

8. Third-party sharing and international processing

Templates and clips stored directly by the App are not provided to Google in advertising, analytics, crash-reporting, or purchase requests. The advertising, analytics, diagnostic, and purchase-processing information described in Section 4 may be transmitted to Google through Google Mobile Ads, UMP, Firebase, and Google Play and may be processed outside your country using Google’s global infrastructure.

9. Children’s privacy

The App is not designed primarily for children and does not directly collect a date of birth or age. Distributing the App to children or as a family app requires a separate review of applicable law and Google Play Families policies.

10. Changes to this policy

We may update this policy when the App’s features, SDKs, or legal requirements change. For material changes, we will update the effective date and provide notice through the App, store listing, or published policy page as appropriate.

11. Contact

For privacy questions, contact: