Winkumi Privacy Policy
Version: 21 October 2026. This policy covers Winkumi’s local creative features and the optional online account service for people aged 16 and over. Feature availability is shown in the app. Local discoveries remain on your device.
Winkumi is provided by Parallax Software.
Menno Simonszplein 75, 2014SC Haarlem Netherlands
Privacy and data requests: info@parallax.software
Your photos stay with you
Photos, face parts, discovery names and notes, drafts and device progress stay on your device unless you choose an online action. Creating an account never automatically uploads your album. In the mobile app you can select a discovery and save immutable original and edited photo copies, layers, title, note and category to your private account Nest. A local pending-upload queue keeps only the copies you explicitly choose; sending requires your explicit action and a current account session. Editing your local discovery later does not silently replace that queued copy. The website shows only your own account Nest and does not upload or edit photos. You keep ownership of your photos and creations. We provide your account profile, selected interests, posts and progress to perform the features you request; there is no automatic transfer of your local profile or album.
Private posts and photos are accessible to your current account and authorised service/moderation operations. You choose whether to request publication review. Only eligible approved posts become visible to other signed-in members, with your account display name and username. A publication request is separate from private saving; block and report filters apply to Explore. Selected interests, post categories and creation times support the requested feed ranking and account progress. We do not use this information for targeted advertising or direct messaging.
Private posts and photos are accessible to your current account and authorised service/moderation operations. You choose whether to request publication review. Only eligible approved posts become visible to other signed-in members, with your account display name and username. A publication request is separate from private saving; block and report filters apply to Explore. Selected interests, post categories and creation times support the requested feed ranking and account progress. We do not use this information for targeted advertising or direct messaging.
What an optional account uses
An optional account uses your email address, display name, password, self-declared age range and acknowledgement of the current Privacy Policy and Terms. We process these details to provide the account, sign-in and password recovery you request, on the basis of performing that service. Your display name can be a nickname. This flow does not request a full date of birth, identity document, location or phone number.
We store your email address and display name, a password hash, account and sign-in identifiers, account status, age range, and the versions and server times of your privacy and terms acknowledgements. Acknowledging this notice is not blanket consent for unrelated processing, age verification or parental permission. Security and abuse prevention rely on our legitimate interest in protecting the service, with access restricted to what is necessary; a specific legal obligation or legal claim can require limited additional retention.
We store your email address and display name, a password hash, account and sign-in identifiers, account status, age range, and the versions and server times of your privacy and terms acknowledgements. Acknowledging this notice is not blanket consent for unrelated processing, age verification or parental permission. Security and abuse prevention rely on our legitimate interest in protecting the service, with access restricted to what is necessary; a specific legal obligation or legal claim can require limited additional retention.
Email codes and security
Account, sign-in and password recovery codes are sent from info@winkumi.com using Google Workspace and the Gmail API. Google processes the recipient email address, message and delivery information to deliver these service messages. These are not marketing messages. Never share your password or verification code with support.
The account database stores protected hashes of codes and session tokens, validity times and attempt counts. Codes are valid for 10 minutes; this validity period is not a promise that every related database or mail-provider record is erased after 10 minutes. Sign-in and security records can include the IP address, user agent, event time and result to limit abuse and investigate access problems.
The account database stores protected hashes of codes and session tokens, validity times and attempt counts. Codes are valid for 10 minutes; this validity period is not a promise that every related database or mail-provider record is erased after 10 minutes. Sign-in and security records can include the IP address, user agent, event time and result to limit abuse and investigate access problems.
Age ranges and device protection
Local creative features can be used without an account, including by people under 16. Online accounts are for people aged 16 and over. The account screen asks whether you are under 16, 16–17, or 18 and over; these are self-declarations, not age verification. People under 16 cannot register, and no parental approval or parent-registration process is offered. Do not select an older age to evade this limit. We do not collect a full date of birth or identity documents in this flow.
An existing younger-use restriction on a device remains in place; choosing an older age does not erase it or assign local discoveries to an account. No child or parent contact details are requested to unlock that restriction. Local photos and drafts remain available on that device.
An existing younger-use restriction on a device remains in place; choosing an older age does not erase it or assign local discoveries to an account. No child or parent contact details are requested to unlock that restriction. Local photos and drafts remain available on that device.
Updates and service providers
Winkumi checks for compatible signed updates over HTTPS using the platform, runtime version and update channel. Hosting, delivery and security services can process the IP address, request time, path, response status and timing. Photos, discovery notes and account passwords are not included in update requests.
Update checks and update-file downloads also send a random identifier created for this app installation (EAS-Client-ID), stored in the app’s private preferences. It is not an advertising identifier or a hardware serial number.
Google Workspace and the Gmail API deliver account email; the hosting, network and security services support delivery and account protection. Providers receive only the data needed for their role under applicable processing terms. Processing can take place outside the European Economic Area; applicable transfer arrangements, including contractual safeguards where required, govern that processing. This version has no advertising SDK, advertising identifier or in-app behavior analytics SDK. We do not sell your data or use it for targeted advertising.
Update checks and update-file downloads also send a random identifier created for this app installation (EAS-Client-ID), stored in the app’s private preferences. It is not an advertising identifier or a hardware serial number.
Google Workspace and the Gmail API deliver account email; the hosting, network and security services support delivery and account protection. Providers receive only the data needed for their role under applicable processing terms. Processing can take place outside the European Economic Area; applicable transfer arrangements, including contractual safeguards where required, govern that processing. This version has no advertising SDK, advertising identifier or in-app behavior analytics SDK. We do not sell your data or use it for targeted advertising.
Permissions and exported copies
Camera and photo access depend on the permissions you choose to grant in the operating system. You can change them in device settings. This version does not request location or microphone access. You choose the destination when exporting or sharing an image. Copies in your photo library, another app or an operating system backup follow that destination’s rules and must be managed separately.
Deleting an account and local discoveries
Account information is retained while needed to provide your account. Incomplete registration records are needed only to complete or recover that registration and protect its verification process; when that purpose ends, they are reviewed for removal after any required security checks and limited retention obligations. Code and session validity are not promises of physical erasure at the same instant.
When full account and photo deletion is shown as available, you can start it in account settings or on this website’s account deletion page. A fresh password and email-code verification and a separate final confirmation are required. The confirmed request closes the account, ends its sessions and hides its posts. The same request can continue after a lost connection without another permanent-delete confirmation. Completion is shown only after the supported active account, profile, posts and revision history, uploaded originals and edited copies, and associated sign-in and security records have been removed and the active photo objects are confirmed absent. A pending or interrupted operation is not a completed deletion. An unresolved upload, unknown provider outcome, unsupported dependency or retention obligation can prevent safe progress; contact info@parallax.software without sending a password or code.
A limited receipt is kept so the confirmed request can resume safely and an older restored database cannot reactivate the erased identity. On completion it does not retain the email address, raw account identity, photo location, password or session credential. Minimal identifiers in another member’s block/report records and records needed for an unresolved security incident, fraud prevention, consent evidence, a specific legal claim or a mandatory obligation can be retained only while necessary for that purpose. Security and audit records are reviewed against their recorded bounds and any current hold. Such retention is separate from active account use; it is not permission to keep using an erased account.
Sent service email, access/error logs and backups are separate copies. They are retained only while needed for delivery or support, security, a specific obligation, or the relevant backup/infrastructure cycle. Account deletion does not instantly erase every backup, provider or previously exported copy. Those copies have their own removal process. A restore must respect an earlier erasure request rather than treat the old identity as a new active account. A later registration is a separate account.
Account deletion keeps discoveries and drafts stored on your device. It does not remove exported images, operating-system backups or copies you sent to another service; manage those copies at their destination. Where full deletion is unavailable, the screen describes the supported scope and does not claim that all account or media copies were erased.
When full account and photo deletion is shown as available, you can start it in account settings or on this website’s account deletion page. A fresh password and email-code verification and a separate final confirmation are required. The confirmed request closes the account, ends its sessions and hides its posts. The same request can continue after a lost connection without another permanent-delete confirmation. Completion is shown only after the supported active account, profile, posts and revision history, uploaded originals and edited copies, and associated sign-in and security records have been removed and the active photo objects are confirmed absent. A pending or interrupted operation is not a completed deletion. An unresolved upload, unknown provider outcome, unsupported dependency or retention obligation can prevent safe progress; contact info@parallax.software without sending a password or code.
A limited receipt is kept so the confirmed request can resume safely and an older restored database cannot reactivate the erased identity. On completion it does not retain the email address, raw account identity, photo location, password or session credential. Minimal identifiers in another member’s block/report records and records needed for an unresolved security incident, fraud prevention, consent evidence, a specific legal claim or a mandatory obligation can be retained only while necessary for that purpose. Security and audit records are reviewed against their recorded bounds and any current hold. Such retention is separate from active account use; it is not permission to keep using an erased account.
Sent service email, access/error logs and backups are separate copies. They are retained only while needed for delivery or support, security, a specific obligation, or the relevant backup/infrastructure cycle. Account deletion does not instantly erase every backup, provider or previously exported copy. Those copies have their own removal process. A restore must respect an earlier erasure request rather than treat the old identity as a new active account. A later registration is a separate account.
Account deletion keeps discoveries and drafts stored on your device. It does not remove exported images, operating-system backups or copies you sent to another service; manage those copies at their destination. Where full deletion is unavailable, the screen describes the supported scope and does not claim that all account or media copies were erased.
Your choices and data requests
You can use available local features without an online account. Contact info@parallax.software to request access, correction, erasure, restriction, portability or information about your personal data, or to object to processing based on legitimate interests. We ask only for the minimum information needed to identify the records securely. Where a request cannot be completed because a specific obligation or unresolved security issue applies, we explain the applicable reason and review route. You can complain to the Dutch Autoriteit Persoonsgegevens or the relevant data protection authority. Changes that introduce new account-data processing will be explained before that processing starts.