LoggLogg Ltd

Privacy
Policy.

Last updated: 28 September 2026

LoggLogg is an app for local logging of time, place, and the user’s own notes or actions.

This version of LoggLogg does not create user accounts, does not use login, does not use LoggLogg cloud storage, and does not send the user’s log history to our own servers.

Network connectivity may still be used for specific functions such as obtaining or verifying trusted time or resolving geographic coordinates into a human-readable address. Using the network for these functions does not mean that the user’s complete log history is uploaded to a LoggLogg account or cloud service.

Log entries are stored locally on the user’s own device.

1. What information the app can process locally on the device

When the user uses LoggLogg, the app may process the following information locally on the user’s own device:

For time-related functions, LoggLogg may use trusted network time when available. If trusted time cannot be obtained, a log may still be created using the device’s local clock.

In that case, the individual log is marked as untrusted and the user is warned. That status remains associated with the individual log and is not changed later simply because network connectivity returns.

The user’s log history is stored locally on the user’s own device. LoggLogg Ltd does not receive this log history and does not have access to it in this version of the app.

2. How the information is used

The information is used for the core functions of the app, including:

The user’s complete log history is not sent to LoggLogg Ltd’s own servers in this version of the app.

3. Location

The app uses location in order to attach position information to log entries created by the user.

The device may determine geographic coordinates using technologies such as GPS/GNSS and operating-system location services.

A human-readable street or address may require network access for address resolution. When an address lookup is performed, the geographic coordinates required for the lookup may be provided to the relevant device, operating-system or geocoding service.

The user’s complete LoggLogg history is not sent as part of an address lookup.

Location information saved as part of a Logg is stored locally on the user’s device.

4. Data storage

Data created in the app is stored locally on the user’s own device.

LoggLogg Ltd does not maintain a server-side copy of the user’s complete LoggLogg history in this version of the app.

Users can manage and delete their locally stored records through the functions provided in the app.

5. Sharing and export

If the user actively chooses to copy, share or export information, the app may prepare text or files for that purpose.

When the user chooses to share data with another person, app or service, this happens on the user’s own initiative.

Any further processing of the information depends on the selected receiving app or service and its own privacy practices.

6. Network-assisted services

LoggLogg does not sell personal data and does not upload the user’s complete log history to LoggLogg servers.

Certain functions may use network connectivity or services provided by the device or operating system. These functions include obtaining or verifying current time information and converting geographic coordinates into a human-readable address.

For trusted-time functions, LoggLogg may make a network request to obtain or verify current time information. The user’s log entries, notes, categories and geographic coordinates are not included in the trusted-time request.

As with ordinary internet traffic, a service receiving a network request may receive technical connection information such as the device’s public IP address.

For address resolution, the geographic coordinates required for the lookup may be provided to the device’s, operating system’s or platform’s geocoding service. This is necessary to convert the coordinates into a readable address.

The user’s complete LoggLogg history, notes and categories are not sent as part of an address lookup.

iOS and Android may use different underlying operating-system or network mechanisms to perform these functions, but the purpose and privacy principles are the same on both platforms.

7. Security

Data created in the app is stored locally on the user’s own device.

The user is responsible for the security of their own device, including screen lock, device security, backup settings and protection of locally stored data.

Website contact form

The website contact form is separate from the LoggLogg mobile app.

When you voluntarily submit this website’s contact form, LoggLogg Ltd processes your name, email address, optional company or organisation, enquiry type and message in order to receive your enquiry and respond to it.

Your enquiry is sent by email through our hosting and email provider, Simply.com. It is not stored as an app Logg and does not change or give us access to the app’s locally stored log history.

To limit spam and abuse, the server uses a keyed hash derived from the requesting IP address together with short-lived request counts and timestamps.

The contact form does not save your message in a separate website database. Enquiries are handled through our email system. Normal hosting and email service logs may also contain technical connection information.

Contact enquiries are kept only for as long as reasonably necessary to respond to and handle the enquiry and any directly related follow-up.

Please do not include passwords, financial information, health information or other sensitive personal information in your message.

LoggLogg Ltd does not have access to the user’s locally stored app records. Those records are managed by the user on their own device. If you have contacted us through the website or by email and have a question about information contained in that correspondence, contact support@logglogg.com.

8. Contact

If you have any questions about this Privacy Policy, you can contact: support@logglogg.com

9. Changes

This Privacy Policy may be updated later if LoggLogg’s features or data-processing practices change, for example if server functions, user accounts, LoggLogg-hosted cloud storage or other external data processing are introduced.