Skip to content
BENO74
Privacy

BENO74 STUDIOS

Tile Wave privacy policy

This policy covers the Tile Wave iOS and Android game. Optional cloud features and development-only measurement are explained separately from the current production configuration.

Last updated and effective: September 11, 2026

On this page

  1. Who operates Tile Wave
  2. Playing and saving on your device
  3. Optional accounts and cloud data
  4. Firebase configuration and analytics
  5. Advertising and UMP privacy choices
  6. Purposes and service providers
  7. Retention
  8. Request account or data deletion
  9. International processing and security
  10. This policy page and contacting us
  11. Policy updates

Who operates Tile Wave

Tile Wave is operated by Eyal Arviv, using the brand BENO74 STUDIOS. For the processing described here, Eyal Arviv is the operator and data controller. Contact privacy@beno74.com.

Playing and saving on your device

You can play Tile Wave and work with local level drafts without signing in. The app stores progress, settings and preferences, level drafts and related game records on your device. When you sign in, it also stores an authentication session so it can reconnect to cloud services.

Removing local app data can remove local progress, drafts and stored sessions. It does not automatically delete an account or copies already stored in the cloud.

Optional accounts and cloud data

Tile Wave uses Supabase for authentication and its cloud database. If you create an email/password account, Supabase processes your email address, password for authentication, account identifier and session information. Verification and password recovery use email.

The app also supports starting Google sign-in, and Apple sign-in on iOS, where the provider is configured and available. These providers may supply identifiers, email addresses and profile details. An Apple private-relay address may be used if you choose Hide My Email. Separate provider accounts are not automatically linked by Tile Wave.

Cloud features store account/profile records, level progress and preferences. If you use shared Cloud Drafts, the database also stores workspace names, membership and roles, invitation codes, draft names and content, playable level data, authorship identifiers, versions and timestamps.

Workspace members with the relevant permissions can access shared drafts. Sharing a workspace is different from keeping a local draft private. Draft deletion may first mark a draft as deleted rather than immediately erase its database record.

Supabase and authentication providers also process technical connection and security information, such as IP addresses, timestamps and session activity, to operate and protect these services.

Firebase configuration and analytics

Production versions use Firebase infrastructure for Remote Config, which retrieves settings that control app behavior, including advertising configuration. Google processes a Firebase installation identifier and technical request information to provide this service. Configuration can be cached on your device; the app uses local defaults when a fetch is unavailable.

Gameplay analytics collection is currently disabled in the production configuration. The presence of Firebase or Remote Config does not mean production gameplay analytics is enabled.

Separately configured development versions can send Firebase / Google Analytics 4 events about feature use, level starts and completions, gameplay mode, app version and aggregated performance. Google may also process its own app-instance identifiers, lifecycle events, device information and approximate location derived from the network connection.

Custom analytics exclude passwords, authentication tokens, free-form user text, full level or board contents and custom advertising identifiers. There is no separate app-level analytics-consent control today. Production analytics requires a separate review of its purpose, disclosure and privacy choices before it is enabled; UMP advertising permission does not enable it.

Advertising and UMP privacy choices

Production ads are currently disabled. Tile Wave includes Google AdMob and User Messaging Platform (UMP) infrastructure, but the current production runtime resolves no ad units and does not start the advertising consent flow. Remote Config alone cannot override that production runtime restriction.

In test or other ad-enabled versions, the app requests UMP privacy information and shows any required message. The Mobile Ads SDK can initialize only when the advertising configuration allows it, ad units are available and UMP reports that ads may be requested. Development ad requests use Google test units.

When required by UMP, Settings → Ad choices → Manage reopens Google’s privacy-options form. The entry is absent when UMP does not require it or advertising is disabled. The app uses UMP’s stored choices and checks the updated decision after changes. Declining consent does not block the core puzzle game.

If these services are active, Google may process connection and device information, consent choices, ad interactions and diagnostics for ad delivery, measurement, compliance, security and fraud prevention. Personalization depends on the relevant permissions and choices; permission to request an ad is not the same as consent to personalization.

Current iOS builds do not request Apple App Tracking Transparency permission or access the IDFA. The iOS Firebase analytics integration excludes IDFA support. We will review disclosures and privacy controls before enabling production ads or changing tracking behavior.

Purposes and service providers

Information is processed to operate the game, authenticate users who choose cloud features, save and synchronize progress and preferences, support shared drafts, deliver configuration, maintain security, and respond to requests. Development analytics helps evaluate gameplay; advertising services operate only as described above.

  • Supabase: authentication and cloud database services. Supabase privacy policy.
  • Google Firebase and Google Analytics: Remote Config and analytics in the versions described above. Firebase privacy information and Google privacy policy.
  • Google AdMob and User Messaging Platform (UMP): the advertising and consent features described above. How Google uses information from apps and sites.

When you choose provider sign-in, Apple or Google processes information for authentication under its own terms. Information may also be disclosed where required by law or needed to address abuse or protect the service.

Retention

Local information stays on your device until replaced or removed. Account and cloud information is stored separately to support ongoing cloud features. Signing out or uninstalling is not an account-deletion request. Shared drafts can include records needed by other workspace members.

The current app has no fixed automatic account-expiry schedule. Database records, soft-deleted drafts, operational logs and backups may have different retention lifecycles. Google manages installation and other service data according to the relevant service settings and processes. Support correspondence may be retained to resolve your request and maintain necessary records.

Request account or data deletion

To request deletion of your Tile Wave account and associated cloud data, email privacy@beno74.com with the subject “Tile Wave account and data deletion request”. You can make this request without reinstalling the app. Send it from your account email where possible, or explain which sign-in method you used. Never include a password or authentication token.

There is currently no in-app account-deletion button. We may need to verify account ownership and clarify what you want removed. Shared workspace records and drafts may require additional handling because other people use them. If security or legal reasons require retention of particular records, or backups take longer to expire, we will explain the relevant limitations in our response.

You can also request access or correction. Depending on the law that applies, you may have rights to portability, restriction, objection, withdrawal of consent where relevant, and complaint to a data-protection authority.

International processing and security

Our service providers operate internationally. Information may be processed outside your country, including in the United States, under the providers’ applicable processing terms. Their privacy information explains their transfer arrangements.

The apps use encrypted network connections to the cloud services and access controls for cloud records. No device, network or storage system can be guaranteed completely secure.

This policy page and contacting us

This page contains no advertising, analytics tags, tracking pixels or consent forms. You can read it without signing in, accepting cookies or enabling JavaScript. Our website hosting providers process ordinary connection information, such as an IP address and requested URL, to deliver and protect the site.

If you email us, we receive your email address, message and any attachments you choose to send. We use these to respond to support and privacy requests. Please do not send passwords or authentication tokens.

Policy updates

We will update this page and its date when these practices change. Material changes will be communicated as required. New account, analytics or advertising features may need revised disclosures and privacy choices before release.

For questions about Tile Wave, email privacy@beno74.com.

© 2026 BENO74 STUDIOS

Studio homeAll privacy policies