Privacy Policy
This policy explains the information used to operate Yink accounts, licensing, support, security, and billing connections.
The English version controls if a translation differs.
Information we process
We process account email, license status, device fingerprint, transaction references, and security logs. Yink Studio does not store complete payment credentials.
Local processing and service data
Artwork, projects, previews and print data are processed locally; output is sent to the file or printer destination you select. Maintenance counters and timer settings are saved locally per printer. Authenticated output reports, including successful file output, can send installation ID, app version, a print-settings hash, driver profile, copy count and virtual-machine status to the license service for security and abuse prevention. These reports do not upload artwork or the original print settings. Local files remain until removed. Request access, correction or deletion at support@yinkstudio.com; legal, transaction and security obligations may require retention. Account deletion does not cancel billing. Google handles sign-in if selected; Microsoft handles distribution and updates of Store installations under its own policies.
Automatic application error reports — Sentry
Desktop builds automatically send software exceptions, stack traces, timestamps, platform/runtime information, environment, error stage and configured release version over HTTPS to Sentry in the United States for troubleshooting. Sentry also receives connection metadata such as IP addresses. We do not intentionally attach account, installation or job identifiers, credentials, artwork, screenshots or recordings; exception text can incidentally contain paths or personal data. Retention follows the configured Sentry project settings. Contact support@yinkstudio.com for the applicable retention period, access or deletion requests. Current builds have no in-app reporting switch; deleting an account does not switch off diagnostic reporting.
Local Windows startup and crash records
Windows builds with native diagnostics save startup stages, error codes, time, app/OS version, process/thread identifiers and fault module names/offsets locally. They do not automatically upload these files or create memory dumps. At the next launch, cleanup attempts to keep at most five startup logs and five crash records and remove records older than 14 days; files held open by other instances may remain longer. After closing the app you can inspect or delete the Diagnostics folder. Review any files before choosing to share them with support. Dumps created separately with Windows tools can contain personal data or document content. %LOCALAPPDATA%\Yink Studio\Diagnostics — MSIX: %LOCALAPPDATA%\Packages\<package-family>\LocalState\Diagnostics
How we use information
We use this information to authenticate accounts, provide licenses, prevent abuse, complete support requests, and reconcile provider events.
Cookies
Account sessions use first-party cookies with HttpOnly, Secure, and SameSite=Lax protections on yinkstudio.com.
Service providers
Cloudflare supports hosting and account sessions, Resend sends account email, Stripe processes yinkstudio.com checkout, and Shopify processes applicable BCH Technologies purchases.
Optional website analytics
Only after you allow it, PostHog in the United States receives pricing views, successful email registration or login, verified Google One Tap login, and checkout start or failure events. Events include language, software release, plan and controlled outcomes, plus a random browser identifier stored locally. We do not send account IDs, email addresses, tokens, URL queries or fragments, referrers, form contents or files; automatic tracking and session recording are disabled. Network connections expose your IP address to the provider, but we do not add it to event properties or request location enrichment. Analytics does not link people across devices. Use Analytics preferences in the footer to refuse or withdraw; withdrawal deletes the local identifier and stops future sending and retries, but cannot recall an already sent request. GPC and Do Not Track override permission. Separate API operational events contain no account or browser identifiers.
Contact
support@yinkstudio.com