Privacy policy

Account and sign-in information

When you sign in with Google, we receive basic information such as your Google user identifier, email and verification status, name, and profile image. We use it to create or link your Snaperk account, maintain sign-in, and display your identity. Google sign-in currently uses only basic identity, email, and profile permissions; it does not request access to Gmail messages, contacts, or Google Drive files. The authentication system stores the account connection and necessary authentication tokens.

For email-code sign-in, we process your email address to send and verify a sign-in code. Codes expire after 5 minutes and are stored as hashes in the database. We also store your language preference and profile information you choose to provide, such as a public username, job title, or industry.

Who receives application information

We keep the application status, product, timestamps, and fulfillment records. Depending on the campaign, you may provide a product account identifier such as an email, username, or UID; a reason for applying; job or industry information; and supporting images, videos, or PDF files. Submit only relevant information that you are entitled to share. Do not submit passwords, sign-in codes, or unrelated sensitive information about other people.

After submission, the product's developer can view your public username, profile image, and the information and files provided with that application to review it, activate access, and follow up on usage. Authorized operations staff may access related information for moderation and issue handling. Reading access to unsubmitted staged files is limited to the uploader. Your Snaperk sign-in email is not automatically sent to developers as a separate field; if you enter it as your product account or include it in submitted material, it is shared with the application. The developer's own privacy rules also apply when it saves this information or uses it in its product.

Public content and moderation

Product descriptions, product images, and campaign details become available to visitors after publication approval. Developers and operations staff can view submitted reviews and their moderation status. Once approved for publication, a review's title, body, use case, recommendation, public username or display name, and whether the author received product access are public and may be indexed by search engines. Your Google name may be used as your display name.

Product account identifiers, private application files, and redemption codes are not published as review fields. Check your review text for information you do not want to make public. We keep moderation records, application events, issue reports, and notifications to process applications and follow up on disputes.

Service providers, email, and essential cookies

Snaperk uses Cloudflare to run the website and provide database, file storage, task queues, and security infrastructure. Account and business records are kept in the database; product images and application files are kept in object storage. These services may process data outside your country or region. When email service is enabled, recipient addresses and message contents are processed by Cloudflare's email service to send sign-in codes or access-delivery notifications.

We use essential cookies to maintain sign-in, protect authentication, and remember your language choice. Authentication records and infrastructure may process IP addresses, browser information, request times, and error information for security, abuse prevention, and troubleshooting. Clearing or disabling essential cookies may prevent sign-in or language preferences from working.

When email-code sign-in is available, the sign-in page loads Cloudflare Turnstile. Cloudflare processes signals such as IP addresses, browser and connection characteristics, site identifiers, and associated origins to detect bots and protect code requests. Our server sends the verification token and available request IP address to Cloudflare to check the result, site, and action. Cloudflare also processes these signals to improve bot detection. See the Turnstile Privacy Addendum linked on this page for its data practices.

How AI search handles input

Smart search may send your search text, selected language, and public information about candidate products to Cloudflare and its connected model service, currently using an OpenAI model, to interpret your request and rank results. Search does not automatically include your private applications, files, redemption codes, or Google authentication tokens. Do not enter confidential or sensitive personal information in the search box.

Current model requests disable response storage and gateway requests disable content logging, while setting a 10-minute gateway cache. These settings do not mean information is never retained: caching, website access and security logs, and the providers' own data practices may still apply. Search text also appears in the search-page URL and may remain in your browser history or links you share.

Retention and file cleanup

Unsubmitted staged files become eligible for cleanup 24 hours after upload; removed files become eligible 24 hours after removal. Files attached to a pending application are retained. Once an application is no longer pending, attached files become eligible for cleanup 90 days after the decision time or latest status-update time. Cleanup runs in background batches, so actual deletion may occur later; failed deletions are retried.

After file contents are deleted, records such as the filename, type, size, and associated status may remain. Account, application, fulfillment, review, moderation, and notification records currently have no single automatic expiry period; they support ongoing service, processing history, and issue resolution. Removing or replacing a product image also does not immediately delete its underlying stored object.

Access, correction, and deletion requests

Existing pages let you view applications, edit or withdraw them while pending, and edit your own reviews. Withdrawing an application does not automatically delete its records. There is currently no self-service account deletion or one-click export of all personal data.

To request access, correction, export, or deletion of personal information, email the Snaperk team below and identify the account and request. We will verify your identity, assess the relevant records and any need to retain them, and discuss how to handle the request. Do not email passwords, sign-in codes, or full redemption codes. You can also revoke Snaperk's authorization through your Google Account's third-party connections settings; revocation does not automatically delete data already held by Snaperk.

Updates and contact

We update this page and its revision date when our data practices change. For questions about this policy, privacy concerns, or related requests, contact the Snaperk team at juntook@gmail.com.