Real devices. Honest feedback.

How to join

We welcome people who can genuinely try the companion apps on an Android 7 or newer phone. A Wear OS 4 or newer watch is needed for the actual watch-face features, but is not required to try the phone companions. Describe the device you really use; do not report watch testing you have not performed. You can also forward the invitation without joining.

Contact Marko to request both apps

1. Read the testing privacy notice first. Review the voluntary intention and access terms on this page before sharing information.
2. Contact Marko directly with your Google Play email address. Request both apps for this cohort. You may include your phone or watch model and, optionally, its Android or Wear OS version. Use the Google account selected in the native Play Store app on your Android phone. Add and select that account on the phone if needed; signing in only in a browser is not enough.
3. Wait for manual access confirmation and your setup email. The developer adds your account to both apps' Google Play email tester lists, then marks the request ready for the welcome. The private email record is not automatically synced to Play lists. When sending is enabled and access is confirmed, an owner-operated script sends one welcome covering both apps. Email delivery is independent of sale dates and does not enroll you in either test.
4. If you are currently an internal tester, wait for the developer's confirmation. After confirmation of the applicable closed test, leave that app's internal test before accepting its closed opt-in. Changing tracks alone does not require reinstallation when version and signature are unchanged; contact the developer if your device reports a problem.
5. Accept both app-specific closed-test opt-ins below. Use the same eligible Google account for both opt-ins and installation. Being added to a tester list or receiving a welcome does not itself opt you in or start your individual 14-day period. Each app requires its own opt-in.
6. Check the price, then install and test on your device. Wait for the developer's free-access confirmation and check both Play listings with the eligible account during the confirmed window. If Google Play asks for payment, stop and contact support rather than paying. The phone companion includes Install or open on watch for a connected Wear OS watch. Direct Play installation onto a watch is also possible. Without a watch, test the phone UI, instructions, links and no-watch handling. With a watch, also select and try the actual face.
7. Try the features available to you and share honest private feedback. Aim to keep the companion apps installed and remain opted in to both tests for at least 14 consecutive days. You are not required to keep a watch face active throughout that period. Participation is voluntary and you can leave without penalty.

After the developer confirms that your account is on both tester lists, accept both official opt-ins:

• After approval: Lento closed opt-in
• After approval: Classic closed opt-in

The voluntary intention we ask you to express is:

I intend to keep the companion apps installed and remain opted in to both closed tests for at least 14 consecutive days. I will test what is available on my actual devices and give honest feedback. Neither watch face needs to stay active throughout the test. Participation is voluntary and I can leave at any time.

The continuous opt-in period is separate for each app and Google account. Keep the companion apps installed during the test rather than using their removal shortcut. Android removal remains available. Removing an app does not itself select Leave the program. If you have a watch, you may return to your usual active face after trying these designs. Keeping apps installed is our practical test request, not a claim of a Google-required daily usage duration or active-face requirement.

Google decides whether production access is granted. Reaching a minimum of 12 testers opted in continuously for 14 days is not automatic approval; real testing and the production-access review still matter. Phone installs alone do not demonstrate watch-face testing or guarantee production approval. We do not claim to have individual session statistics or automated proof of each person's 14 days. See Google's testing requirements.

Access for accepted testers

Both apps are paid apps with a temporary free-installation sale for accepted testers. The window is 18 October 2026, 00:00 GMT through 31 October 2026, 23:59 GMT. Do not assume free access from these dates alone. Access remains subject to developer confirmation, closed-test eligibility and the actual Play price for your account.

Wait for confirmation that both apps are ready, accept both opt-ins, and check each listing with the same Google account selected in your phone's native Play Store. If a price appears, do not pay. Contact the developer privately if there is an account, eligibility or installation problem.

The sale window concerns obtaining the apps at the confirmed free price. It is separate from the requested installed/test duration and each app's continuous opt-in period. You may need to continue testing after the sale ends; the sale dates do not shorten the requested 14 consecutive days or promise continued app availability.

Do not purchase an app in order to join this programme or expect a buy-and-refund arrangement. If Google Play asks you to pay, stop and contact Lento support or Lento Classic support for the relevant app before proceeding.

Participation is for testers aged 13 or older who meet the applicable age requirements for their Google account and the apps, using an eligible Google Play account in a country where the relevant app is available and permitted. Leaving the test is voluntary and has no penalty. Continued availability is governed by Google Play's applicable terms and policies, not a promise of permanent availability from the developer.

Testers are not charged for participating. Access is not conditional on a positive public rating or review. See the Google Play Terms of Service.

What to try

• On the phone: launch, text and artwork layout, links, instructions and handling when no watch is connected.
• Initial installation and selecting each app as your watch face.
• Opening customization and trying the available design settings.
• Time and date display, including readability in normal use.
• Always-on display (AOD), if your watch supports it and you choose to enable it.
• For Lento Classic, the Smooth and Step seconds-hand options, plus Dial marks On/Off and the corresponding numeral/date placement in active mode and AOD.

Tell us what worked, what did not and what you expected. Both positive and negative feedback are useful. These are practical things to explore, not requirements to manufacture activity or report a favourable result. Neither watch face adds in-app telemetry for the test.

Keep feedback private and useful

Use Google Play's private testing feedback option when available, or email the address for the app: Lento support or Lento Classic support. No public rating or review is required.

A short description, your phone or watch model and optional OS version are normally enough to begin. If a screenshot is useful, remove personal details and notification content first. Do not send passwords, authentication codes, payment details, identity documents or unnecessary sensitive information. We do not ask for your date of birth.

To stop participating, leave each relevant Google Play test. You may also email the developer for removal from the manual tester lists, help or deletion of records the developer controls. Asking the developer to remove an email record is separate from managing each app's Google Play opt-in. You can leave without penalty.

Additional privacy notice for optional testing

This notice covers applying for and taking part in the voluntary closed-test programme outside the apps. The watch faces themselves still do not collect or share personal data. Their separate policies remain available for Lento and Lento Classic.

Controller and contact

Marko Marić, publishing as mark.om, is responsible for the test records he handles. For testing or privacy questions, contact mark.om.4383+lento@gmail.com or mark.om.4383+lento-classic@gmail.com. Both addresses reach the developer's same Gmail inbox.

Information handled and why

We handle the Google Play email address you voluntarily submit, any name included in your correspondence, your request message, device model or OS version you choose to provide, which apps you request, test feedback, and welcome-email send-attempt status and timestamps. The developer manually adds the requested account to both apps' Google Play email tester lists. Access and participation information are handled only to the extent Google makes them available. This does not mean we can see individual app sessions or automated proof of your continuous participation. This flow does not collect Google Groups membership or assigned codes. The project does not collect payment data.

We use the minimum information needed to review requests, administer access, communicate about testing, troubleshoot reported problems and document actual test outcomes for Google's production-access review. We do not sell these records or use them for advertising. We do not submit identifiable tester records or private feedback to external AI tools. Truly non-identifying aggregate findings or technical results may be used; removing a name alone is not enough if the remaining details can identify someone.

The owner-only Testers sheet holds three fields: email address, send status and attempt time. The owner first adds your account to both Play tester lists, then marks the sheet entry ready. An owner-operated Google Apps Script, separate from this website and the apps, uses that ready entry to send one welcome when sending and access are enabled. Sending is independent of sale dates. It records an attempt before calling Google's Mail service and records acceptance when that call returns; acceptance is not proof of inbox delivery. Sent or ambiguous attempts are held against automatic repeat delivery. The script does not synchronize Play lists, verify your opt-ins, read the support inbox or feedback, or measure app usage. Real recipient records are not provided to AI tools. These records and accessible version history remain subject to the retention and deletion limits below.

Private records and correspondence

The developer manages the tester lists and the private sheet; the website does not publish participant lists or provide readers with access to those records. Welcome emails and participant feedback are handled privately. Contacting the developer does not automatically add an account to Play, opt you in or install either app.

Google still processes account and service information under its own policies. The owner-operated welcome sender is separate from the support inbox and does not read messages or attachments.

Legal basis

Where the General Data Protection Regulation applies, we rely on Article 6(1)(f) for our legitimate interests in organizing voluntary tests, providing access, troubleshooting and documenting actual test outcomes for production access. Processing is limited to what is reasonably necessary for those purposes. Participation is voluntary, and you may leave without penalty. For processing necessary to meet an applicable legal obligation, we rely on Article 6(1)(c); for information necessary to establish, exercise or defend a specific legal claim, we rely on our legitimate interest in doing so.

Retention and deletion

We retain identifiable test-only records only while needed for a pending application or active participation. We delete them earlier when no longer needed and, in any event, no later than 90 days after the earliest applicable event: withdrawal, rejection, the end of your participation or the end of that cohort. A pending application closes with its cohort if it has not already been decided. Awaiting production approval or a possible future cohort does not extend retention of old test records. A future cohort requires a new voluntary participation choice.

This ceiling covers test-related received and sent messages, application records, manual Play tester-list entries, sheet send records and accessible history, feedback, downloaded attachments, exports and other copies or backups under our control. Deletion is handled by the developer; it is not automated by the watch face or this website.

Genuine separate ongoing ordinary support follows the app policy's ceiling of 12 months after the support request is resolved, with earlier deletion when no longer needed. We do not relabel all testing correspondence as support or retain unrelated test details to extend the testing deadline. Longer retention is limited to information necessary for an applicable legal obligation or a specific legal claim, and only for as long as that reason requires.

You may request earlier deletion using either contact above. We will consider the request and explain any applicable reason preventing immediate deletion. Providers' independent account records, security logs, backups and retention follow their own policies; deleting our controlled copies cannot erase all records independently held by Google or GitHub.

Providers, website hosting and international processing

Google Play provides the manual email tester lists, test opt-in, distribution and private feedback where available. Gmail handles developer correspondence; Google Sheets, Google Apps Script and its Mail service support the owner-operated welcome-email process described above. Google processes account, content and technical information under its Privacy Policy. These service activities are separate from the watch faces' own data practices.

GitHub Pages hosts this static page and processes hosting information, including visitors' IP addresses for security. This site has no forms, third-party analytics, advertising, tracking cookies or externally embedded images or fonts. Its email link opens your email app; only a message you choose to send provides information to the developer. The invitation page uses a small browser-only helper that copies its public link when you press Copy link. It does not read your clipboard, send messages, register you, or transmit data to the developer. The visible link can also be copied manually without JavaScript. See the GitHub Privacy Statement.

Google and GitHub may process information outside the European Economic Area, including in the United States. Section 6 of the Lento policy and Lento Classic policy provides the providers' published transfer explanations and safeguard contacts. Those are the providers' arrangements, not a claim that the developer has independently signed particular transfer clauses.

We limit access and disclosure to what is needed to operate the programme and its services or handle a necessary legal obligation or specific legal claim. No internet service or email transmission can be guaranteed completely secure.

Your rights, including the right to object

Depending on applicable law and the circumstances, you may request access, correction, deletion, restriction of processing or a portable copy where portability applies. Contact either app address above. You may stop participating at any time without penalty; that choice is separate from exercising your data rights.

Your right to object: Where we rely on legitimate interests, you can object at any time on grounds relating to your particular situation. We will stop that processing unless we demonstrate compelling legitimate grounds overriding your interests, rights and freedoms, or processing is necessary for the establishment, exercise or defence of legal claims.

You may complain to the competent data protection authority. The European Data Protection Board provides a list of EU/EEA supervisory authorities. This notice concerns information actually handled for testing; it does not introduce an account system or data collection into the watch faces.

Changes to this notice

We will revise this page and its update date if testing data practices change, and communicate material changes before new processing begins where required.