1. Information we collect
Account and identity
When you sign in with Google, Zinkr receives your Google account identifier, verified email address, display name, and profile photo. Zinkr never receives your Google password.
Profile and payment-destination content
We store the name, handle, photo, introduction, public location or role, payment handles or links, payment-option order, and other content you choose to publish. You may separately enter an optional U.S. public phone number. For eligible Zinkr Plus profiles, that number can appear in a business contact sheet or after a payment handoff and can open the visitor’s calling or messaging app; Plus can also offer a vCard containing the profile display name and that phone number. Zinkr never copies sign-in, billing, payment-handle, Zelle, or Google Places phone data into this field. Older contact or theme values may remain in account records for compatibility but are no longer accepted or displayed.
Business phone verification
Eligible Zinkr Plus customers can submit a Google Maps link for a public Places listing. Zinkr sends the selected listing’s phone number to Twilio solely to deliver and check a six-digit text or voice code. Zinkr stores the Google Place ID, verification and publication status, timestamps, requested channel, the last four phone digits, one-way security identifiers, delivery/check counts, and non-sensitive status events. It does not store the code, Twilio token, provider secret, or full phone number in its claim audit records. Listing details are refreshed from Google rather than treated as proof of ownership. A successful check proves control of the listed phone only, and the business is not public until the customer separately publishes it.
Billing, safety, and service data
For Zinkr Plus, we store Stripe customer and subscription identifiers, subscription status, and billing-period dates. Stripe—not Zinkr—collects and processes full card or bank-payment details for the subscription. We also record profile activity, safety reports, verification delivery metadata, timestamps, and operational security data such as rate-limit identifiers. A safety report may include an optional reporter email; it is available only to authorized Zinkr moderators and a configured safety-alert processor, never to the reported profile owner. High-risk reports can temporarily pause a new or repeatedly reported profile pending owner or moderator review. Hosting and security logs may include IP address, browser or device details, and request information.
2. How we use information
We use this information to authenticate users; create, publish, personalize, and secure profiles; send visitors to the selected payment provider; provide profile analytics; administer Zinkr Plus; prevent abuse; respond to safety reports and support requests; maintain service reliability; and comply with applicable obligations.
Profile views and provider selections indicate activity and outbound intent only. Zinkr cannot tell whether a payment was completed.
3. When information is shared
We use service providers needed to operate Zinkr, including Google for identity and public Places listing data, Twilio for SMS and voice verification, Stripe for subscription billing, Railway for hosting, and PostgreSQL infrastructure for application data. These providers process information under their own terms and privacy notices.
When a visitor chooses a linked payment service, the visitor leaves Zinkr and that provider receives information according to its own practices. Public profile content may also be copied or shared by other people. We may disclose information when required by law, to protect users or the service, or in connection with a legitimate business reorganization.
4. Cookies and browser storage
Zinkr uses only strictly necessary, first-party cookies for secure authentication and page-owner access. We do not currently use analytics, advertising, personalization, or session-replay cookies, and Zinkr does not store preferences in local or session storage. Because no non-essential storage is used on Zinkr pages, we do not show an accept/reject banner. See the Cookie Notice for names, purposes, and durations.
5. Retention and security
Profile, account, verification-delivery, event, safety, and billing records are kept while needed to provide and protect the service, enforce verification limits, resolve disputes, or meet legal obligations. Authentication cookies expire after eight hours. Business verification sessions expire after five minutes. Deletion requests may not immediately remove information from limited security records or backups where retention is still necessary.
Zinkr uses signed, HttpOnly cookies, HTTPS in production, access controls, request-origin checks, durable delivery limits, and other safeguards. No online service can guarantee absolute security.
6. Your choices and rights
You can correct profile information in Manage Profile, change payment destinations, pause the public page, and manage or cancel Zinkr Plus through Stripe’s secure billing portal. To request a copy, correction, or deletion of account data, email hello@zinkr.net. We will assess the request and may need to verify that you control the account. Rights vary by location and may include access, correction, deletion, restriction, objection, portability, or a complaint to a data-protection authority.
7. International processing and third-party services
Zinkr and its providers may process information in the United States and other places where they operate. Privacy protections can differ by location. Google, Stripe, Railway, payment providers, and other linked services publish their own notices describing their processing and international-transfer practices.
8. Changes and contact
We may update this notice as the product or legal requirements change. The effective date above identifies the current version. Questions or data requests can be sent to hello@zinkr.net.