RLC Creator Network
Privacy Policy
How RLC handles your information, authorized platform connections and privacy requests.
Last updated November 2, 2026
1. Who operates the Network
Rick Lagnese Communications LLC (RLC), based in the United States, operates the RLC Creator Network and is responsible for the information described in this policy. This policy explains how we handle your information when you use the Network or send a website inquiry. Contact rick@ricklags.com with privacy questions or requests.
2. Information you submit
Account registration and sign-in use your email address and authentication details. Google sign-in can supply account identity information through the sign-in service. Your Network profile can include your display name, biography, social or website links you provide, and country for campaign eligibility.
Creator applications include your contact email, display name, optional Discord handle, geographic region, games or genres, and selected content categories. Geographic region is separate from country-based campaign eligibility. Previously submitted free-text answers may remain in older application records. Saved drafts can contain the partial answers you enter before submission.
IGA applications include name, email, Discord handle (N/A is accepted), the social profile links and paired audience counts you supply, your statement about supporting independent games, an optional biography and an optional other link. These submitted counts are not automatically verified platform metrics.
Member activity can include game or key requests, request notes and decisions, assigned-key records, coverage URLs and notes, competition video-proof links and notes, reviewed scores, and Ask RLC messages and replies. We also store membership status, review decisions, timestamps and operational records needed to manage these activities.
The separate developer and publisher inquiry forms collect the contact, studio or company, game or company link, requested support, budget, readiness, timing and other answers shown on those forms. These inquiries are stored in private Google Sheets. Earlier IGA applications held in Sheets remain separate from Network applications and are not automatically linked to accounts.
3. Authorized platform information
You choose whether to authorize a platform connection. We use information from that platform to identify the account or channel you authorize, connect it to your Network profile and check continued access when needed.
Twitch connections use your account ID, login name, display name, profile image and profile link. YouTube connections use read-only access to your channel ID, title, handle, thumbnail and channel link. A connection confirms authorized access, not exclusive ownership; signing in with Google is separate from connecting a YouTube channel.
Kick connections use your account ID, name and profile image. Kick may also return your email, but we do not save it as part of the connection. TikTok connections and TikTok sign-in use your platform ID, display name, avatar, username and profile link. Instagram connections use the account ID, username, name and profile image of the one Instagram account you choose to share, plus a profile link built from the username.
We do not collect platform follower, subscriber or view totals, videos, private messages or posted content through these connections. Audience counts you enter in applications are separate from connected account information. These connections do not give RLC permission to publish through your account.
4. How information is used
We use submitted and authorized information to provide sign-in and profile features, review each membership independently, verify connected account access, assess campaign eligibility, administer requests and assigned keys, review coverage and competition entries, respond to support messages and protect the service from misuse.
RLC administrators can review applications and relevant member activity. Other members do not have access to your private account, keys or support tickets. A reviewed competition leaderboard can show the display name and score included in an administrator-approved result.
Providing a coverage or proof link allows RLC to review the linked material. A link may lead to a public third-party page governed by that site's own privacy practices.
5. Storage and service providers
The site and Network use Lovable hosting and Lovable Cloud for account authentication, application data and server-side processing. RLC's configured managed email service handles transactional confirmations and owner notifications. Google Sheets stores the separate developer and publisher inquiries and retained historical Sheet records. Connected platforms process authorization and API requests under their own policies.
Platform access and refresh tokens are encrypted and stored on the server, not displayed in member pages. We also store platform identifiers, connection status, permissions granted and connection dates. Required browser storage keeps you signed in, and short-lived cookies help secure platform connections.
Access controls restrict private records to authorized users and RLC administrators. No system or communication is entirely risk-free. Hosting and service providers may also process technical request and diagnostic information to operate and protect the service.
6. YouTube API Services
The Network uses YouTube API Services for the read-only channel connection described above. Use of that connection is subject to the YouTube Terms of Service. Google's handling of information is described in the Google Privacy Policy.
You can revoke RLC's Google or YouTube authorization through Google account permissions. Revoking provider permission and disconnecting in the Network are different controls. For deletion of retained RLC records, contact rick@ricklags.com.
7. Disconnecting and deletion requests
For TikTok, Disconnect asks TikTok to revoke authorization, then removes the local connection information and encrypted tokens after TikTok confirms success. If revocation cannot be confirmed, we retain that information, pause further access checks and show an error so you can retry or contact RLC. We retain a record of your policy agreement.
For other platforms, Disconnect removes local connection information and encrypted tokens but does not revoke the platform's permission. Disconnect does not delete your platform account or erase earlier application information, membership decisions, support messages, campaign records or backup copies.
To withdraw the platform's permission as well, use its connected-app or account-permission settings. For YouTube and Google, use the Google account permissions link above. If access has expired or been revoked, you may be asked to reconnect when access is checked.
You can update available profile fields yourself and request correction or deletion of other RLC-held personal information by emailing rick@ricklags.com. We may need to verify that the request relates to your account. Account deletion is handled by request, not an automatic account-erasure button; older Sheet records also require review.
8. How long information is kept
We keep information to operate accounts and memberships, review applications, manage campaigns and support, maintain security and resolve outstanding requests. How long it is kept depends on the record and its purpose; we have not set a fixed deletion period for all records.
Records and backups are not automatically erased when you stop using the Network or disconnect a platform. Deletion requests require review of any continuing need for the records and the service providers' backup retention. Contact RLC to discuss information connected to your account.
9. Service communications
Account confirmation and recovery messages support sign-in. After a successfully saved IGA application, the Network can send a receipt confirmation to the saved email address and notify RLC. Developer and publisher inquiries have their own post-save confirmations and owner notifications. RLC may follow up on an inquiry, application or support request by email or, where supplied, Discord.
A receipt is not membership approval. These service communications are separate from marketing. Registering, connecting a platform or applying does not subscribe you to a mailing list or count as consent to marketing.
10. Optional website analytics
On ricklags.co, optional Google Analytics 4 and Microsoft Clarity are used only after you accept analytics. Neither runs in the website preview or on sign-in, password-reset or Network account pages.
Google Analytics measures page visits without address query details and records that a developer or publisher inquiry succeeded. It does not receive submitted answers, contact details or submission identifiers. IGA applications are not recorded as inquiry-success events.
Microsoft Clarity measures interactions and records sessions on selected public pages. It does not record inquiry or application forms, sign-in or Network pages, the Creators page or these policy pages.
You can accept or decline optional analytics and change your choice through Privacy preferences in the footer. Your choice is stored in your browser. Withdrawing consent stops optional tracking and attempts to remove its cookies. Storage needed for sign-in and secure platform connections is separate from optional analytics.
11. Questions and policy updates
Contact rick@ricklags.com for access, correction, deletion or privacy questions. This policy may change when the service or its data flows change. The date at the top identifies the current version.
