Rugberry is provided by BRRY Dijital Teknoloji Anonim Şirketi, the controller responsible for the processing described here. For privacy questions and requests, contact info@brry.co. This notice covers the Rugberry Mac app and this privacy page, including local images and settings, purchases, support and optional usage analytics. Features and controls described below depend on the app version you use.
Rugberry places a visual cover over part of your desktop. It does not browse, move, organize or delete the files beneath that cover. You do not need to create a Rugberry account.
Wallpaper, photos and local settings
Invisible reads the current wallpaper image locally to match the cover to your desktop. If access is needed, you can select the image in a macOS file picker. Rugberry may save a read-only permission bookmark so it can read that selected wallpaper again. It does not capture the screen to obtain the wallpaper.
You can preview an included wallpaper or a photo you choose. Previewing does not change the desktop wallpaper. If you confirm Set as desktop wallpaper, Rugberry saves a static image copy in its local app storage and asks macOS to use it on the selected display. That wallpaper remains after Rugberry quits; change it in macOS System Settings when you want a different one. Rugberry does not upload these images, their filenames or their paths, or include them in usage analytics.
Rugberry saves settings such as appearance, placement, completed rug shape, interaction preferences, onboarding state and the analytics choice locally on your Mac. macOS may also save the control window's position. Unreadable settings may be kept locally for recovery.
Locally enabled diagnostics can create reports, synthetic rug previews and rug simulation recordings, including interaction coordinates and technical timing information. Rugberry does not automatically upload those local outputs. Review them before choosing to share them with support. These local app diagnostics are separate from the purchase SDK diagnostics described below.
Purchases and access
Apple's App Store and RevenueCat process information needed to verify and restore purchases and existing trials, verify complimentary access, and provide purchase reporting. This includes an app-specific purchase identifier, product and transaction identifiers, receipts or signed transaction information, purchase dates and access status. RevenueCat requests also include app/SDK/operating-system versions, machine/platform type, up to three preferred locales, available store-country information and technical operating-state flags. The SDK can report the system tracking-permission status. Receiving services also see network connection information such as IP address. Rugberry automatically checks purchase entitlements to decide which app features are available.
Apple handles payment details. Rugberry does not receive your payment-card information or require your email address to use the app. The purchase identifier is separate from the optional analytics identifier. Turning off usage analytics does not disable purchase verification or purchase reporting.
The purchase SDK stores local identity, customer-information and attribute caches. Its technical diagnostics can persist events while their enablement is being determined and can upload them if enabled by the effective SDK configuration. Those diagnostics can include event/session identifiers, timestamps, request timings and results, error and endpoint information, product information, and transaction identifiers. They are separate from PostHog usage sharing.
Email support
Contact Support opens an editable draft inside Rugberry. It initially contains the RevenueCat Support ID, app version and build, macOS version and access status. You can remove or change these details before sending.
Rugberry does not send the email automatically. You choose whether to open the draft in an email app or copy the edited draft to the clipboard for manual email. Closing the support window discards its in-app draft; copied clipboard contents and drafts opened in an email app or webmail are handled separately and are not removed by closing that window.
If you send a message, we receive your email address, message and any details or attachments you choose to include. We use them to respond and investigate the issue. Keeping the Support ID in the email lets us associate the message with the relevant purchase record. Email providers process the message to deliver and store it.
Optional usage analytics
Rugberry uses PostHog to understand feature use and improve the app. Usage sharing is on by default when no preference has been saved, including after an update. Events can be sent before you change that setting. A saved Off choice remains off after an update or relaunch.
When sharing is on, Rugberry sends selected app interactions and outcomes: app opens, controls and onboarding use, appearance and reveal actions, purchase/trial/restore outcomes, support-screen views, Invisible introduction views and dismissals, What's New replays, first preview interactions, successful Invisible activation and wallpaper-access-needed events.
Events include a random app-specific identifier, app version and build, event/interface version information, the app environment, and a broad access status such as paid, complimentary, trial or unpaid. Where relevant they include the chosen Textile or Invisible appearance, the screen or surface used, and fixed feature/version labels. PostHog receives events when requests reach its service. The identifier stays the same across launches while sharing remains enabled; it is pseudonymous rather than a guarantee of anonymity.
The app's analytics payload does not include desktop files, images, filenames, paths, screenshots, recordings, email addresses, purchase receipts, transaction identifiers or pointer movements. Rugberry does not use advertising identifiers or session replay. Its analytics requests ask PostHog not to create person profiles or enrich events with geographic information, and substitute a zero address for the event's IP field. Providers still receive the network IP address needed to handle a connection. This is not a claim that all provider logs or other services discard IP addresses.
To stop sharing, open Access & Support → Access options → Privacy settings and turn off Share basic app usage (optional). This does not affect your purchases or app access. It stops new events, cancels pending requests and removes the local analytics identifier. Events are not queued on disk for later delivery. A request already received cannot be recalled; switching off does not delete data already received by PostHog. Switching on again creates a new identifier.
Recipients and processing locations
Apple provides App Store purchasing and related store services under its own privacy terms. RevenueCat provides purchase verification and reporting; PostHog provides optional usage analytics; email providers handle support correspondence. Cloudflare hosts this policy page. These services may use their own service providers.
The app sends analytics to PostHog's US ingestion service. Network services and support handling can involve processing outside your country.
International-transfer safeguards and the applicable provider arrangements have not yet been fully verified. We cannot currently identify a verified safeguard for every transfer described here. Contact info@brry.co for available information about a particular recipient or transfer.
Legal grounds
The legal grounds for the processing described in this notice have not yet been fully verified. In particular, default-on usage sharing must not be understood as affirmative consent. This notice does not establish a legal basis for that collection.
Retention and deletion
Local settings, permission bookmarks, saved wallpaper copies, purchase caches and diagnostics can remain on your Mac after quitting or reinstalling. Removing Rugberry alone may not remove that data. If you plan to remove saved wallpaper files, first choose a different wallpaper in macOS System Settings so macOS no longer relies on the saved copy.
Turning off analytics clears its local identifier but does not erase earlier server events, support correspondence or purchase records. Deletion of provider-held information is a separate request. Apple controls its own App Store records.
We have not yet established a verified retention and deletion schedule for analytics events, purchase records, support correspondence, provider logs and backups. Those records may remain stored after you stop using the app or turn off analytics. We cannot currently promise a fixed deletion deadline. A provider’s event-query window is not proof that the underlying records have been deleted.
Your choices and rights
You can decline to select a photo, stop optional usage sharing, and choose what to include in a support message. Purchase verification needs the purchase information described above to confirm access; optional usage analytics and sending support email are not conditions of using paid features.
Depending on applicable law, you may request information about processing and recipients, access to or a copy of your personal data, correction, deletion, restriction, portability, or object to processing. Where applicable, you may also request notification of corrections or deletions to recipients, object to harmful results from solely automated processing, and seek compensation for unlawful processing. Where processing relies on consent, you may withdraw that consent without affecting the lawfulness of earlier processing. These rights have legal conditions and exceptions. Where applicable, you can complain to a competent data protection authority, including the Turkish Personal Data Protection Authority or the supervisory authority for your location in the EEA.
Use the contact at the start of this policy to ask about your data or exercise a right. We may need proportionate information to verify the request and locate relevant records. The app does not send your email address or purchase identifier to PostHog, so your email address alone may not identify earlier analytics events. Turning analytics off removes its local identifier, which may limit our ability to match those events to you. We do not require you to send a payment-card number, Apple password or desktop files to make a request.
Privacy requests can be sent to info@brry.co. Our operational request-handling and provider-deletion procedures are not yet fully established. This does not limit rights or deadlines that apply by law; it means we cannot claim that those procedures have been verified.
This privacy page
Loading this page sends connection information, including your IP address and HTTP request information, to Cloudflare to deliver and protect the page. This is separate from the app's optional usage analytics setting.
This page has no advertising, analytics scripts, third-party embeds or application-set cookies. It uses locally served styles and system fonts. Cloudflare may process technical request and security information as its hosting infrastructure operates.
Following an external link, such as a wallpaper credit or license link, opens the relevant service in your browser. That service receives the connection and browser request information and handles it under its own policy. Included wallpapers are bundled with Rugberry; their credit links are not automatic image uploads or runtime downloads.
Security and the visual cover
Rugberry uses macOS sandbox restrictions and connects to its purchase and analytics services over HTTPS. Local files remain subject to your Mac’s access controls. The rug is a visual overlay: it does not encrypt, secure or change permissions on the files it covers.
Changes to this policy
The effective date identifies the version of this policy. We will update the notice when relevant app behavior or data practices change and provide any additional notice or choice required by applicable law.