Rafino · Legal

Privacy Policy

Last updated: 20 October 2026

This policy explains how Rafino handles your information, including our planned Uber ride-booking integration.

1. Who is responsible

Rafino is operated by Sohail Sheikh. For privacy questions, access requests, corrections or deletion requests, contact rafino.app@gmail.com. This policy covers rafino.app and the website’s updates signup.

2. What is available today

Rafino is currently in development. This website introduces Rafino and lets you subscribe to launch and product updates. It does not currently offer an Uber login, make ride bookings, or collect Uber profile, location or trip information.

3. Information collected by this website

• Updates signup: your email address, signup time, consent record and a private unsubscribe token.
• Abuse prevention: a short-lived hash derived from your network address and the current time window, plus a request counter. The signup database does not store the original network address. These records expire after the hourly rate-limit window and are cleared during subsequent form requests.
• Hosting and security: our hosting provider, Cloudflare, may process connection information such as IP addresses, requested URLs, browser information and security logs to deliver and protect the site.
• Messages you send: your email address and the information you choose to include when contacting us. Please do not email passwords, payment-card details or unnecessary sensitive information.

This website does not request device location, load advertising trackers, or use a Rafino analytics cookie. Fonts and illustrations are hosted with the website.

4. Why we use this information

We use your signup information to send the Rafino updates you request. We use technical information to operate the website, prevent abusive submissions and investigate problems. We use correspondence to answer your requests. Where consent is required, we ask for it; you can withdraw your email-updates consent at any time. Other processing is limited to operating and protecting the service or meeting applicable legal obligations.

5. Planned Uber integration

We plan to offer Uber ride booking within Rafino using Uber’s third-party (3P) ride-booking APIs, subject to Uber approval, the agreed integration model and availability. The following describes the planned handling of data; these features are not active on this website. We do not currently receive or store Uber rider data or authorization tokens.

• Your choice and permission: if you choose to link an Uber account, authorization will take place through Uber’s sign-in and permission flow. If an approved booking flow instead uses details you provide directly to Rafino, we will explain what is shared with Uber and obtain the required consent before submitting it. Rafino will request only the information and permissions needed for the feature you choose. A newsletter signup does not authorize Uber access.
• Potential data: depending on the approved permissions, the integration may use a rider or Uber account identifier, name, contact email or phone number needed to arrange the ride, pickup and destination addresses or coordinates, fare and arrival-time estimates, booking identifiers, trip status, cancellation information, and driver or vehicle details needed to display your booking. Device location will only be accessed after the relevant permission is given; entering a pickup address manually will be offered where the feature supports it. Historical trips will only be requested if an explained feature needs them and the required permission is granted.
• Purpose and sharing: rider contact details, pickup, destination and booking instructions may be sent to Uber to quote, request, manage or cancel the ride you choose. Uber may share the necessary ride details with the driver or other providers involved in fulfilling that request. Information received from Uber will be used for that travel feature, not for selling data or unrelated advertising. Newsletter addresses are not shared with Uber merely because someone subscribes.
• Account security: Uber handles its login credentials. Rafino will not ask you to provide your Uber password or payment-card details in this website. For an account-linked integration, access and refresh tokens will be handled by a secured backend with restricted access, rather than placed in public website code. We will not retain Uber passwords or raw payment-card details. These controls must be implemented and checked before the integration goes live.
• Control: you will be able to stop using the integration, withdraw authorization through Uber’s available account controls, and request deletion of Rafino-held information by contacting us. We will stop new access after authorization is withdrawn and remove or de-identify Rafino-held Uber information when it is no longer needed for the requested service, unless an applicable legal obligation requires retention. Any required retention and actual time limits will be disclosed before launch. Disconnection will not cancel an active ride automatically or delete information independently held by Uber.

Before enabling an integration, we will update this policy and the in-app notices to explain its actual permissions, data storage, retention periods and disconnection process. Uber independently handles information under its Privacy Notice and service terms. Mentioning Uber does not mean Rafino is currently approved or endorsed by Uber.

6. Storage, access and service providers

Website subscriptions are stored in a private Cloudflare D1 database. Access is limited to the operator and authorized people or service providers who need it to operate Rafino. The public website has no subscriber-list download endpoint. Email correspondence is processed through our Gmail account. Cloudflare and Google may process information in countries other than yours under their applicable terms and safeguards.

We do not sell personal information. We may disclose information where required by law or when reasonably necessary to protect users, investigate misuse or protect legal rights. If an email-delivery provider is introduced, we will disclose material changes before using it.

7. Retention and deletion

We keep your subscription while you wish to receive updates, until you unsubscribe or request deletion, or until the list is discontinued. The unsubscribe function removes the active subscription record. Contact us if you need help. Hosting-provider logs and backup copies may remain for their applicable retention cycles. We keep correspondence only as needed to resolve the matter or meet a legal obligation.

8. Your choices

You can ask to access, correct or delete personal information, withdraw consent, or raise a privacy concern by emailing rafino.app@gmail.com. Marketing messages we send will include an unsubscribe link. We may need to verify a request before releasing or changing information. Rights and response requirements depend on applicable law; you can also contact a relevant privacy authority where that right exists.

9. Security, younger users and changes

We use restricted database access and HTTPS for the hosted website, but no online service can promise absolute security. This signup is intended for adults; we do not knowingly seek personal information from children. Contact us if a child’s information has been submitted so we can remove it.

We may update this policy as Rafino develops. The date at the top identifies the latest version. Material changes to a new feature’s data handling will be explained before the feature is enabled.