Rocket Time Privacy Policy
Version 1. Effective on Rocket Time's launch day.
This Privacy Policy describes the personal information Edward Lukowsky, the developer of Rocket Time ("Rocket Time", "we", "us"), collects through the Rocket Time apps for iOS and Android (the "Apps") and the website at rockettime.app (the "Site"; together with the Apps, the "Service"), how we use and disclose it, how long we keep it, and the choices and rights you have.
Summary (not binding). You can use most of the Service without an account. Your exact location stays on your phone. An account is needed to get your own trip prices, book a Trip or use a membership. Booking details go to our booking partner and the airline or hotel. Ads are served by Google AdMob, which collects device and ad data under Google's policies. You can delete your account in the Apps. The full text below governs.
1. Who Is Responsible
- Rocket Time is responsible for the personal information described in this Privacy Policy.
- You can contact us about this Privacy Policy or your information at support@rockettime.app or by mail to Edward Lukowsky, 18034 Ventura Blvd, Unit #655, Encino, CA 91316.
2. Information We Collect and How We Use It
2.1 Location
- With your permission, the Apps read your device's location while you are using them. They never ask for location in the background. Your exact location is used on your device to work out what you can see, point the sky view, draw a launch's path against your horizon and tell when you have arrived at a booked Trip's viewing spot. The Apps do not send your exact location to us.
- To get the horizon, cloud forecast and viewing spots for where you are, the Apps ask our servers for the data for an area about 5 km across (a geohash cell) or a larger cloud forecast square. These requests carry no identifier of you or your device, and we do not store which device asked.
- If you turn on alerts, the Apps work out on your phone which launches are worth alerting you about, the seconds after liftoff each one rises above your horizon, the moments a Starship or a free-flying Dragon passes over you, and whether a booked Trip's viewing spot is within driving range, and send us those lists and numbers with your device record. They are not a position, but several together narrow down the region you are in. If you have a membership that uses them, the Apps also send the airport nearest your home, worked out on your phone, and the two drive limits you chose: how far you would drive from home and how far after landing.
- If you do not grant location permission, you can pick a place by hand, and only that place is used as above.
- To show the name of your town and the drive to the nearest launch sites, the Apps may ask your phone's built-in map services (Google on Android, Apple on iPhone) for the place at your location and the road route from it. Rocket Time doesn't keep the answers on its servers.
- When you visit the Site, our hosting provider, Cloudflare, estimates your approximate location from your IP address. The Site uses that estimate, rounded to about 7 miles, to show the next launch near you and roughly where you are on its map, sent only to your browser. We do not store it with anything about you; the launch scores worked out for that area are kept in Cloudflare's cache for up to a day, for anyone visiting from the same area.
2.2 Device and Alerts
- If you turn on alerts, the Apps send us a push notification token issued by Apple or Google, your device platform, the alerts you chose, the launches you saved and the lists in Section 2.1.3. We give the device a random identifier and store these with it to send the alerts you asked for. If you are signed in, we link the device record to your account, to send alerts that depend on your membership.
- If you follow a launch on your Lock Screen or in a live notification, the Apps send us a token for that launch's live updates. On Android, the App subscribes to a Firebase Cloud Messaging topic for that launch.
- Some alerts, including the time to leave for a booked Trip, are scheduled on your phone and are not sent by us.
- We record which alerts we have sent to each device so the same alert is not sent twice.
- If you save a Trip, we store its price, currency and the time it was checked with your device identifier, to tell you when it changes.
2.3 Accounts and Sign-In
- You do not need an account to use most of the Service. You need one to get your own prices, to book a Trip and to use Travel Club or Travel Club Pro.
- You can sign in with Apple or Google. Either one sends us an identifier for your account with them, and that is what your Rocket Time account is tied to. Google's sign-in token also includes your email address and name, and Apple's includes your name and email address if you choose to share them (or a private relay address if you choose Hide My Email); we don't keep them on our servers. The app keeps the sign-in name and email on your phone to suggest them at checkout, and removes them when you sign out or delete your account. Google's own privacy policy covers its sign-in, which may use your IP address to help prevent fraud.
- If you sign in with Apple, we also store a token Apple issues so we can revoke Rocket Time's access with Apple when you delete your account.
- We store a hashed copy of your sign-in session. On iPhone, if you use iCloud Keychain, your sign-in and the choices you made in setup are kept in it, so a new iPhone or another of your Apple devices with the same Apple Account stays signed in and skips setup. Apple encrypts iCloud Keychain end to end; we can't read it. Signing out removes the sign-in from all of them.
- When you get prices, we check that you're signed in. For flights, the app also sends the airport nearest your home and the drive limits you chose, so the search can pick airports. We don't keep your searches with your account. For each pair of airports, we keep how the flight prices our searches find compare with published average fares, with nothing about who searched.
- The account deletion page on the Site (rockettime.app/delete-account) loads Apple's and Google's sign-in code when it opens, so Apple and Google receive your IP address and browser details under their own privacy policies, even if you don't sign in.
2.4 Trip Bookings
- When you book a Trip, you enter the travelers' names and, for flights, each traveler's date of birth, gender as shown on the travel document and nationality, and a contact email address and phone number. A room booked without flights collects one name for each room, the lead guest's, with the contact email and phone. We send these details to our booking partner, Nuitée Connect (LiteAPI), which sends them to the airline and hotel to make the booking.
- You enter your payment card in Nuitée Connect's payment form. Rocket Time does not receive or store your card details.
- We store a record of each booking: the launch, viewing spot, airports, number of travelers and rooms, dates, the booking references issued by our booking partner, the hotel and airline names, the price paid, the free cancellation deadline, its status, the version of the Trip Booking Agreement you agreed to, and the device and account that booked it. From the contact details we keep only the email address and first name, to send the Trip's emails. We use this record to show your Trip, to send its alerts and emails, to move or cancel the Trip when you ask, and to understand how Rocket Time is used.
- If you are signed in, the Apps also store on your account a copy of each booked Trip as shown in the Apps, including the lead guest's name, email address and phone number, so the Trip appears on your other devices and can be moved in the same name.
- After a booking, the app keeps that checkout's contact email and phone number and each traveler's name and, for flights, date of birth, gender as shown on the travel document and nationality, on your phone only and not in its backups, so it can offer them at your next checkout. We don't receive this copy. The app removes it when you sign out or delete your account.
- When you pick where to stay on the map, the map and the place search come from Apple Maps on iPhone and Google Maps on Android. What you type and the place you pick go to Apple or Google to show the map and find the place, under their own privacy policies. The place you pick goes to our server and to LiteAPI to find hotels near it. We don't keep it with anything about you; the list of hotels near a place is kept for a day for anyone who searches near the same place.
2.5 Memberships and Purchases
- If you buy a membership or the earlier Remove Ads purchase, Apple or Google processes the payment; we never receive your card details.
- We keep the store's record of your membership on your account: the store, the plan, the store's purchase identifier, when it renews or ends, and whether it was refunded. We check it with Apple (App Store Server API and notifications) or Google (Google Play Developer API, and Google Cloud Pub/Sub for Play's notices). When you buy on iPhone, the App sends Apple your Rocket Time account identifier with the purchase, and on Android it sends Google an identifier for your account, so the purchase is matched only to your account.
- We keep it until you delete your account. Deleting your account doesn't cancel the membership with the store.
2.6 Camera and Motion Sensors
- With your permission, the Apps use the camera and motion sensors to show a launch's path over the live camera view and to find what blocks your view of the sky. Camera images and sensor readings are processed on your device. They are not stored or sent to us.
- On Android, the camera view uses Google Play Services for AR (ARCore), which is provided by Google and governed by the Google Privacy Policy.
2.7 Maps
- Maps come from Google Maps on Android and Apple Maps on iPhone. They load imagery for the area on screen, which can include the area around you. On Android, the Google Maps SDKs also collect your IP address, device details, crash reports, how you move the map and identifiers for those SDKs, under Google's privacy policy.
- The sky view map in the iPhone App loads map tiles from OpenFreeMap, which receives your IP address and the map area shown.
2.8 Agreements You Accept
- We keep a record of which version of the Terms of Service, Privacy Policy and Trip Booking Agreement you agreed to, and when, with your device or account, the platform and the app version.
2.9 Technical Information
- Requests from the Apps reach our servers through Cloudflare, which processes your IP address to deliver and rate-limit requests. Our hosting providers keep request and error logs.
- To limit abuse, the Apps give our servers a random install identifier and an attestation from Apple (App Attest) or Google (Play Integrity) that the request comes from a genuine copy of the App.
2.10 Analytics
- We analyze the information described in this Privacy Policy ourselves, including device and install records, requests to our servers, prices people get, bookings and memberships, to understand how Rocket Time is used (for example, how many people get prices compared with how many book), to fix problems, to improve the Service and to plan our business.
- We do this on our own systems. We do not send it to analytics companies, and we do not sell it. We may share or publish figures that are combined so they do not identify anyone.
2.11 Information We Do Not Collect
- We do not use third-party analytics or crash-reporting services, and we do not collect your contacts, photos, browsing history or exact location.
3. How We Disclose Information
3.1 Recipients
We disclose personal information only to the recipients below, and only for the purposes stated.
| Recipient | Information | Purpose |
|---|---|---|
| Nuitée Connect (LiteAPI) | Traveler and contact details, chosen flights and rooms, the place you pick to stay near | Booking, payment and changes to Trips; finding hotels |
| Airlines and hotels | Traveler and contact details, through Nuitée Connect | Providing the flight or room |
| Resend | Contact email address and first name, Trip details | Sending your Trip's emails |
| Apple | Push tokens and alert content, sign-in requests (including on the Site's account deletion page), your account identifier with iPhone purchases, App Attest, place searches and maps on iPhone | Alerts, sign-in, purchases, abuse prevention, maps |
| Push tokens and alert content (Firebase Cloud Messaging), sign-in requests (including on the Site's account deletion page), Play purchases and notices, Play Integrity, place searches, place names and maps on Android, ARCore | Alerts, sign-in, purchases, abuse prevention, maps, camera view | |
| Google AdMob | Device and advertising identifiers, IP address, ad interactions, diagnostics, collected by its software in the Apps | Serving and measuring ads (Section 3.2) |
| Cloudflare | IP address and requests; stored launch and area files | Delivering the Site and the Apps' requests; rate limiting; hosting |
| Railway | All information we store | Hosting our servers and database |
| OpenFreeMap | IP address and map area, from the iPhone App's sky view map | Map tiles |
- To get forecasts, horizons and viewing spots for an area, our servers send the coordinates of that area to MET Norway (cloud forecasts, rounded to about 10 km), the OpenStreetMap Overpass service (roads and places) and the Copernicus elevation data. These requests contain no identifier of you or your device.
- Links to rental cars and other third-party sites carry the airport and dates of the Trip. When you open such a link, the site you visit receives your IP address and collects information under its own privacy policy.
- We may disclose information if required by law, subpoena or court order; to protect the rights, safety or property of Rocket Time, our users or others; or to a successor in a merger, acquisition or sale of all or part of our business, which will be bound by this Privacy Policy for information it receives.
- We require each service provider that receives personal information from us to protect it and to use it only to provide its service to us.
3.2 Advertising
- The Apps show ads from Google AdMob unless you have a membership or the earlier Remove Ads purchase. AdMob's software in the Apps collects the information listed in Section 3.1 and uses it as described in Google's privacy policy and How Google uses information from sites or apps that use its services. Google may let other ad networks buy ads shown through AdMob; on iPhone, those networks receive anonymous install reports through Apple's SKAdNetwork.
- Every ad request asks for non-personalized ads. The iPhone App does not ask for permission to track you across other companies' apps and websites, so AdMob does not get your device's advertising identifier. The Android App does not read your device's advertising ID.
- Where the law requires consent for ads, including in the European Economic Area, the United Kingdom and Switzerland, the Apps ask for it before loading ads, and Settings offers privacy choices for ads to change it.
3.3 Sale and Sharing Under US State Law
- We do not sell personal information for money. We do not sell or share traveler details, contact details, account information or booking records.
- The disclosure of device information, IP address and ad interactions to Google AdMob for advertising may be considered a "sale" or "sharing" under the California Consumer Privacy Act and similar state laws, even though the ads are non-personalized. You can opt out of it by emailing support@rockettime.app with the subject "Do Not Sell or Share", or by buying any membership, which removes ads.
- We do not knowingly sell or share the personal information of consumers under 16 years of age.
- We do not use or disclose sensitive personal information for any purpose other than providing the Service you request.
3.4 Categories Under California Law
In the past 12 months, we have collected the following categories of personal information defined in California Civil Code section 1798.140, from you and your device, for the purposes in Section 2.
| Category | Examples | Disclosed to |
|---|---|---|
| Identifiers | Device and install identifiers, push tokens, account identifier, IP address, email address | Service providers in 3.1; Google AdMob |
| Customer records (Cal. Civ. Code § 1798.80) | Traveler names, phone number, email address | Nuitée Connect, airlines, hotels, Resend |
| Characteristics of protected classifications | Date of birth, gender on travel document, nationality | Nuitée Connect, airlines |
| Commercial information | Bookings, prices paid, membership and Remove Ads status | Nuitée Connect, airlines, hotels; Apple; Google |
| Internet or network activity | Ad interactions, requests to our servers | Google AdMob; Cloudflare; Railway |
| Geolocation data | Launch lists and timings worked out from your location, nearest airport, approximate location from IP on the Site | Railway; Cloudflare |
4. Retention
| Information | Kept for |
|---|---|
| Exact location, camera images, sensor readings | Not sent to us; kept only on your device |
| Device record (push token, alert choices, saved launches, launch lists, nearest airport, drive limits from home and after landing) | Until you ask us to delete it, or 30 days after Apple or Google reports its token is no longer valid, unless a booked Trip names the device |
| Live update token for a launch | Until 6 hours after that launch |
| Late alert listings | 1 day after the launch |
| Starship and Dragon pass timings | 1 day after each pass |
| Record of alerts sent | 30 days |
| Cloud forecast squares and area files | 30 days after the last request; not linked to anyone |
| Website launch scores for an area about 7 miles across | Up to a day in Cloudflare's cache; not linked to anyone |
| Account identifier, Apple token, sessions | Until you sign out (session) or delete your account |
| Membership record | Until you delete your account |
| Record of agreements you accepted | As long as your account, or your device record if you never signed in; for a booking, as long as its booking record |
| Trip copy stored on your account | Until you delete your account |
| Booking record (Section 2.4.3) | For as long as we decide we need it, for tax, accounting, chargeback and dispute records, legal requirements, and understanding how Rocket Time is used |
| Records we use for analytics (Section 2.10) | For as long as we decide we need them for those purposes; figures combined so they do not identify anyone may be kept indefinitely |
| Traveler details sent to Nuitée Connect, airlines and hotels | Under each recipient's own retention policy |
5. Deleting Your Account and Information
- You can delete your account in the Apps under Settings. You can also request deletion at rockettime.app/delete-account or by emailing support@rockettime.app.
- When you delete your account, we delete the account, its identifier and its sessions, remove the Trip copies stored on it, delete its membership records, unlink your booking records and device records from it, and revoke Rocket Time's access with Apple if you signed in with Apple.
- Deleting your account does not cancel any booked Trip or any membership. Memberships are canceled in your Apple Account or Google Play settings. Booked Trips remain booked with the airline and hotel, and remain on the device that booked them.
- After account deletion, we keep the booking record described in Section 2.4.3, without your account and without traveler names or contact details, as described in Section 4, because it is a record of a paid transaction.
- Turning off alerts in the Apps stops alerts but does not delete your device record. When you remove the App, Apple or Google stops accepting its notification token, and we delete the device record, and any agreements accepted on it without an account, 30 days later.
6. Your Rights
- Depending on where you live, including California, Colorado, Connecticut, Texas, Virginia and other states with consumer privacy laws, you may have the right to: (a) know what personal information we have collected about you and get a copy; (b) correct inaccurate personal information; (c) delete personal information; (d) opt out of the sale or sharing of personal information and of targeted advertising (Section 3.3); and (e) not be discriminated against for using these rights.
- To use a right, email support@rockettime.app. We will respond within 45 days, and may extend that once by 45 days where the law allows, with notice to you.
- Because you can use most of the Service without an account, we will verify a request by matching information you provide with information we hold, such as the booking reference or the email address used for a booking. We will not ask for more information than verification requires.
- You may use an authorized agent to submit a request. We may require the agent to provide your signed permission and may ask you to verify your identity directly.
- If we decline your request, you can appeal by replying to our decision with the subject "Appeal". We will respond to an appeal within 60 days. If we deny your appeal, you may contact your state attorney general.
- You can withdraw location, camera, motion and notification permissions at any time in your device's settings. Features that depend on them will stop working.
7. Children
- The Service is not directed to children under 13, and we do not knowingly collect personal information from children under 13.
- A person must be at least 18 years old to book a Trip, and a person under 18 needs a parent's or guardian's permission to create an account or buy a membership. A Trip may include travelers under 18, whose details are provided by the adult who books.
- If you believe we have collected personal information from a child under 13 other than as a traveler named by an adult, contact support@rockettime.app and we will delete it.
8. Security
- The Apps and the Site communicate with our servers over encrypted connections.
- Our servers accept requests only through Cloudflare, store sign-in sessions only as hashes, and never receive payment card details.
- No method of transmission or storage is completely secure, and we cannot guarantee the security of information.
9. International Users
- We are located in the United States. Information we collect is processed in the United States and in other countries where our service providers operate.
9.1 If You Are in the European Economic Area, the United Kingdom or Switzerland
- Edward Lukowsky, at the address in Section 11, is the controller of your personal information.
- We use your information on these legal bases: to perform our contract with you (alerts you turn on, accounts, memberships and bookings); our legitimate interests in running, securing, analyzing and improving the Service (Sections 2.9 and 2.10), which we balance against your rights; your consent where the law requires it (location, camera, motion and notification permissions, and ads, which the Apps ask for before loading them); and legal obligations (booking and tax records).
- You have the right to access, correct, delete, restrict or object to our use of your information, to receive it in a portable form, and to withdraw consent at any time without affecting earlier use. To use them, email support@rockettime.app. You can also complain to the data protection authority where you live or work.
- Your information is processed in the United States, which may not have the same data protection laws as your country. Where we rely on service providers to receive it, we use the safeguards they offer for those transfers, such as the European Commission's standard contractual clauses or the EU-US Data Privacy Framework.
- We do not make decisions about you based solely on automated processing that have legal or similarly significant effects.
10. Changes to This Privacy Policy
- We will post any change to this Privacy Policy with a new version number and effective date, and the Apps will show a notice of it. If a change materially expands how we use or disclose personal information collected before the change, we will tell you in the Apps before it takes effect.
- We will review this Privacy Policy at least once every 12 months.
11. Contact
Edward Lukowsky
18034 Ventura Blvd, Unit #655
Encino, CA 91316
support@rockettime.app