ZUKY
Your ideas. Your information.
A private workspace, a shared community and clear choices about what leaves your space. Updated 22 November 2026.
Who is responsible?
Zuky is a trade name of Destroombank B.V. We determine how personal information is used to operate Zuky and are the controller for that processing.
Destroombank B.V.Torenlaan 5B, 1402 AT Bussum
The Netherlands
KVK 96706902 · VAT NL867724742B01
What we use, and why
- Account and workspace. Your site-specific sign-in ID, display name, profile details, preferences, projects, tasks, notes, files and collaboration records let us provide the service you request. Our basis is performance of our agreement with you. We use your email address and a one-way password hash for email or Zuky ID sign-in. If you connect Google, we store its account identifier and protected sign-in credentials; we do not receive your Google password. Confirmation and recovery links go to your account email. Earlier registrations may contain your sign-in email and submitted note. We also save the last section you opened in each project so you can resume on another device. That navigation preference is private to your account.
- Sign-in security. Necessary session cookies keep you signed in. We store session creation, activity and expiry times and browser/device information so you can review and end your sessions. At registration, our hosting provider can estimate a country from your connection. To see where people join Zuky, we count new accounts by UTC day and estimated country. These totals contain no account identifiers. For adults who have not set a usual base, the current connection country can also help suggest relevant posts. Travel or a VPN can change this estimate. Your profile location stays under your control. Trusted hosting network information can support abuse protection. Request counters use keyed identifiers instead of readable email addresses or Zuky IDs. These measures support our legitimate interest in protecting accounts. Your sign-in email and device list are not public profile data. Account & security also shows a private history of successful sign-ins, session endings and changes to your sign-in details. History entries contain a time, an action and, for sessions, a general browser/device label. They do not contain your password, session token or full IP address.
- Your Zuky ID. We assign a public eight-character code so people can find and share your profile without your email address. It is not a password and does not grant access to private content. After account deletion the code stays reserved, with its account link and assignment time removed, so an old shared code cannot point to a new member. A public profile page still requires your separate publication choice.
- Community and conversations. We store posts, replies, media, follows, connection requests and messages to deliver those features. Your chosen display name, optional profile image and introduction accompany your activity. You can use a nickname and remove your profile image. Your sign-in email is not shown on your profile. A chosen name does not make activity untraceable: we still link it to your account for security, delivery and moderation. We do not sell your personal information or use it for cross-context behavioural advertising.
- Your feed. We remember up to 3,000 post IDs and the time you first viewed each one so For you can prioritise posts you have not seen. We do not save a recording of your scrolling or time spent on each post. This history is private to your account and stays until replaced or the post or your account is deleted. Latest, Following and your saved posts remain available independently. Recommendations also use your chosen interests, follows, topic feedback and a bounded selection of your recent likes and saves. You can change interests, ask for less of a topic, remove a like or save, or use the chronological Latest view. Our basis is our legitimate interest in a useful, less repetitive feed.
- Location you choose to share. You can add a country, region and city to your profile and choose which level other members can see, or hide your location. These fields are optional. We do not request GPS access or infer your address. Your location choice is used to present your profile and support relevant discovery.
- Safety and reliability. Reports, blocks, moderation actions, request counters and limited audit records help prevent abuse and investigate faults. Our basis is our legitimate interest in a secure, usable service, balanced against your rights. Legal obligations can also require processing.
- Feedback. When you send feedback, we store your selected category, note, app page address, account ID, submission time and review status. This helps us investigate problems and improve Zuky. Private project content, screenshots and device logs are not automatically attached. Feedback is visible to you and authorised moderators, not other members.
- Eligibility and choices. We record the terms version, privacy notice version and time of acceptance. For registration with Zuky, we ask your date of birth before collecting new account details. Existing members without a declaration are asked before continuing into the app. We use it to check eligibility and apply age-appropriate safeguards. We retain the declaration method, assessment date, age group and, for members under 18, the date when that protection boundary is reached. We do not retain the submitted birth date separately or show age information on your profile. This is self-declared information, not verified age identification. A short-lived private cookie carries this check through registration, including Google sign-in, and discourages immediate retries after an ineligible date. You can export your stored declaration or request a private correction review in account settings, including when age eligibility blocks access. We retain the requested age group, relevant protection boundary, your explanation, review outcome and timestamps. Authorised reviewers can examine these records; they are never part of your public profile. Account deletion removes them. Historical acceptance records can contain the adult declaration required when they were accepted.
- Invitations and Founding membership. If you accept an invitation link, we record the inviter and your account, the acceptance time and whether you qualify under the Founding Member rules. Qualification checks profile completion, an owned project with a completed task and a return visit after 24 hours. The inviter sees only totals; this never exposes your private work. We use these records to administer the programme and prevent duplicate claims. A pseudonymous account identifier remains after deletion to prevent claiming again while this programme is active; it is not anonymous data. Earned badges are visible beside profile photos. They are not identity verification, financial entitlements or ranking scores. Read the programme rules.
Private work and shared work
Project concepts, tasks, notes and attachments are restricted to the owner and invited project members. Viewers can read; editors can change content. Keep invitation links private. Owners can revoke unused invitations and remove members.
A community excerpt or project update does not publish your underlying workspace. Project followers need owner approval and see only the separate updates page. They do not become collaborators. Closing that page stops follower access.
Sharing an ordinary post link does not make its content public. If you choose a public image preview, we make a separate copy of the one image you reviewed available to anyone with that preview link, including people without a Zuky account. Your post text, comments, profile details and workspace are not included in that preview. This option starts off and is available only for community posts on a public profile. We record your choice, its version and publication time to apply that choice.
You can turn off a public image preview in the post’s Share controls. Editing or hiding the post, changing its audience or your profile’s privacy, or removing the selected image also stops future preview reads from Zuky. Making the post or profile public again does not restore an old preview. Recipients and social platforms may keep copies they already received. Member blocking does not restrict an image you have separately made public.
Zuky invites investors to join its Lifter network. With the candidate’s permission, our team records their contact details, professional background and portfolio for review. We keep the review decision and its reasons with the candidate record. After approval, the candidate can review the professional introduction and accept a private invitation with their verified Zuky account. Their Lifter badge and approved introduction then appear on their member profile, including a private profile. Contact details and review notes stay private. The badge identifies membership of the network. It does not certify funds or endorse an investment.
Project owners can explicitly publish a separate introduction and selected text excerpts for all approved Lifters. The owner previews the exact content before publishing. Those shared snapshots do not automatically change with private tasks or notes. Full workspace access still requires an invitation to a specific person. Disabling Lifter sharing stops access to the shared version; separately invited workspace members must be removed separately.
Lifters can optionally let project makers know when they view a shared project. This is off by default. When enabled, a visible project visit can create a notice naming the Lifter and linking to their profile, at most once per project per 24 hours. Merely fetching a list does not create a notice. The setting can be turned off for future visits; earlier notices remain with their recipients. Visit records are removed after 90 days by bounded cleanup during subsequent visit processing. Notices follow the recipient’s notification settings.
A private profile restricts its posts and follower lists to approved followers. Your basic introduction, name and photo can still be visible to signed-in members, including alongside replies in threads you join. Disabling discovery removes you from discovery lists; it does not make published activity anonymous. Blocks restrict access in both directions within the signed-in app.
Each post can be shared with the community or only your followers. A private profile restricts both to approved followers. Changing to public opens existing community posts to Zuky members; posts explicitly set to Followers stay restricted. Drafts and workspace content are never published by changing these settings.
A separate, optional public page lets visitors without an account read information you explicitly choose to publish outside Zuky. Review the preview in your profile’s sharing controls, choose any photo, bio, collaboration details or website to include, and confirm publication. Your name and username identify the page. Individual posts require their own publication choice and an active public profile page. Comments, location, private work, follower lists and messages are not included. Original post attachments stay in the app; a separately published image preview can accompany a shared link.
Turning off the profile page withdraws its public posts too. Editing shared profile details, making your profile private, hiding or editing a post, an account hold, or account deletion withdraws the affected pages. Republishing requires a fresh choice. We keep the selected fields, consent version and latest publication time with your account and include them in your export. Public pages are not offered for search indexing or cached by Zuky. Anyone can still read or copy a published page, including someone visiting anonymously after being blocked. We cannot recall copies saved by other people or services.
Messages are restricted to participants through the app, but are not end-to-end encrypted. The operator and service providers may access stored information when needed for administration, security, legal requests or troubleshooting. A message request can include a first message, visible to its recipient before they decide whether to accept. In accepted direct and group chats, participants can share photos, videos and voice messages. We privately record which messages you have read to update your unread count. A direct-message read receipt is shared only when both participants have read receipts enabled when the recipient reads the message in the open, visible conversation. Fetching an inbox does not create a receipt. Turning this choice on later does not reveal messages read while sharing was off. Either participant can turn read receipts off in Message choices; shared read times are then hidden, including in account exports. Typing indicators share a short-lived typing signal with accepted chat participants, never your unsent text. You can disable sharing and seeing these signals in Message choices. They expire automatically; they do not create an online or last-seen history.
Optional AI
Translation is optional. When you select Translate, Zuky checks whether it already has a current translation into your reading language. When a new translation is needed, the selected text and target language are sent to the configured translation service.
The launch interface does not offer project coaching or photo-based idea generation. Adding a photo to a project, Jam or message does not by itself send it to Google Gemini for ideas. If you create concept art in a tool you choose outside Zuky, that tool handles your input under its own terms.
For post translation, only the selected post and requested language are used. We store one current translation per post and language so readers who already have access can reuse it without sending the same text again. It does not become public or enter your private AI conversation history. Editing the post text invalidates its translations; deleting the post deletes them. Profile privacy, blocks and post permissions apply to every request.
You can stop using AI and clear its history. That cannot undo a request already processed by the provider. Contact [email protected] for information about provider retention, regional processing and training settings. Do not send secrets or another person's information without an appropriate basis. Zuky is not intended for sensitive or regulated data.
Providers and international use
Cloudflare Turnstile helps protect registration and account access from automated abuse. When a security check is needed, Cloudflare processes technical browser and network information, including your IP address. Zuky checks the result on its server. We use short-lived, keyed security counters and token fingerprints rather than storing raw passwords or challenge tokens in those counters. These checks support our legitimate interest in preventing fraud, spam and account attacks.
Zuky manages your sign-in session. Its application host and database process account and application records. Google handles sign-in if you choose it. Resend receives your email address and the content of transactional account emails and applicable plan notices for delivery. Storage services handle uploaded files. Device and browser providers process push subscriptions if you opt in. Cloudflare processes selected text when its translation service is used. When automated community moderation is enabled, the relevant content can be sent to OpenAI for a safety assessment. Ask [email protected] about the providers and transfer safeguards for your account.
Providers may process information outside your country, including outside the EEA. International transfers are subject to applicable data-protection requirements. Contact [email protected] for information about the providers, processing locations and transfer safeguards that apply to your data.
Opening an external tool does not connect it to your Zuky account. Sharing sends the link or file you select to the receiving app. A profile card can include your chosen name, photo and Zuky ID. A project card can include its title and cover. An exported image can be forwarded or kept independently, even after access to the original changes.
Cookies, storage and notifications
Sign-in uses necessary session mechanisms. Zuky stores functional preferences such as theme, motion, board/list choice and the last visited project on your device. Resume identifiers are account-scoped and do not contain private project text. Unsent text may remain in bounded tab memory until you close or reload the tab.
Landing button counts are aggregated by day without visitor identifiers. No advertising tracker or marketing-email sender is included. Optional tracking would require a separate assessment and, where required, prior choice. Hosting and sign-in providers may keep operational logs.
Push is optional and can be disabled in settings and your browser. Lock-screen wording is generic. The service worker does not cache private account data for offline use.
Retention and deletion
Optional product improvement measurement is off unless you choose it in Settings. With your consent, Zuky records a small set of day-level milestones for 56 days: creating a task, marking a task done, acknowledging someone's response and returning to take another project step. We compare groups using existing profile language and country information, never city, precise location, private text or scrolling behaviour. These records stay within Zuky and do not affect your feed, badges or access. They are available in your account export, stop contributing to reports after 90 days and are then removed by routine cleanup. Turning the setting off deletes the measurement records immediately. Deleting a source task or comment also removes its measurement reference. Choosing not to participate does not limit the product. You can withdraw consent at any time.
Sign-in sessions expire after 30 days unless renewed through active use. Recovery links expire after 30 minutes and email confirmation links after 60 minutes. Expired session and verification records are removed in bounded maintenance rounds. Changing or resetting your password ends other sessions; you can also end them from Account & security. Security activity is available for 90 days; expired history entries are removed in bounded maintenance rounds. Deleting your account removes its Zuky sign-in credentials, sessions and security history. An unfinished email registration without a profile may be removed after 30 days without verification or account activity. A fresh confirmation request protects it from this cleanup. Current recovery requests, sessions and safety restrictions are preserved; minimal identity safeguards remain to prevent old links or restrictions from transferring incorrectly to a new signup.
Account-email content and links are encrypted while awaiting delivery. They are removed after a final delivery attempt or expiry; an active attempt finishes before maintenance clears it. Body-free delivery receipts and their feedback are removed after seven days without updates. We retain a keyed recipient identifier and minimal block or clearance information to prevent unwanted mail and delayed delivery reports from undoing your request. This is not a public email address and is not used for advertising. Resolved support decisions can be removed after 180 days following an authorised review; active blocks and necessary preservation remain protected.
Account and project records remain until you delete the content or account, subject to legitimate legal and safety retention needs. Rate-limit windows expire and old counters are cleaned opportunistically. Unused media is also cleaned opportunistically; deleting its metadata revokes app access even if object-storage cleanup must be retried.
Account deletion removes active profile data, owned projects, posts, connections and conversations. Contributions in someone else's project may remain without your author identity. A consumed Founding Member number is not reissued; its account link is removed. Deletion does not itself erase independent provider logs, backups or copies shared outside Zuky.
To keep an old sign-in or open tab from recreating a deleted account, we retain a pseudonymous account-status key, revision and deletion time. This is not your profile or project content and is not used for recommendations or advertising. Starting again requires an explicit new-account action and does not restore your previous records. For Zuky email or Google sign-in, the internal identity uses a keyed pseudonym of your verified email. This allows account safety restrictions to continue when that same address registers again; it is not a public email directory.
Deletion can be subject to necessary backup, security and legal retention. Contact [email protected] for the retention periods and exceptions that apply to a specific request.
Your choices and rights
Use settings to edit your profile, control visibility, manage notifications, export records or delete your account. Exports contain structured records and file metadata; download file contents from the project. General AI history can be cleared separately.
Depending on the applicable law, you may request access, correction, deletion, restriction, portability or object to processing based on legitimate interests. You can withdraw optional consent for future processing. Rights have lawful exceptions; reasonable identity verification may be needed. Authorised agents may act where applicable. We do not penalise you for exercising privacy rights.
Send requests to [email protected] or our postal address above, including after deleting your account. You do not need to create a new account to make a request. Under the GDPR we normally respond within one month; if a lawful extension is needed, we explain it within that month. You may complain to your local data-protection authority, including the Dutch Autoriteit Persoonsgegevens.
US rights depend on your state and whether its law applies. Where applicable, we honour access, correction, deletion, portability and appeal rights. Zuky does not currently sell personal information, share it for cross-context advertising or use it for targeted advertising, so there is no such activity to opt out of.
Age eligibility and policy changes
Zuky is intended for people aged 16 and over who meet the eligibility requirements in our terms, including any higher local requirement or required permission. Report suspected ineligible use so we can investigate and take appropriate action. A date of birth declaration is not verified age identification and does not replace our response to actual knowledge of underage use.
For members recorded as under 18, profiles start private, discovery and location sharing are off, new message requests are limited to people they follow, and read receipts, typing signals and optional push notifications start off. Existing public profile and post pages, shared project pages and Lifter project snapshots are withdrawn when that first declaration is recorded. A correction request for an under-18 age applies these protective defaults immediately; an under-16 request also pauses product access while it is reviewed. Approved Lifter status is suspended for a separate review. No review approval automatically republishes content. Recommendations use chosen interests without inferring interests from likes or saves, and videos play when the member chooses to play them. Turning 18 does not automatically publish a profile or enable read receipts, typing signals or notifications.
Material changes are communicated in the service. New optional purposes are not covered by an old checkbox. Terms acceptance, optional AI permission and notification choices remain separate.