This policy covers Marka, the Android app published by Nakanikuneko (space.nakanikuneko.marka.app), the Marka website and the company workspace. Local use, optional personal backup and company collection have different data flows, explained below.
Local app data
Marka stores photos, videos, stamps and capture proofs, projects, clock and break records, saved notes and addresses, identity details, logos, settings and previews in its private app storage. The mobile app can be used without a company account. Workers join companies by invitation; company users sign in to the web workspace.
A stamp and its embedded capture record can contain time, coordinates, location accuracy, notes, identity and device/app information. Review the details you include before sharing a file. A typed address can differ from the captured coordinates.
Joining a company and uploading records
An invitation preview displays company branding, the invited worker name and any company stamp rules. Joining sends the invitation, your chosen display name, an installation identity, device name, platform and app version to the company service. An invitation can connect multiple installations to the same worker record. Each installation has separate access credentials, and a company user can revoke it individually.
At joining, you choose whether to include eligible existing photos, videos, projects and timesheets, or collect future records only. Future-only collection excludes pre-join records; it does not disable automatic collection of new records. Transfers can run in the background according to your sync frequency, network preferences and available company capacity.
Collected information includes original media with its embedded stamps/proofs, filenames, capture times and locations, verification results, project associations, previews, worker/device associations and eligible clock/break records. The workspace also records upload state and relevant connection/activity times to manage devices and synchronization.
Company users can view, organize and export company-held records, see them by worker, date, project and location, and review attendance. Historical map traces connect recorded capture locations and times; they are not continuous GPS monitoring. Workers cannot browse or download colleagues' company media through their device connection.
Company rules may enforce selected stamp settings and control company-project creation. Unenforced settings remain editable; notes and saved addresses remain worker-editable. Changing a display name or organizing a project does not rewrite immutable capture facts.
Media collection is upload-only. Deleting a local file, leaving a company, uninstalling the app or having a device revoked does not remove records already collected by the company. Leaving or revocation stops future authorized collection from that connection. Reinstalling can create a new installation identity; device revocation is not a permanent hardware ban.
Timesheets and company responsibility
The company service combines eligible clock and recorded-break events for a worker, including records from multiple devices. Company users can review overlaps, make audited corrections and approve or export timesheets. Corrections and approvals are separate from original source events. Structured attendance may remain after an attached photo is deleted under media retention rules.
The company determines why it collects workers' records, who uses them and how it uses exports. It is responsible for providing appropriate workplace notices and meeting the requirements applicable to its use. Marka operates the service and processes company records to provide it. Contact your company about its collection instructions, access and use; contact us about operation of Marka or a privacy request.
Company accounts and payments
Company accounts use an email address, name, account credentials and essential session cookies. If you choose Google sign-in, Google provides the account/profile information needed to authenticate you, such as your email, name and profile image. Password credentials are stored as hashes. Account access, verification and recovery require service communications.
Paid subscriptions are processed by Paddle as merchant of record. Paddle collects payment and billing information under its own terms and privacy policy. Marka receives and stores the customer, transaction, subscription, invoice and billing-event information needed to manage your plan, payment status, support and accounting. You enter payment-card details into Paddle's checkout, not a Marka card-entry form. See Paddle's privacy policy and buyer terms.
Hosting, email and security
The website and company service use Google Cloud hosting, database and private object storage. Service operators and providers process connection information and operational/security records to deliver, protect and troubleshoot the service. Company files are access-controlled; temporary authorized download/export links can be used by anyone holding them until they expire, so do not share those links unintentionally.
Resend delivers transactional emails such as account verification, password reset, company deletion confirmation and storage/subscription notices. It receives the destination address and message content needed for delivery. Our email integration has open/click tracking disabled. See Resend's privacy policy and Google's privacy policy.
We do not include advertising or analytics SDKs in Marka. If you arrive from a Google ad, the ad click ID is kept in a cookie, then with your company account, and, if your company subscribes, made available to Google Ads with the payment amount, currency and time to measure the ad. Essential authentication cookies, service logs and company device/attendance records are still necessary for the features described here. We do not claim that every use of the service is anonymous.
Permissions and location
Camera access captures photos, videos and invitation QR codes. Microphone access records audio with videos. Location access adds capture coordinates while the camera is in use; video capture can include location samples. Marka does not continuously read background GPS to build a worker's route. Network access supports company uploads, backup and optional online services; network-state checks support Wi-Fi preferences.
The system picker lets you choose individual files, logos or an invitation QR image without granting general access to your library. Legacy storage permission is used where required to save captures on older Android versions. You can manage permissions in your device settings; denying a permission can make the corresponding feature unavailable.
Address lookup and maps
Address lookup sends coordinates to the phone's geocoding service, typically provided by Google on Android. Map displays request tiles from the configured map provider; the current public provider is OpenStreetMap. Tile requests reveal your IP address and the requested map area to that provider, but do not send it the capture file. Company maps also use locations already collected in the workspace.
See the OpenStreetMap Foundation privacy policy and tile usage policy. A provider handles its received information under its own policies.
Optional Google Drive backup
If you connect Google Drive backup, Marka uploads eligible photos and videos to the Drive folder you select. These are complete media files, including their existing visible stamp and embedded proof. This backup does not include the app database, saved notes/addresses, projects or timesheet database. Google account/folder details used for backup are retained on your device.
Drive backup is separate from company collection and company Google sign-in. Disconnecting Drive, deleting local files or uninstalling Marka does not delete existing Drive copies. Manage those copies in Google Drive. Google processes them under its own privacy policy.
Online timestamps and capture proofs
Online time confirmation is enabled by default on supported Android captures and can be turned off in Settings. When available, Marka sends FreeTSA a SHA-256 digest of the signed capture record. FreeTSA receives the digest and ordinary connection information such as your IP address, not your photo/video, note, coordinates or certificate chain. See FreeTSA's service information.
If online time confirmation is unavailable, a capture can retain its ordinary phone-time seal. A timestamp establishes that a signed record existed by the stated time; it does not prove the photographed scene or exact capture time.
Capture proofs include a public key and may include hardware attestation certificates and capture/device facts. Files sealed by the same installation/key can be linked through that public key. Supported edits preserve original capture facts through separate edit proofs; arbitrary re-encoding or unsupported edits can invalidate verification.
Sharing, exports and file verification
Sharing or exporting hands the selected file/report to the app or recipient you choose. Company users can export collected records and reports. Recipients can see visible stamp information and inspect embedded metadata/proofs; their copies are outside Marka's local deletion controls.
Selecting a file for verification in the app or on the public website checks its bytes locally. That verification operation does not upload the selected file. Company uploads and server verification of already-uploaded files are separate operations.
Retention and deletion
Local records remain until you delete them or remove the app's local data. Gallery copies, shared/exported files and Drive backups remain in their respective destinations. Deleting a company copy does not delete a worker's local copy, and local deletion does not delete the company copy.
Company media has no age-based expiry while it fits within an active plan's allowance. When newer uploads exceed the allowance, eligible oldest media by capture date moves to Pending deletion with a seven-day grace period. The company can free space or upgrade before the applicable deadline. Capacity constraints can also pause uploads, leaving waiting files local. Manual cloud deletion is permanent for the company copy and has no promised recovery window.
After trial or paid access ends, uploads stop. The current lifecycle allows 30 days of read/export/renewal access, followed by seven days pending deletion. Existing capacity-related deadlines can expire earlier. Renewal before deletion can restore eligible access within capacity; it cannot resurrect permanently deleted records.
Generated cloud export downloads expire after 24 hours and are cleaned up separately. Deletion is processed asynchronously: access can end before physical object cleanup finishes. Structured attendance, minimal deletion/deduplication records, billing records and security/support records can have different retention needs from media. We retain those records only as needed for their stated purposes, legal obligations, security or dispute resolution. Company deletion and privacy requests are separate from merely disconnecting a phone.
Delete your account or data
To request deletion, open Delete account and data, sign in, choose Delete account or Delete company data, then confirm the emailed link within 30 minutes. Settings → Profile also offers Delete account; Settings → Company offers Delete company. Cancel an active company subscription in Billing first. Deletion is asynchronous; the private email link shows progress and lets you download a completion receipt after storage and database cleanup have been checked.
Account deletion removes your profile, login credentials, OAuth tokens and sessions. If you are the only company user, it also deletes company media, previews, exports, timesheets, projects, worker labels and device connections. A shared company stays with its remaining company users. Delete company data keeps your login account. Phone originals, Drive backups and recipient copies are not deleted. Workers without a web login can request removal from their company or contact us below.
We retain a private deletion journal and receipt in our database and bucket for 365 days to document the request and prevent deleted data returning during recovery. Notification contact details are encrypted and cleared after the completion email is sent or seven days, whichever comes first. Recovery copies rotate under our configured seven-backup and seven-day point-in-time recovery policy; restoration requires reapplying deletion journals. Minimal billing identifiers remain to reject late payment callbacks, and Paddle retains records under its own policies. A receipt confirms our application checks, not physical erasure of a provider’s storage hardware. A copy of the completion receipt is also emailed to our operator for handling deletion enquiries. It contains request/subject identifiers, timestamps and checks, not deleted photos, notes, credentials or the customer’s private receipt link. Mailbox recovery copies follow the email provider’s retention controls.
You can manage app permissions, local records, optional backup, company connection and available sync settings. Company users can manage company records, devices, exports and the authenticated company-deletion process. Ask your company about worker records it controls, including access, correction or deletion requests.
Depending on applicable law, you may have rights concerning access, correction, export, deletion, restriction or objection to processing, and a right to complain to the relevant authority. Contact us at hello@nakanikuneko.space. We may need to verify your identity and company authority, and some records may need to be retained for lawful reasons. Using an invitation or agreeing to this policy does not remove applicable rights.
Children, changes and contact
Marka is a work tool and is not directed at children. Do not use it to collect children's information without an appropriate basis and the safeguards applicable to your use.
We update this policy and its date when relevant data handling changes. Nakanikuneko operates Marka. Privacy and product-support contact: hello@nakanikuneko.space. Support messages disclose your email, message and any attachments to us and the email services involved; include only information needed for your request.