privacy information

operator and contact

gnocchi is operated by Yurumi, a business established in Sweden. use our private operator inbox for privacy, moderation and payment questions. keep the receipt link to check for a human response.

account, profile and work

Base44 handles email/password verification, Google sign-in and account sessions. account email and authentication data are not public profile fields. chosen profile names, handles, biographies, disciplines, avatars, availability and contact/portfolio links are public. new accounts are members. members apply once with 1–3 snippets to become designers. an accepted application publishes exactly its reviewed selection and grants direct publishing for future projects and snippets. application status, staff/advertiser permissions and publishing suspensions are separate; disciplines, credits and payments do not grant publishing access. public portfolios belong to designers, while members have a basic interaction identity. public work and collaborator credits may be seen by visitors, search engines and people who share them. credits are supplied names/links, not verified invitations or ownership.

new snippet uploads, sanitised media, posters and analysis frames are stored privately with encrypted media bytes. short-lived authorised viewing grants allow an applicant, permitted reviewer or visitor to published work to view the appropriate media; storage references alone cannot decrypt it. historical public uploads continue to use their existing private-storage viewing links. applications, their review snapshots, internal notes and drafts remain private before acceptance. private storage does not make a published work confidential. drafts, account details, cookbook folders/saves, feedback, reports, legal requests and payment ledgers are not publicly listed. do not submit client-confidential or unauthorised material.

cooks, saves and activity

cook totals and recent cook/copy/share activity can be public. activity names are off by default; settings → privacy controls optional identity. turning identity off suppresses prior names; turning it on does not identify earlier anonymous events. cookbook details stay private, though consenting engagement can contribute to a designer's aggregate save counts. a tip has a separate name choice at checkout; it may appear across the designer's public snippets without amount or billing details. request a correction or attribution withdrawal.

analytics and storage choices

audience analytics measure content impressions, opens and link/contact clicks. advertising measurement uses visit/browser identifiers for impressions, clicks and approximate reach. designers/advertisers receive aggregate reports, not named viewer lists. optional audience, advertising and search measurement are off until consent, with separate choices in cookie preferences; dnt/gpc suppress them. functional votes, saves, security and necessary service records still operate.

search observations include sanitised queries, selected filters, result counts, timestamps and opening attribution with random interaction ids. obvious sensitive patterns are rejected but queries are not guaranteed anonymous. do not enter personal or sensitive information. configured detailed retention is 30 days and daily aggregates 12 months; these are product settings, not statutory periods.

payments and newsletter

Stripe checkout/Connect is currently in sandbox mode and no connected designer is ready to receive tips in the audited configuration. the implementation permits one-time usd tips from $1 to $100, default $5, not a fixed $3. it specifies no application commission or separate service-fee line; Stripe fees can affect settlement. no support gnocchi payment, monthly support cancellation or badge-entitlement flow is implemented. snack language means cash support, not food or a charitable/tax-deductible donation. contact us about payment errors, refunds or any applicable withdrawal right; no mandatory right is excluded and no voluntary change-of-mind refund is promised.

Stripe handles payment details; gnocchi receives account/profile and checkout/payment references, state, optional attribution and a hashed requester key, not full card numbers. newsletter subscriptions store email, status and an unsubscribe token separately from accounts; the public archive exists, but outbound newsletter delivery is not implemented in the audited code. account verification/reset and service messages are separate.

providers and retention

Base44 supplies application hosting, authentication, database, file storage and platform service email infrastructure. Stripe supplies payments when used; choosing Google sign-in involves Google. following external contact links or visiting social channels involves those providers. we do not claim eu-only hosting or absence of international transfers. ask the operator about applicable provider arrangements through the private channel. automated element suggestions: after you upload a snippet while signed in, your browser makes one small, reduced-size jpeg preview of it (for an image, a scaled copy; for a video, a sheet of four still frames sampled at set points with their timestamps; svgs are cleaned of scripts and external references first). the original file is not sent for analysis. the preview is uploaded to gnocchi's private file storage on Base44, our hosting and backend provider, and a link to it that expires after two minutes is passed to Base44's built-in ai integration. Base44 selects the ai model and the provider that runs it, so that provider receives the preview and our list of element names. its only purpose is to propose up to three elements from gnocchi's fixed element list; suggestions are editable defaults that you can accept, change or ignore, and they never approve, publish, feature, title or describe work. Base44's storage offers us no way to delete files, so the preview stays in private, non-public storage, and we keep a reference to it for deletion once that becomes possible. Base44's published documentation says data on plans other than Enterprise may be used to train ai models. gnocchi is not on an Enterprise plan, so we cannot rule this out. Base44 does not publish how long the model provider keeps the preview. we privately keep a staff-only record of each suggestion: which snippet and media version it was for, the suggested and final elements, whether you used the suggestion, when it ran, and the element-list and model setting used. it is never shown publicly. you can always choose elements yourself.

notification display content is cleared after 30 archived days or 90 unread days, except action-required items; minimal delivery keys and source records remain. there is no universal automated retention/deletion process for every record or file. project-row removal is not complete media/account erasure, and backups/third-party copies can persist separately. deletion and export requests require manual handling. necessary narrow financial records may remain under applicable duties without keeping an entire account.

rights and requests

request access, correction, deletion, portability, restriction, objection or consent withdrawal through settings → privacy or the public request form. this is a request, not an instant export or deletion operation. we should respond without undue delay, normally within one calendar month, with notification and reasons for lawful extensions. verification must be proportionate; identity documents are not required by default. withdraw optional tracking at any time in cookie preferences, without changing the lawfulness of prior consent-based processing.

you can complain to Sweden's IMY or another competent supervisory authority. editorial decisions are human; rule-based validation, sorting and anti-abuse checks exist. no solely automated legally significant decision flow was found. registration currently has no age-verification field; contact the operator about a child's information.

about this information

this is a factual service-information notice, prepared 27 october 2026, version info-2026-10-27. it is not a replacement terms agreement. a complete replacement privacy policy is held for operator/legal review before approval; accepting terms does not mean consenting to optional analytics or newsletters.