Last updated: 13 November 2026
Your photos, notes, collections, and plates stay in your local library. Ruvano does not upload that library to its own servers.
Your photo library is not used for advertising. The app does create a service account from a device identifier, asks for permission to track on iOS, and shares device identifiers and install-attribution data with our servers and with Adjust. You still choose when to share a photo, plate, or note.
Ruvano is a personal photo collection app for recording, organizing, reviewing, and creating four-photo plates from door and window photographs. This Privacy Notice explains what information is handled by the app, how it is used, when it may leave your device, and what choices you have.
Ruvano is designed around local use. Your personal collection, imported photos, thumbnails, notes, collection names, and generated plates are stored on your device in the app’s local library. Ruvano does not require account registration for its core collection features, and it does not provide cloud synchronization for your library.
When you choose to save a plate to your photo library, share a photo, share a plate, or share a note, you intentionally create an external copy or pass content to the system share sheet and the destination you select. Those external copies are not controlled by Ruvano after export.
Ruvano does not sell your personal information. Ruvano does not sell, rent, or trade your photos, notes, collection records, generated plates, or other user content.
Ruvano does not share your user content with third parties for advertising, marketing databases, profiling, or resale. Your content leaves the local library when you choose to share it or save a plate to your photo library. Opening a legal web page connects to its host without sending your collection content.
The app includes the Adjust attribution SDK from Adjust GmbH. Adjust and our servers receive the device identifiers and install-attribution data described below. Adjust is used for install attribution. They do not receive your photo library, notes, or plates. Opening a legal page connects to its hosting provider and does not send your collection. The app does not include a crash-reporting SDK.
We may update this Privacy Notice to reflect changes in the app, legal requirements, platform rules, or data practices. When the notice changes, the “Last updated” date will be revised.
Material changes may be communicated through the app, an updated web page, release notes, or another reasonable method. Your continued use of Ruvano after an updated notice becomes available means that you accept the revised Privacy Notice, to the extent permitted by applicable law.
Your collection data is kept locally on your device until you delete it, clear collection data in Settings, uninstall the app, or remove the relevant content. This includes app-created photo copies, thumbnails, collection records, notes, and generated plate records stored inside the app’s local library.
Ruvano does not operate a crash-log or support-message collection service in the current app. Help & notes opens the system share sheet; it does not submit a support request to us.
Adjust GmbH receives install and session events, including device identifiers, and keeps them under its own retention rules. Our servers keep the device identifier, the service user ID, and advertising attribution fields used to operate the account and measure install attribution. Device and app store services may also process information under their own policies.
Exported copies, such as images saved to your system photo library or files shared with another app, are not deleted when you delete Ruvano’s local copy. You must manage those external copies directly in the location or service where they were saved or sent.
Depending on your location, you may have rights to access, correct, delete, export, or restrict the use of your personal information. Because Ruvano’s core library is stored locally, many of these choices can be exercised directly on your device by viewing, editing, exporting, deleting entries, deleting plates, or clearing collection data in Settings.
You may correct information by editing entries, collections, titles, labels, notes, and plate names in the app where editing is available. You may delete app-stored content by deleting entries, deleting saved plates, deleting collections, or using the clear collection data option. You may export certain content by using the system share sheet or saving generated plates to your photo library.
You may withdraw consent for optional permissions through your device settings. For example, you can deny or revoke camera access or photo library write access. If a permission is withdrawn, the related feature may stop working, but other parts of the app may remain available.
For privacy questions or rights requests, use the contact method listed in the Contact section. Please note that if data exists only on your device and is not accessible to us, we may be unable to inspect, recover, or delete it remotely.
Ruvano uses technical measures intended to protect local app data. The app stores its catalog and media records in a local database and local files, with user content protected using encryption. Encryption keys are managed through secure device storage, such as the iOS Keychain or Android secure storage where available.
Imported images are normalized into app-managed copies. During this process, Ruvano is designed to redraw images and remove source metadata such as EXIF and GPS metadata from the app’s stored copies. Generated plates do not intentionally include your notes or location fields, although visible information inside a photo or title may remain visible in the final image.
No security method can be guaranteed to be perfect. Device-level risks, operating system behavior, backups, temporary files, exported copies, shared files, screenshots, and recipient actions may affect the privacy of your content outside Ruvano’s local encrypted library.
Ruvano uses information to provide the app’s core features: importing or taking photos, creating local entries, organizing photos into collections, searching and filtering records, displaying photo details, generating four-photo plates, saving plates, and enabling user-initiated sharing.
Ruvano does not use your personal collection content for ads. Ruvano does not use your photos, notes, labels, or generated plates for profiling. Ruvano does not use your information for selling personal data or user content.
Local identifiers, timestamps, and settings support the library features. We do not send your photos, notes, labels, or plates to an analytics service. We do send the install-attribution data described under Identifiers and advertising measurement to our servers and to Adjust.
Ruvano is intended for door and window photo organization and plate generation. The app does not perform facial recognition, does not conduct biometric analysis, and does not create face templates, faceprints, or biometric identifiers.
If an image you import happens to contain a person or a face, Ruvano treats that image as ordinary user-selected photo content for local storage and display. The app does not identify people in the image or compare faces against any database.
Temporary processing files may be created when importing, normalizing, viewing, sharing, or exporting images. Such temporary data is deleted after processing or cleaned up as part of app maintenance where technically possible. Exported copies that you save or share are controlled by the destination you choose.
Your collection stays on your device. Opening legal pages or sharing content with an app or recipient you select can involve services outside your country. Those services handle the connection or shared copy under their own policies; opening a legal page does not upload your collection.
Ruvano does not provide cloud synchronization or transfer your local photo library to its own servers.
User-provided data. Ruvano may store photos you import or capture, app-created photo copies, thumbnails, entry titles, type selections, style labels, shape labels, material labels, color labels, detail tags, country or region text, collection names, collection membership, observation notes, generated plate titles, generated plate images, and optional shared note drafts while you are using the app.
Automatically generated app data. The app may create local identifiers for entries, photos, collections, and plates; timestamps such as collection or generation dates; app settings such as the sample collection preference; sorting and filtering states; temporary files used for sharing or export; and technical records needed to operate the local library.
Diagnostics and device-related data. The app does not collect crash logs, performance metrics such as launch time, hang rate, frame rate, or energy use, or a separate category of other device data. Your operating system or app store may separately handle diagnostics under its own policy.
Cookies and similar technologies. The native app does not need cookies for the local collection features. If you open legal web pages or other web content inside the app, the web view, hosting provider, or platform may use cookies, local storage, logs, or similar technologies according to the relevant web service’s settings and privacy practices.
Permissions. Ruvano may request camera access when you choose to take a photo. It may use the system photo picker when you choose photos. It may request permission to add images to your photo library when you tap Save to Photos. It may use the system share sheet when you choose to share a photo, plate, or note. On iOS, before advertising measurement starts, Ruvano shows the App Tracking Transparency prompt. If you decline, the app does not receive the advertising identifier (IDFA). Ruvano does not request location, microphone, or contacts permission.
The photo collection stays on your device. Separately, the app collects the information below and sends it off the device.
User ID. After the device signs in, our servers assign a user ID. The app stores it and later sends it back to our servers together with advertising attribution fields, so an install source can be connected to the service account. We use it to operate the account and to measure install attribution. It is linked to you and used for tracking. It is not sent to Adjust as a separate user ID.
Device ID. The app reads a persistent device identifier. On iOS this is the vendor identifier, kept so it can survive reinstall, and it is also the sign-in token for the service account. After you allow tracking, the app and Adjust read the advertising identifier (IDFA). Adjust also creates its own advertising device identifier and reads the vendor identifier. These identifiers are sent to our servers and to Adjust. We use them to sign the device in and to measure install attribution, and we share them with Adjust. Adjust may use them for analytics and third-party advertising measurement. They are linked to you and used for tracking.
Product interaction. Adjust receives session information such as session count, session length, and time spent, and uses it for analytics. It is not linked to your identity and is not used for tracking. Install attribution uses the device identifiers and advertising data described above.
Advertising data. The app sends the advertising network, campaign, ad group, and creative identifiers returned by Adjust, together with any install referrer Adjust provides, to our servers along with your user ID and device ID. We use this for analytics and to measure install attribution. It is linked to you and used for tracking. The photo collection does not display third-party ads.
Purchases. The current version does not collect purchase history. It has no in-app purchases, subscriptions, orders, or receipts, and it does not send purchase amounts, product codes, order numbers, or receipts. It also does not collect a separate category of other device data.
Adjust is the tracking SDK in this app. On iOS you can decline the tracking prompt, or turn off Allow Apps to Request to Track in Settings, to stop IDFA access. We do not sell personal information.
If you are in the EEA, the UK, or Switzerland, the GDPR gives you the right to request access, correction, deletion, restriction, or portability of the account and attribution data we hold, and to object to processing used to measure install attribution. If you are a California resident, the CCPA gives you the right to request access to or deletion of personal information we hold, and to opt out of sale or sharing. We do not sell personal information. To ask us to delete the service account and the attribution records we store, email ylrdwasgrfy@hotmail.com. We cannot delete a photo library that exists only on your device. Use Clear Collection Data in Settings, or delete the app, for that local library.
By downloading, installing, accessing, or using Ruvano, you acknowledge that you have read this Privacy Notice and agree to the collection, use, storage, processing, and sharing practices described here.
If you do not agree with this Privacy Notice, do not use the app. You may also limit certain processing by not granting optional permissions, not importing photos, not using sharing features, or deleting app-stored content from your device.
For questions: ylrdwasgrfy@hotmail.com