1. Who operates UrakkaOS
UrakkaOS is developed and operated by Pohja Systems. For privacy questions, access requests or deletion requests, contact pohjasystems@gmail.com. This policy covers UrakkaOS and this public information website.
2. Information the system processes
Depending on the features you use and the information supplied to a project, UrakkaOS processes:
- Account information, such as an email address, user identifier and project membership or role.
- Project information, including project names, descriptions, addresses and records supplied by authorized users.
- Project files, such as field photographs, documents and other uploaded files, together with file names, MIME types, sizes, timestamps, folder and file identifiers, links and checksums.
- Measurements, work records, notes, issues and daily logs when entered into the system.
- Technical information needed to operate and troubleshoot the service, such as request timestamps, error information and infrastructure logs.
Uploaded files may contain personal information or embedded metadata. Upload only information that you are authorized to provide. The system is in development and limited testing; the categories above describe information handled when the relevant records or features are used.
3. Why information is used
Information is used to maintain project records, associate files with the correct project, check access rights, complete and verify uploads, prevent duplicate records, support project documentation and troubleshoot service problems. We do not use Google user data for advertising, and we do not sell Google user data.
4. Google Drive access and files
UrakkaOS uses Google Drive to store and manage project files. The current integration requests the Google Drive scope https://www.googleapis.com/auth/drive. This is a broad permission that allows the application to view, create, edit and delete Drive files accessible to the authorizing Google account. It is used because the integration works with an existing project folder structure.
The implemented upload workflow places a file in its configured project folder, searches for an existing upload when retrying, checks file metadata and its checksum, and links the verified Drive file to a project record. Drive access is used only for UrakkaOS functions. The broad OAuth permission does not mean this public website displays or publishes the account’s Drive contents.
Google OAuth client secrets, access tokens and refresh tokens used by the deployed integration are handled by server-side components. They are not published in this website or distributed to the normal client interface. The backend may provide a limited upload-session URL so a client can transfer the selected file; that URL must also be treated as confidential.
5. Storage and service providers
Project files are stored in the connected Google Drive account. User accounts, project records, file references and related metadata are stored in the UrakkaData Supabase project. Server-side integration credentials are stored as backend secrets. Hosting infrastructure serves this public website and supports service operation.
Google, Supabase and infrastructure providers process information as needed to deliver those services under their applicable terms and policies. This can involve processing in locations supported by those providers. We do not promise that every category of information stays within a particular country.
6. Sharing and human access
Project information is made available to authorized project users according to their access rights. We do not disclose Google user data to unrelated third parties. Data is shared only as needed to provide the service with user authorization, for security purposes, or when required by applicable law. Operator access to Google user data is limited to user-authorized assistance, security investigations or legal requirements.
UrakkaOS’s handling of Google API data is subject to the Google API Services User Data Policy, including its Limited Use requirements. Google user data is not used to train generalized AI or machine-learning models.
7. Retention and deletion
Project records and files are retained while needed for the project and service operation, subject to requests from the authorized account or project owner and any applicable legal obligations. There is no automatic short retention period promised for all project data.
To request access, correction or deletion, contact Pohja Systems. We may need to verify your authority over the account or project. Removing a project record does not necessarily delete the corresponding Google Drive file, and revoking OAuth access does not itself delete files or records already stored. Removal of provider backups is subject to the provider’s retention processes.
8. Revoking Google access
You can revoke UrakkaOS access through your Google Account’s third-party connections settings. Revocation prevents future access using that authorization and may stop uploads or other Drive functions. For project data already stored, contact Pohja Systems or manage files directly through the account that owns them.
9. Security
UrakkaOS uses HTTPS for service connections, server-side credential storage and project access checks. No service can guarantee absolute security. Do not share passwords, OAuth tokens or upload-session URLs, and report suspected unauthorized access to the contact below.
10. This public website
This information website has no account login, advertising trackers, analytics scripts or optional tracking cookies. Hosting and network systems may process technical information needed to serve and protect the site. Links to Google or other providers lead to services governed by their own policies.
11. Changes and contact
We may update this policy as the service develops. The effective date identifies the current version. Material changes to the use of Google user data will be disclosed, and renewed consent will be requested where required before the changed use begins.
Pohja Systems
pohjasystems@gmail.com