LENTO · PRIVACY
Lento Privacy Policy
1. Who is responsible and how to contact us
Marko Marić, publishing under the developer name mark.om, provides Lento and is responsible for personal information handled in connection with developer support and the optional testing programme.
For support, privacy questions or requests concerning your information, email mark.om.4383+lento@gmail.com.
2. Information handled by the watch face
Lento is a standalone, resource-only Watch Face Format watch face for Wear OS. It displays time and date and uses customization settings managed by the watch platform to render the selected design.
The watch face has no application permissions, executable application code, account system, advertising SDK, analytics SDK or developer-operated network service. It does not itself collect, transmit or share personal information with mark.om or third parties.
You do not need to create an account with mark.om or contact support to use Lento. There is no mark.om account to delete and no developer-held user database created by the watch face.
3. Google Play and Wear OS
Google Play and the watch operating system provide purchase, installation, updates and system services under their own terms and privacy policies. These services are separate from the watch face's own data practices. The project does not collect payment data; the watch face does not request your payment information.
See the Google Privacy Policy for information about Google's services. Your device manufacturer or other platform providers may also have policies applicable to their own services.
4. Information you voluntarily send to support
If you email us, we receive your email address, any name included in your email, message content, attachments and other details you choose to provide. These may include your watch model, Wear OS version or an order reference if relevant to your question.
We use this information to respond to your request, investigate the reported issue and, where necessary, handle related legal obligations or a specific dispute. We do not sell support correspondence or use it for advertising.
Support email is received and answered through a personal Google/Gmail account. The Lento and Lento Classic support addresses deliver to the same inbox, which the developer manages without delegated access, automatic forwarding or third-party integrations that read messages. We do not submit support correspondence to external AI tools. Google processes email content and related technical information under its Privacy Policy; Google's own service processing is separate from our choices about handling support requests.
Please share only information needed for your request. Do not send passwords, authentication codes, full payment details or unnecessary sensitive information.
Optional testing outside the app
If you apply for or join a closed test, you voluntarily provide a Google Play email address and may share device details and feedback. The developer first adds your account manually to both apps' Google Play tester lists, then marks a private sheet entry ready for one welcome email. The sheet holds email, send status and attempt time. It is not automatically synced to Play, and you must accept each app's Play opt-in yourself. This flow does not collect Google Groups membership or assigned codes.
The additional testing privacy notice explains those records, send-attempt handling and the roles of Google Play, Google Sheets, Google Apps Script, its Mail service and Gmail. The watch face's own no-collection practices remain unchanged. Test-only records follow that more specific notice, including its shorter retention ceiling. Genuine, separate ongoing ordinary support follows the support policy below; testing records are not reclassified as support simply to keep them longer.
5. Legal basis, retention and deletion
Where the General Data Protection Regulation applies, we process ordinary support correspondence under Article 6(1)(f) for our legitimate interest in answering questions and resolving reported issues. We limit this processing to information reasonably necessary for that purpose. Where necessary to establish, exercise or defend a specific legal claim, we rely on our legitimate interest in doing so. Where processing is necessary to comply with a legal obligation applicable to us, we rely on Article 6(1)(c).
We keep support correspondence only for as long as needed to handle the request or related follow-up questions, and for no more than 12 months after the support request is resolved. This ceiling is not a minimum: we delete information earlier when it is no longer needed. It covers received and sent messages, downloaded attachments, exports and any other copies or backups under our control. We retain information longer only when needed to meet a legal obligation or in connection with a specific dispute, and only for as long as that reason requires.
You may request earlier deletion by emailing the privacy contact above. We will consider your request and explain any applicable reason that prevents immediate deletion. Independent service-provider security logs, backups and retention are governed by the applicable provider's policies.
6. This support website and service providers
This website is hosted on GitHub Pages through the developer's personal GitHub account. GitHub logs and stores visitors' IP addresses for security purposes. We do not use those logs for analytics or add analytics, advertising, tracking cookies, account sign-in or contact forms to this site. GitHub describes its processing, including processing by GitHub, Inc. and GitHub B.V., in its Privacy Statement.
All public pages and design galleries are free to view before sharing an email or opting in on Play. The website does not enroll you or collect form data, and has no third-party analytics or forms. An email link opens your email app; only a message you choose to send provides information to the developer. The invitation's browser-only Copy link helper copies its public URL on request, without reading your clipboard or sending data to the developer.
Google and GitHub may process information outside the European Economic Area, including in the United States. Google describes reliance on applicable adequacy decisions, including the EU-U.S. Data Privacy Framework for covered transfers to Google LLC, and Standard Contractual Clauses where required for transfers not covered by adequacy. GitHub describes participation in the EU-U.S. Data Privacy Framework and generally relying on European Commission Standard Contractual Clauses for transfers to countries not recognized as providing adequate protection. These are the providers' published transfer arrangements.
Further information is available in Google's transfer-framework explanation and GitHub's international-transfer explanation. Google provides a contact form for requesting a copy of its Standard Contractual Clauses. Questions or requests concerning GitHub's applicable transfer safeguards can be directed to dpo@github.com.
7. Security and disclosures
We use the security controls offered by the hosting and email providers and limit access to support correspondence to what is needed to handle requests. No internet service or email transmission can be guaranteed completely secure.
We disclose support information only as needed to operate the email support service or when disclosure is necessary to comply with a legal obligation or address a specific legal dispute. This does not introduce data collection into the watch face itself.
8. Your privacy rights
Depending on the law that applies to you and the circumstances, you may request access to, correction or deletion of your personal information, restriction of processing, or a portable copy where the right to data portability applies. Contact us using the email address above.
Your right to object: Where we process your personal information on the basis of legitimate interests, you have the right to object at any time on grounds relating to your particular situation. To object, email the privacy contact above. We will stop that processing unless we demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or the processing is necessary for the establishment, exercise or defence of legal claims.
You may also raise a concern with the competent data protection authority. The European Data Protection Board provides a list of EU/EEA supervisory authorities. These rights concern information actually held about you, such as support correspondence; the watch face does not create a developer-held account or user profile.
9. Changes to this policy
We will update this page if the described data practices change and revise the date at the top. Where required, material changes will be communicated before new processing begins.