Your data
Privacy Policy
1. Controller and contact
The proposed controller for GameGigs is:
SCALABLE PERFORMANCE GROUP GmbHMartinistr. 66
49078 Osnabrück
Germany
Privacy contact: support@scalable-performance-group.de
Telephone: +49 541 93135030
The operator details are based on the SPG Studio Privacy Policy. Further company information appears in our Imprint.
2. Scope and current status
This policy covers the GameGigs landing-page preview, its information pages and its built-in reward calculator. The intended brand domain is gamegigs.app; this version is prepared for hosting on Netlify.
Creator account management, campaign submissions and payouts are not connected yet. When the waitlist is enabled, clicking “Join” opens an email signup form with double opt-in. A waitlist subscription does not create a creator account. This policy does not cover unrelated SPG apps or the independent games and social platforms mentioned on this website.
3. Website delivery and technical data
To deliver the website, its hosting infrastructure receives connection information such as your IP address, request time, requested URL and browser-related request headers. Such data may also be processed for security and troubleshooting.
The intended basis for necessary website delivery and security is our legitimate interest in operating a functional, secure service under Article 6(1)(f) GDPR. This version is delivered through Netlify and uses Netlify Functions and Blobs. The contracting hosting entity, processing locations, applicable transfer safeguards and technical-log retention periods are still being verified for the launch version.
The actual processor agreements and technical-log retention must be verified for this deployment; no fixed hosting-log period is promised here.
4. Landing-page variants, cookies and click measurement
The landing page randomly displays one of six headline variants. Its current implementation uses a first-party cookie named gg_netlify_v1 and a browser-storage entry named gamegigs-netlify:creator-headlines-v4 to keep a browser’s assigned variant consistent. These identifiers are specific to the Netlify deployment.
The signed assignment contains a random browser identifier, the experiment and variant IDs, an expiry time and a test marker. The cookie lasts up to 90 days and is restricted with Secure, HttpOnly and SameSite=Lax attributes. The browser-storage entry does not automatically disappear after 90 days, although the signed assignment expires; it can remain until replaced or cleared.
Our own analytics database records the experiment ID, random browser ID, assigned variant, first recorded view time and, if you click a Join button, the first recorded click time and button location. Duplicate views and clicks from the same assignment are not counted as new visitors or conversions. The analytics event records do not include your name, email address, form contents or IP address. Technical hosting logs are separate.
The purpose is to compare headlines and understand which ones lead to Join clicks. A Join click is not a completed signup. Explicit variant-preview links are excluded from these measurements. The report is restricted to the site owner.
Open implementation point: this measurement currently starts automatically on ordinary landing-page visits. There is not yet a consent preference panel. The lawful basis and any required consent under GDPR and applicable device-storage rules must be settled and implemented before public launch. This draft does not treat continued browsing as consent.
Retention: assignment tokens expire after 90 days. The current analytics database does not yet have an automated deletion schedule. A defined server-side retention and deletion process must be implemented before launch; clearing browser storage alone does not delete existing server records.
You can remove the cookie and browser-storage entry through your browser settings. A later ordinary visit may create a new assignment. For a request concerning stored experiment data, contact us; a random browser identifier may be needed to locate a record. We will not request unnecessary identifying information simply to identify you.
5. Reward calculator, fonts and external links
The calculator computes illustrative rewards in your browser. On ordinary, measured landing-page visits, we separately record when you first open it, changes to its four inputs, example selections and clicks on its own Join button. Recorded settings are campaigns per week, reward per video, qualifying players per week and reward per player, together with calculated weekly and monthly estimates. Changes are grouped after a short pause rather than recording every slider movement.
These events are linked to the random browser identifier and assigned headline variant described above, with a calculator-visit ID, event ID and server timestamp. A calculator Join click stores an immutable snapshot of the settings at that moment. Other Join buttons do not attach calculator settings to their clicks. The purpose is to understand calculator use and whether its own CTA is used; these events are reported separately from other landing-page Join clicks. Preview links are excluded.
When waitlist signup is enabled, confirmed subscriptions are attributed to the variant and original signup button. A signed reference connects only calculator-origin subscriptions to their original calculator click. A click or form submission alone is not a confirmed subscription. Calculator event records currently have no automated deletion schedule. The legal-basis, consent and retention review described in Section 4 also applies to these events.
Fonts, images, scripts and styles are served with this website. The page does not embed third-party social feeds or advertising pixels. If you follow an external link, the destination processes data under its own policy. Email links open your email application and send nothing until you choose to send a message.
6. Contacting us
If you email us, we process your email address, any name you provide, the message and relevant correspondence to handle your request. Please avoid sending passwords, payment credentials or unrelated sensitive information.
The basis is Article 6(1)(b) GDPR for requests related to entering into or performing a contract, and otherwise Article 6(1)(f) GDPR, our legitimate interest in responding to enquiries. We retain correspondence for as long as needed to deal with the matter and, where applicable, for statutory retention or legal-claim purposes.
7. Recipients and international processing
Necessary data may be processed by website infrastructure and email-service providers, authorised personnel handling your request, and public authorities where required by law. We do not sell personal data.
Where a provider acts as a processor, the applicable processing arrangements must be documented. Any processing outside the European Economic Area requires an applicable basis under Chapter V GDPR, such as an adequacy decision or appropriate safeguards. The specific providers, countries and safeguards for the GameGigs launch are open review items; no particular provider certification is asserted by this draft.
8. Your rights
Subject to the applicable legal conditions, you may request access, correction, erasure, restriction of processing and data portability. You may object to processing based on legitimate interests for reasons relating to your situation. Where processing is based on consent, you may withdraw that consent at any time without affecting the lawfulness of earlier processing.
Send requests to support@scalable-performance-group.de. You may also complain to a supervisory authority, particularly in the country where you live, work or believe an infringement occurred.
The supervisory authority identified in SPG Studio’s policy is:
Die Landesbeauftragte für den Datenschutz NiedersachsenPrinzenstraße 5
30159 Hannover
Germany
9. Security and future services
The preview is served over HTTPS. Access to the analytics report is restricted. These measures reduce risk but cannot guarantee absolute security.
The current landing page does not make automated eligibility or payout decisions. Before we introduce accounts, submissions, referral verification or payouts, we must provide an updated policy explaining the additional data, purposes, lawful bases, recipients and retention periods. The date above identifies this version.
Netlify waitlist deployment
This deployment uses Netlify Functions and private Netlify Blobs storage for headline experiments, calculator events and the launch waitlist. Its analytics records are separate from the earlier ChatGPT Sites preview.
When enabled, the waitlist stores your selected game categories, intended social platforms or new-account preference, phone platform, email address, the wording and time of your consent, confirmation status, and—where available—the headline variant and button or game tile through which you signed up. Game tile clicks are counted per visitor and tile; a tile does not select a game campaign or prefill your preferences. Only a signup through the calculator button includes a reference to that button’s recorded settings. Joining the waitlist does not create a creator account. Resend processes the email address and message content to deliver confirmation, welcome and getting-started emails. We store delivery status and, if you explicitly confirm it, your interest in an early test gig. Merely opening an email link does not register interest.
The purpose is to confirm your requested waitlist subscription, send the early-access, new-gig and getting-started emails you requested and use your selections to match you with relevant games and campaigns. Answers remain in your browser’s memory until you submit the form; they are not sent as separate analytics events or shared with publishers by this form. You may withdraw at any time through the link in your welcome email or by contacting support. Withdrawal removes the email address, preferences, stored email jobs, early-gig interest and attribution from the active waitlist record and retains a pseudonymous suppression key to prevent further sends. Confirmation links expire after 24 hours. Pending entries and analytics records currently require operator-managed deletion; a retention schedule and processor agreements must be finalised before public launch.
For abuse prevention, a keyed hash of the connecting IP address is used for short-window request limits; raw IP addresses are not stored by this application. Hosting and email providers may keep separate technical delivery logs. Existing consent and legal-basis review requirements in this draft still apply.
Publisher enquiries
When you submit a pilot enquiry, Netlify Forms processes your name, work email, studio or publisher name, game or studio URL and optional message on our behalf. We use these details to respond and discuss a potential pilot. This enquiry is separate from the creator waitlist and does not subscribe you to marketing emails. Netlify provides form storage and spam filtering. We review enquiries in the Netlify dashboard; access is restricted to authorised team members. Contact support to request deletion. The retention schedule and processor arrangements described in this draft must be finalised before public launch.
