Privacy policy

Last updated: October 10, 2026 · Platform policy

1. Information we collect

BloxAds sign-in stores an account identifier, display name, email and a salted password hash. You may add a studio name, gaming channel URL, payout method and payment contact. Optional profile fields include a profile photo, biography, country or region, time zone, website and Discord username. Profile photos are private to your own workspace. Campaign records include briefs, source materials, published video links, publication dates, review notes, recorded eligible views, approved earnings and transfer references.

Tracking records include Roblox Share Links, report dates, manually entered visit and player counts, evidence links and verification notes.

The contact form stores the name, email, request category and message you submit, including any optional studio, game URL, estimated campaign budget, launch window and creative-format details, together with your signed-in account identifier and submission time.

2. How information is used

Information is used to operate accounts, review creator participation, manage campaigns, calculate approved earnings, coordinate manual payments and review support or privacy requests. It is also used to enforce campaign limits, prevent duplicate submissions and keep operational audit records.

3. Who can see your records

Advertisers can view submissions and results for their own campaigns. Creators can view their own submissions, earnings and payout requests. Administrators can view campaign operations, creator applications, payment contacts and contact requests. Other creators cannot access your private earnings or payout details.

Campaign owners and administrators can view tracking evidence and verification notes. Joined creators can view their assigned Share Links and reported counts. A campaign case study can be published with the studio’s permission and includes the studio, game, summary, approved clip results, budget and any campaign total acquisition report. Private evidence links and creator contact details are excluded from public stories.

4. Uploaded materials

Source files are stored with the site's hosting provider. Access is restricted to the file owner, administrators and creators who joined the linked campaign. A public source link you supply may have its own sharing settings outside BloxAds.

5. Service providers

The site uses its hosting providers for the application, database and uploaded files. BloxAds manages sign-in on its own server. BloxAds does not collect card numbers or initiate transfers. You provide payment contact details for separate manual payout coordination.

6. YouTube examples

Shorts thumbnails are served by this site. When you choose to play a Short, an embedded YouTube player loads and YouTube may receive information such as your IP address, browser details and playback activity. The player uses YouTube's privacy-enhanced embed domain. You can also choose to open the video on YouTube directly.

7. Cookies and advertising

The workspace uses functional sign-in and navigation state. No advertising pixels, heatmaps, session replay or behavioral advertising integrations have been added. We do not sell personal information. See the cookie policy for the current categories.

Email delivery and preferences

When SMTP is configured, our email provider processes your email address and account messages to deliver verification links, password recovery links, welcome messages and security notices. We store hashed, expiring verification and recovery tokens. News messages are optional and require your opt-in; you can change your preference in My profile or unsubscribe through any news email. We store delivery status for news emails. Account service emails remain enabled even when you unsubscribe from news. No email tracking pixels are added.

8. Retention and requests

Account, campaign, support and payment records remain in the workspace for its operation and reconciliation. Detailed retention schedules and deletion controls will be finalized before external launch. Use the contact form with the Privacy request category to ask about access, correction or deletion. Requests are reviewed by the operator; sending a request does not automatically delete records.

9. Account security

We store salted password hashes, hashed session tokens, session activity times and temporary anti-abuse counters. When you enable two-factor authentication, the authenticator secret is encrypted on the server; recovery codes are stored as hashes and can each be used once. You can review and revoke your sign-in sessions in My profile.

Keep your sign-in account secure and use only channels and payment details you control. Administrative decisions are checked on the server and records are scoped to the relevant user or campaign.

10. Updates and contact

The date above identifies this version. Material changes to the service should be reflected here. Questions about this notice can be sent through the contact page.

Team access and website publishing

We store registered accounts’ team roles and access status so campaign managers and administrators receive the appropriate permissions. Suspension preserves existing campaign records and approved rewards. Administrator changes are recorded in the activity log.

Images uploaded through Website content are public website media, separate from private campaign source files. Public page copy and credited video examples are stored as website configuration.