RugberryGet Rugberry This notice covers the Rugberry Mac app and the Rugberry website at rugberry.brry.co, including its support pages. Rugberry is provided by BRRY Dijital Teknoloji Anonim Şirketi, the controller responsible for the processing described here. For privacy questions or requests, contact info@brry.co.
The website is self-contained. You do not need to visit a separate company website to read this notice or find Rugberry support. Features and controls in the app depend on the version you use.
Rugberry is a visual cover over part of your desktop. It does not browse, move, organize or delete the files underneath that cover, and it is not confidential storage. No Rugberry account is required.
Visiting this website
The website serves its images, videos, styles and interaction code from the Rugberry site. Page scripts control presentation, the textile gallery and video playback. This site does not include advertising tags, an analytics SDK, a login, a support form or a file-upload feature. Its own code does not use cookies or persistent browser storage to measure visitors.
Loading pages and media still sends connection information, such as your IP address, requested address and browser request information, to the website's hosting and security services. Those services process requests to deliver and protect the site. This is separate from the app's optional usage-sharing setting. The absence of an analytics script does not mean that hosting infrastructure receives no information or keeps no security logs.
App Store buttons and wallpaper credit/license links open other services in your browser. Those services receive your request and handle it under their own policies. A support email link opens your chosen email handler; it does not automatically send a message.
Wallpaper, photos and local app information
Invisible reads a supported static wallpaper image locally to match the cover to the desktop. If permission is needed, you can select that image in a macOS file picker. Rugberry may retain a read-only permission bookmark so it can read the selected wallpaper again. It does not obtain the wallpaper by capturing your screen or scanning the files beneath the cover. If permission cannot be retained, the app may ask again after reopening.
You can preview a bundled wallpaper or a photo you choose. Previewing does not change the desktop wallpaper. The separate Set as desktop wallpaper action asks for confirmation, saves a static image copy in local app storage and asks macOS to use it on the selected display. That wallpaper can remain after quitting Rugberry; you can change it in macOS System Settings. Rugberry does not upload images, filenames or paths as part of these wallpaper features or include them in usage analytics.
Appearance, placement, completed rug shape, interaction preferences, onboarding state and the analytics choice are saved locally. macOS may save window positions. Unreadable settings may be preserved for recovery. Locally enabled diagnostics can write reports, synthetic rug previews and simulation recordings, including interaction coordinates and technical timing information. These local app outputs are not automatically uploaded. Review them before choosing to share them with support.
Purchases and access verification
Apple's App Store and RevenueCat process purchase information to verify and restore purchases and existing trials, verify complimentary access and provide purchase reporting. Information can include an app-specific purchase identifier, product and transaction identifiers, receipts or signed transaction information, dates and access status. Rugberry checks purchase entitlements to determine access to paid features.
RevenueCat requests also contain technical information such as app/SDK/operating-system versions, machine/platform type, up to three preferred locales, available store-country information and operating-state flags. The SDK can report system tracking-permission status. Receiving infrastructure also sees connection information such as IP addresses. Apple handles payment information; Rugberry does not receive your payment-card details.
The purchase SDK maintains local identity, customer-information and attribute caches. Its technical diagnostics can persist events while their enablement is being determined and upload them if enabled by the effective SDK configuration. Such diagnostics can include event/session identifiers, timestamps, request timings/results, error and endpoint information, product information and transaction identifiers. This is separate from the app's local diagnostics and optional PostHog usage sharing. Turning usage sharing off does not turn off purchase verification, purchase reporting or the purchase SDK itself.
Email support
Emailing us from the website sends the message and information you choose to provide. The website does not automatically attach an app identifier, desktop files or a diagnostic report.
In the Mac app, Contact Support opens an editable draft that initially contains the RevenueCat Support ID, app version/build, macOS version and access status. You can edit or remove those details. Rugberry does not send the message automatically: you choose whether to open it in an email app or copy the edited draft for manual email. Closing the support window discards its in-app draft, but does not clear the clipboard or drafts/messages in another email service.
If you send a message, we receive your email address, message and any details or attachments you include. We use them to respond and investigate the issue. Retaining the Support ID in a message lets us associate it with the relevant purchase record. Email providers process correspondence to deliver and store it. Do not include Apple passwords, payment-card numbers or unrelated private desktop files.
Optional app usage analytics
Rugberry uses PostHog to understand feature use and improve the app. Sharing is on by default when no preference has been saved, including after an update, and events can be sent before you change that setting. An explicitly saved Off choice remains off after an update or relaunch.
When enabled, selected events cover app opens, onboarding and controls, preview/appearance/reveal interactions, introductions, purchase/trial/restore outcomes and support-screen views. Versions containing wallpaper-recovery reporting also send coarse wallpaper-readiness and permission outcomes, such as access needed, a cancelled selection or an unsupported image. They do not send the selected file or a raw error message.
Events include a random app-specific identifier, app version/build, event/interface version information, broad access status and relevant appearance/screen categories. The app also sends a test/production/development label, or an unknown label when unresolved, and may indicate how that classification was obtained. Newer versions use verified Apple app-transaction information for that classification. The analytics identifier stays the same across launches while sharing is enabled. It is separate from the purchase identifier and should be understood as pseudonymous, not a guarantee of anonymity.
The custom analytics payload does not contain desktop files, images, filenames, paths, screenshots, recordings, email addresses, purchase receipts, transaction identifiers or pointer movements. Rugberry does not use session replay or advertising identifiers. Requests ask PostHog not to create person profiles or add geographic enrichment and replace the event's IP field with a zero address. Receiving services still see the connection's source IP; this is not a promise that every provider log discards it.
Turn sharing off in Access & Support → Access options → Privacy settings → Share basic app usage (optional). This does not affect your purchases or access. It stops new events, cancels pending analytics requests and removes the local analytics identifier. The custom PostHog sender does not save an event backlog on disk or retry failed events. A received request cannot be recalled, and Off does not erase previously received data. Enabling sharing again creates a new identifier.
Recipients and international processing
Apple provides App Store purchasing and related store services under its own privacy terms. RevenueCat provides purchase verification and reporting; PostHog provides optional app analytics; email providers handle support correspondence; Cloudflare delivers and protects this website. These providers can use service providers of their own.
The app currently uses PostHog's US ingestion service. Support and service-provider processing can occur outside your country. Applicable provider agreements and international-transfer safeguards have not yet been fully verified for every flow described here. This notice does not claim a signed agreement, EU-only storage or a verified safeguard for every transfer.
Legal grounds, retention and deletion
The legal grounds for the described processing have not yet been fully verified. In particular, default-on sharing is not affirmative consent. This notice explains current handling; it does not establish a legal basis for that collection.
Local preferences, bookmarks, wallpaper copies, purchase caches and diagnostics can persist after quitting or reinstalling. The inspected app has no general age-based purge of those local files. Before removing a saved wallpaper image that macOS is using, first select a different wallpaper in System Settings.
Turning analytics off does not erase earlier server events, support correspondence or purchase records. Apple controls its own App Store records. A verified retention/deletion schedule for analytics, purchase records, correspondence, provider/security logs and backups has not yet been established. Records may remain after you stop using the app. We cannot promise a fixed purge deadline; a provider's query window does not prove deletion.
Your choices and rights
You can decline to select an image, stop optional usage sharing and choose what to send to support. Purchase verification needs the information described above to establish access; optional analytics and sending an email are not conditions of using paid features.
Depending on applicable law, you may have rights to information about processing/recipients, access or a copy, correction, deletion, restriction, portability, objection and notification of corrections/deletions to recipients. Where applicable, you may object to harmful results of solely automated processing, seek compensation for unlawful processing and complain to the competent data protection authority. Where consent is the legal ground, it may be withdrawn without affecting earlier lawful processing. Rights have legal conditions and exceptions.
Use the contact at the start of this notice for questions or requests. Proportionate information may be needed to verify a request and find relevant records. Your email alone may not locate PostHog events: the app does not send your email or purchase identifier to PostHog, and Off removes the local analytics identifier. Operational request-handling and provider-deletion procedures are not yet fully established. This does not limit rights or deadlines that apply by law.
Security and changes
Rugberry uses macOS sandbox restrictions and HTTPS connections for purchase and analytics services. Local files remain subject to your Mac's access controls. The visual cover does not encrypt or change permissions on covered files and does not guarantee that screen sharing or recording conceals information.
We will update this notice when relevant app or website practices change, with any additional notice or choice required by applicable law. The effective date identifies the published revision.