Necessary cookies
Required for sessions, security, language and platform functionality.
This Privacy Policy explains how CrewMaster S.R.L.S. processes personal data relating to the website crewmaster.net, accounts, integrations with external platforms, and services for creators and communities, pursuant to Articles 12, 13 and, where applicable, 14 of Regulation (EU) 2016/679 (GDPR).
For processing activities for which it independently determines the purposes and essential means, the controller is CrewMaster S.R.L.S., VAT number 01886090883, with its registered office at Via E. Giunta 42, 97016 Pozzallo (RG), Italy.
Contacts: [email protected] (privacy), [email protected] (legal), [email protected] (abuse).
This notice applies to website visitors, registered users, creators, people who link external accounts or access community benefits, and people who request assistance or submit reports.
Third-party services (such as Twitch, Telegram, Discord and Stripe) also apply their own privacy notices to processing activities for which they are independently responsible.
Depending on the activities actually requested, the following data may be processed:
Data may be provided directly by the data subject, received from login providers or connected platforms through APIs, events and webhooks, or generated by CrewMaster's technical systems while providing the services.
Supported authentication and integration platforms include, depending on active features, Twitch, Google, Microsoft, Discord, Steam, Instagram, TikTok, Kick, YouTube and Patreon; community features also include Telegram. The type of data obtained varies according to the permissions granted and the APIs available.
Where membership information comes from an external platform rather than directly from the data subject, it is used within the limits of the purposes and conditions described in this notice.
Depending on the processing activity, CrewMaster relies on the following legal bases under Article 6 GDPR:
The classification of processing activities that may be carried out on behalf of a creator depends on the actual allocation of responsibilities, as explained in the section on creators. A single legal basis is not applied indiscriminately to all operations.
Data strictly necessary for login, subscription verification, linking a platform or billing is requested only for the relevant features. Users may choose which integrations to authorize; failure to provide required information may prevent use of the relevant feature without necessarily preventing use of other available features.
A connection to an external platform may be revoked at any time in accordance with the provider's or CrewMaster's procedures.
CrewMaster uses external providers' authentication and authorization systems and does not store local passwords for these accounts. Access and refresh tokens needed for integrations are encrypted and accessible only to authorized backend components; they are not shown to creators.
Users can disconnect integrations without necessarily deleting their entire account. Upon disconnection or revocation, the affected tokens and links are deleted; where technically possible, CrewMaster also requests revocation from the external provider.
Authorizations and terms of use of external accounts remain subject to the respective providers' rules.
CrewMaster verifies subscription status through endpoints/APIs, events (including Twitch EventSub) and periodic checks, depending on the integrations available.
The creator selects the group or community and access requirements; the system automatically verifies the configured requirements and may grant, maintain or revoke access to restricted groups, servers or content. Failure to meet the requirements may result in loss of access to the corresponding benefit.
Creators may view members' public usernames within the limits of available features, but cannot see restricted internal identifiers or OAuth tokens. Within the features described, CrewMaster does not offer creators the ability to export member lists or send individual messages and does not store the ordinary content of community chats.
If a verification result appears incorrect, support may be contacted to request an investigation. The access checks described are not presented as commercial profiling processes.
CrewMaster uses YouTube API Services in the YouTube features that are actually enabled. Depending on the permissions granted and the features requested, it may access channel or account identifiers, available profile data, membership information (including status, level and any expiration date), as well as the technical data and tokens required for authorization. Any lists imported by the creator through CSV files are separate from data obtained directly through APIs.
YouTube data is used to connect the channel or account, verify subscription requirements, manage access to restricted groups and content, and provide the YouTube features enabled by the creator. Data is accessible only to authorized components and, within the scope of the features selected, to the channel owner or persons authorized by them; it is not sold or used for behavioral advertising.
Use of features integrated with YouTube is also subject to the YouTube Terms of Service. Google’s processing is governed by the Google Privacy Policy. CrewMaster applies the specific use and retention conditions set out in the relevant Developer Policies to data obtained through YouTube API Services.
Users can disconnect YouTube in CrewMaster settings, where available, or revoke permissions through the Google third-party access management page. To delete YouTube data held by CrewMaster, users may also write to [email protected]. Revoking access or deleting data held by CrewMaster does not delete content or data stored directly by YouTube.
For data obtained through YouTube API Services, any stricter deadlines under YouTube rules take precedence: where applicable, API information subject to refresh must be updated or deleted within 30 days; data obtained through authorization must be deleted within the prescribed deadlines following revocation or a deletion request, generally within 7 days. These specific limits take precedence over the general periods stated in the “Data retention” section insofar as they concern the same API data.
CrewMaster acts as an independent data controller for activities whose purposes and essential means it determines: platform account management, authentication and connections required for the direct service, security, support, payments, invoicing and legal compliance.
The creator determines the rules, purposes and recipients of their community and the content they publish; for processing carried out independently in groups, websites, pages and external communications, they act as a separate data controller where the relevant conditions are met.
For specific operations performed on behalf of a creator acting as controller, such as the technical application of membership requirements and access rules configured by that creator, CrewMaster may act as a data processor under Article 28 GDPR. This role concerns only the processing actually entrusted to it, not all CrewMaster activities.
Where a controller–processor relationship exists, the respective obligations must be governed by a Data Processing Agreement (DPA) or another instrument compliant with Article 28 GDPR, defining the subject matter, duration, purposes, data categories, documented instructions, security measures, use of subprocessors and assistance with data subjects’ rights. The applicable terms may be requested from [email protected].
The classification of roles depends on the operations actually performed and the decisions of the parties involved. Creators remain responsible for the lawfulness of the data and content they decide to process independently.
CreatorVault allows creators to upload and share content with their communities, subject to availability periods and conditions configured by the creator.
When a creator deletes a file, CrewMaster arranges its removal from production systems and affected backup copies through an automated procedure. Content is also removed when the account is deleted or the relevant service ends, in accordance with applicable technical procedures.
CrewMaster does not systematically pre-screen all uploaded content, without prejudice to security, moderation and report-handling activities required under applicable rules.
Creator pages, such as crewmaster.net/@CREATOR, may be made public, accessible without logging in and indexable by search engines. Creators determine what content is made public and must avoid publishing third parties' personal information without an appropriate legal basis.
Checkout and payment processing for paid plans are handled through Stripe. CrewMaster does not store full card numbers or payment methods in a form that can be used to make direct charges.
CrewMaster may process data necessary to identify the customer and transaction, verify payment status, manage the plan and comply with tax and accounting obligations.
Stripe may process payment-related data independently or on behalf of the customer, in accordance with its roles and contractual and privacy documents.
CrewMaster uses an internal statistics system that stores only aggregated results, such as the total number of visits to a page, without storing individual users' browsing histories in its reports.
According to the stated configuration, CrewMaster does not use Google Analytics, Google Tag Manager or Meta Pixel. Technical cookies and any tools associated with external features are described in the Cookie Policy.
The absence of a consent banner is based on the exclusive use of technologies exempt from consent. Any non-technical tools or embedded content requiring consent must be activated only after valid consent has been obtained.
CrewMaster does not sell users' personal data or make it available to third parties for behavioral advertising. The exchange of information necessary for requested integrations and payments does not constitute a sale of data.
To the extent necessary, personal data may be processed by server infrastructure and connectivity providers, Cloudflare for network and security functions, Stripe for payments and checkout, connected platforms and authentication providers, as well as authorized persons or professionals in fulfillment of legal obligations.
A list of relevant providers and information about the corresponding safeguards may be requested by writing to [email protected]. Infrastructure details that could compromise system security are not disclosed.
CrewMaster uses dedicated servers rented and managed by the company, located in Germany and Finland, with redundant systems. Its databases use MySQL and MongoDB and are not provided through third-party managed cloud database services.
The infrastructure employs disk encryption, HTTPS connections, access controls and network protections, including through Cloudflare. The fact that databases are located in Europe does not mean that all processing by third-party services takes place exclusively within the European Economic Area.
When providing the services, some providers and connected platforms, including Stripe, Cloudflare and authentication providers, may process or transfer data to countries outside the European Economic Area, including the United States.
For transfers subject to the GDPR, applicable mechanisms include European Commission adequacy decisions, mechanisms such as the EU-U.S. Data Privacy Framework for participating organizations, and/or Standard Contractual Clauses, depending on the provider, service and specific transfer operation.
To find out which mechanisms apply to a particular service or to obtain information about the relevant safeguards, write to [email protected].
Retention periods and criteria vary by data category:
Deletion requests are handled through systems that enable data associated with the data subject to be identified and removed, including membership history records, subject to exceptions provided by law.
CrewMaster adopts technical and organizational measures proportionate to the risks: encryption at rest on storage media, token encryption, HTTPS, restrictions on administrative access, additional device and network controls, backups and redundancy.
Procedures are in place to detect, contain, document and assess security incidents, and to notify the Italian Data Protection Authority and data subjects in the cases provided for in Articles 33 and 34 GDPR. No IT solution can guarantee absolute security.
Where provided for by the GDPR, data subjects may request access, rectification, erasure, restriction, portability and objection to processing, as well as withdraw consent where processing is consent-based. They may also lodge a complaint with the Italian Data Protection Authority (Garante per la protezione dei dati personali) or another competent authority.
Requests can be sent to [email protected]. CrewMaster normally responds within one month of receipt, subject to extensions and other provisions of applicable law.
Where a request concerns processing carried out by a creator independently of the platform, it may also be necessary to contact that creator.
Access to CrewMaster's free services is intended for users who meet applicable age requirements, generally at least 14 years old in Italy, and comply with the rules of the authentication platforms used.
To purchase paid plans independently, users must have the legal capacity to enter into a contract. At checkout, CrewMaster requires a declaration of legal age and checks the consistency of tax information already requested for billing. If the Italian tax identification code indicates that the purchaser is a minor, the purchase is blocked and the person may contact support to assess the involvement of a parent or legal representative.
The age threshold of 14 established under Italian law for specific cases of digital privacy consent does not amount to legal capacity to enter into paid contracts independently.
CrewMaster may send technical, administrative and security communications needed to operate the service. According to its currently stated configuration, it does not send marketing newsletters or use user data for advertising profiling.
If promotional communications are introduced in the future, the necessary information will be provided and the applicable legal basis used, allowing the relevant rights to be exercised.
Automated membership checks may affect access to specific benefits, groups or content configured by the creator. Conditions depend on the service rules and the subscription status communicated by connected platforms.
Support may be contacted regarding disputes over incorrect checks. Any automated decisions subject to Article 22 GDPR must be assessed in light of the actual features and their effects.
CrewMaster may update this Privacy Policy to reflect changes in legislation or services; the date shown above identifies the version. Changes will be communicated when required by law.
For information and requests: [email protected].