Skip to main content

Payments are not open yet. You can browse the watch faces; activation and purchase come later.

pulseface

Privacy

This policy covers the pulseface.io website and PulseFace watch faces, including Parhan Sency for Garmin and Wear OS. Operator: PulseFace.io. Questions or requests about personal data: send them through the form on the contact page.

When you buy the Garmin version on this website, we keep your email for the receipt, order data (order number, product, amount, status), and the watch code. Card and payment data are processed on the Midtrans page; we only receive the status and transaction number.

The Garmin watch face contacts our server to check its license. It sends only the watch code, the watch face version, and a disguised identifier for the watch.

The Wear OS watch face collects and sends no data at all. Purchases of the Wear OS version are processed by Google Play.

The contact form keeps your reply email and your message, plus the topic and the order number or watch code if you enter one.

This website uses Cloudflare for security and to stop spam. For that, visitor IP addresses are processed briefly.

This website only uses cookies needed for payments and security to work, with no advertising or analytics cookies.

How long we keep data. Paid orders and their payment data: 10 years from the end of the transaction year, because they must be kept for bookkeeping.

Buyer email: 2 years after the purchase, then removed from the order. Orders that were never paid: 90 days.

Data for watches that never bought: 180 days after their last report. Data for watches that bought: as long as their license exists.

Contact form messages: 1 year after the last message. Security records that contain IP addresses: at most 1 year.

Deleted data also leaves our backup copies within 14 days.

You can ask for a copy of your data, correct it, delete it, or withdraw consent through the contact form. Data that must be kept for bookkeeping stays until its retention period ends.

Security: data travels over an encrypted connection (HTTPS), and only the operator can access it.

Last updated 3 November 2026.