Privacy Policy

This notice covers the RENO mobile applications and the presentation website at reno.urban-division.com. It explains the current development version; it is separate from the general Urban Division company website notice.

1. Who is responsible

The data controller is:

Tax identification number (CUI): xxx

Trade Register number: xxx

Use the contact above for privacy questions and requests about your personal data.

2. Information used by RENO

Account and sign-in

Your verified email address, Google account identifier, an internal RENO account ID and session records. Google handles your sign-in credentials; RENO does not receive your Google password. The Google SDK also handles basic account information and technical sign-in data under Google’s policies.

Projects and saved products

Project and room names, categories, product links and available product details, notes, quantities, prices, currencies and saved exchange valuations.

Shopping and collaboration

Your chosen shopping items, quantities marked as purchased, project memberships, invitations, expiry/acceptance/revocation status and the accepting account. A recognized iOS Share channel may be recorded for invitations when the operating system reports one.

Support messages

Your email address and information you choose to send when asking for help. Include only the details needed to resolve your issue.

Technical information

Requests needed to operate and protect the service may include IP addresses, request paths, timestamps and errors. Hosting, operating-system and sign-in providers may process their own technical information.

RENO does not request your contacts, precise device location or payment card details. A project currency can be suggested from the device’s region setting, without requesting GPS access. Free-text notes can contain whatever you enter; avoid putting sensitive information into them unless it is necessary and appropriate.

3. Why information is used

Account and catalog information lets us authenticate you, save and synchronize your projects, manage access, prepare shopping estimates and provide the features you choose. Contract-related processing supports the service you request. Our legitimate interests include service security, reliability and responding to ordinary enquiries. We also process information when required by law. If a separate optional use requires consent, that use must be explained before it starts.

4. Shared projects

When you join or share a project, the people with access can see and work on that project’s content. A project owner can view invitation status and the accepting email address. Shared-project access does not give collaborators access to your unrelated private library or other projects.

Only share content you are entitled to share. Other people may have already seen, copied or acted on content before you remove their access. The treatment of shared content when an account is deleted must be finalized and explained before public release.

5. Merchants, product pages and images

When you ask RENO to retrieve a product or display a merchant image, your device contacts the merchant or its content providers. They may receive your IP address, the requested URL and device/browser information, and their own privacy practices apply. Extraction happens on your device; RENO does not import the login cookies from your store app or browser.

Saved product details and image links are sent to the cloud catalog when you save. Merchant product images are kept as merchant URLs rather than uploaded to our own image storage. Your device may cache displayed images and other temporary data; this is not an offline catalog.

6. Providers and data transfers

The catalog/API is hosted on Amazon Web Services. Google provides sign-in. Frankfurter and, as a fallback, the European Central Bank provide public exchange-rate data: those requests use currency pairs from our server rather than your account ID or private product list. Email providers handle support correspondence.

Some providers operate internationally. The final policy must identify the support email provider and confirm any applicable international-transfer arrangements and safeguards before public release.

Provider information: Google Privacy Policy, Google Sign-In SDK disclosure and AWS Privacy Notice.

7. Security, retention and deletion

Requests to our API use HTTPS, and access is controlled by the account and project permissions. RENO uses protected operating-system storage for its private session credentials. We do not claim that the catalog is end-to-end encrypted or that any system is entirely risk-free.

Account and project records remain available while the account and its content are maintained. Deleting a product location affects that location; signing out or uninstalling RENO does not delete the cloud account. Sessions currently expire after seven days, which ends their validity rather than deleting the account.

The current development version has no complete account-deletion flow or inactivity-based account purge. Final account-deletion handling, shared-project effects, operational-log retention and any backup retention periods must be confirmed before this policy becomes effective. See account and data deletion for the current status.

8. Your choices and rights

Depending on the circumstances and applicable law, you may request access, correction, erasure, restriction or portability of personal data, and object to processing based on legitimate interests. Where consent is used, you may withdraw it without affecting earlier lawful processing. We may need proportionate information to confirm your identity.

Under the GDPR, valid rights requests are normally answered within one month; extensions may apply with the required notice. You can complain to your competent supervisory authority. In Romania this is the ANSPDCP. Further information is available from the European Commission.

9. Cookies, analytics and notifications

This presentation website does not set cookies, use local storage or load analytics/advertising scripts. RENO does not add an advertising or behavioural-analytics service in the current version. Google sign-in and merchant pages may use their own necessary storage and technical processing. Push notifications are not enabled in the current version.

10. Children and changes

RENO is not designed as a children’s service. Contact us if you believe a child has supplied personal information inappropriately. We will update this notice when relevant practices change and publish the applicable effective date when the reviewed policy takes effect.