JobRhino Privacy Policy

Who we are

JobRhino LLC, 4655 Osage Beach Pkwy Ste A, Osage Beach, MO 65065. Privacy questions: chase@jobrhino.pro

The short version

• JobRhino is a work tool for contractor companies. What goes into it is your company's business information and your customers' contact details.
• Your company decides what goes in and who on your team can see it. We handle it to run JobRhino for your company.
• We do not sell anyone's information. JobRhino shows no ads and has no advertising ID or tracking tools in it.
• The app does not track where you are.
• You can delete your account in the app, or start at https://app.jobrhino.pro/account-deletion

What we collect and why

1. Your account

Your name, your work email, your username, the company you work for, and your role there (for example Owner, Office, Sales or Crew). Your password is stored scrambled, so no one can read it, including us. If you turn on two-step sign-in, we keep its secret key locked (encrypted).

Why: so you can sign in, see the right work, and keep your account safe.

2. Sign-in and security records

When you sign in, we record the time, a scrambled form of your internet address, and the browser or phone you used. The phone app also sends three more things: the phone's browser details, which can name the phone's model and system version; which kind of phone it is (iPhone, Android or web); and which version of the app you have.

Why: to spot sign-ins that should not happen, to let your office sign out a lost phone, and to tell an old version of the app to update.

The web sign-in, account setup and password-reset pages use Cloudflare Turnstile to check that a person, not a robot, is using them. Cloudflare sees your internet address when those pages open. The phone app's sign-in does not use it.

If you sign an agreement form for your company, or open one sent to you to sign, we keep your internet address and browser with that form, as proof of who signed and when.

Our servers also keep a log of each request your phone or browser makes: the time, the address it asked for, and the internet address it came from. When you search in JobRhino, the words you typed can be part of that address. We use these logs to keep JobRhino working and safe, and they are deleted as they age out.

3. Your company's work

Everything you and your team type, tap, photograph or attach in JobRhino is your company's business record. That includes:

• customers and their homes: names, phone numbers, email addresses, service addresses, and property details such as foundation type or square footage
• proposals, jobs, appointments, invoices and payment status
• messages to and from customers by email or text
• photos and files: job, inspection and Pricebook photos, logos, badges, and documents you attach
• signatures: a customer's typed name and, where used, a drawn signature
• notes, checklists and follow ups
• your work time: when you start, take a break, take lunch and stop. This is a clock, not a location.
• presentations your team shows a customer: which presentation, how long it was on screen, and for which customer or job, so your company can see what gets used

Why: so your office and your crew see the same work, and so JobRhino can make the documents, messages and bills your company asks it to make.

On a customer's or job's page, JobRhino can show a Google map of the service address. To draw the map, the address goes to Google, and Google may set its own cookies in your browser.

4. What the phone app keeps on your phone

So the app works with no signal, it keeps on your phone:

• a copy of what you opened: today's stops and jobs, and on the Sales side the customers, proposals and follow ups you looked at. These copies hold customers' names, phone numbers, emails and addresses.
• time entries waiting to send
• an on-site proposal you started, with the customer's name, phone, email and address, the photos you took for it, and any signature the customer drew
• the last few customers, jobs and proposals you opened, for the Recently viewed list
• your sign-in keys, your Company ID, which side of the app you use, your light-or-dark choice, and a scrambled form of your customer-mode code

Signing out clears your sign-in keys, the copies of what you opened, and time entries waiting to send. Some things can stay on the phone after you sign out: on-site proposals with their photos and signatures, the Recently viewed list, your Company ID, and your app choices. Deleting the app removes everything it kept on the phone.

5. Camera and photos

The app opens the camera or your photo library only when you tap a photo button. It sends only the photo you take or pick. It does not look through your photos on its own.

When you tap Directions, the address opens in your phone's map app. Call and Text open your phone's own phone and messages apps.

6. Phone and browser alerts (optional)

Alerts are off until you turn them on in Account, then Your alerts. When you turn them on:

• On an iPhone or Android phone, the app gets a push address for that phone from Google Firebase Cloud Messaging. iPhones also use Apple Push Notification service. The app sends the push address to JobRhino, and we keep it locked (encrypted) and tied to your sign-in on that phone.
• In a web browser, your browser's own push service gives JobRhino a push address, and we keep it locked the same way.
• A phone alert says only "Proposal accepted. Open JobRhino to review it." It names no customer, address or price. A browser alert carries only an alert number.
• We delete the push address when you turn alerts off, when you sign out on that phone, or when Google, Apple or your browser tells us it no longer works.

The iPhone and Android apps include Google's Firebase Cloud Messaging library only to deliver alerts. To do that, Firebase gives the app on your phone an ID (an installation ID) that Google receives. JobRhino gets the phone's push address only after you turn alerts on.

7. Rhino, Ask and Autodraft (AI)

JobRhino's assistant, Rhino, uses OpenAI to answer questions and write drafts. When someone at your company asks Rhino a question, uses Autodraft to write a message, or asks Rhino to lay out the Home review, JobRhino sends OpenAI the records needed for that one request. For example, Autodraft for a message sends the customer's name, address and recent messages, and Autodraft for a Pricebook item sends the item's name, description and service. If your company turns on the Friday digest email, JobRhino also uses OpenAI once a week to lay out that email.

• In the phone app, Autodraft asks for your OK before its first draft. After that, it still sends nothing until you tap Autodraft. To take back your OK, stop using Autodraft.
• JobRhino asks OpenAI not to store its answers. OpenAI may still keep request records for up to 30 days to watch for misuse, or longer when required by law or needed to protect its services or other people. JobRhino does not allow these records to be used to train a general-purpose AI model.
• Rhino can carry out a supported change to a JobRhino appointment when a person with the right access clearly asks for that change. That request can give permission without a second confirmation. Rhino asks for missing details or a decision when the request is unclear or needs a separate choice, such as overriding a scheduling conflict. Customer messages and other actions keep the review steps shown in JobRhino. Calendar monitoring alone does not give Rhino permission to change the schedule.
• Rhino conversations expire after 30 days. After that, no one can open them again, and they are deleted.

8. Calendar connection (optional)

Google Calendar is optional. When a company owner or administrator selects Connect Google Calendar, Google asks the Google account holder to authorize JobRhino to identify the account, read its calendar list, and view and edit calendar events. Google's event permission is broad enough to allow access to events across calendars available to that account. JobRhino's current feature lists available calendars and synchronizes events only on calendars the owner or administrator explicitly maps in JobRhino. The person connecting should choose an account and mapped calendar appropriate for the company's work.

Where calendar assistance is available, you can also connect Google Calendar for Rhino. The connection notice explains that Rhino will monitor busy times on the calendars you choose and help with scheduling changes you request. You then authorize access through Google to identify the account, read its calendar list and read events. This connection cannot edit Google events. JobRhino keeps this permission separate from ordinary calendar sync; an existing sync connection is not automatically enrolled in calendar assistance. Your company must have the right to share the chosen calendar's information with JobRhino for this use. The permissions Google shows can cover more calendars than you choose; JobRhino limits its use to the calendars selected for that connection.

To establish and maintain the connection, we receive the Google account identifier and email address and OAuth access and refresh tokens. We store those tokens in encrypted form. We use the calendar-list permission to display calendar names and identifiers, primary-calendar status, and whether the account can edit a calendar.

For a mapped calendar, Google's API returns event information so JobRhino can calculate busy time, detect changes, and synchronize JobRhino scheduling records. The API response can include more fields than JobRhino needs. The current synchronization code processes those responses but retains, for native Google events, event identifiers, versions and status, and occupied start and end times rather than storing native event titles, descriptions, locations, or attendees in JobRhino busy blocks. We also retain the selected calendar's identifier, synchronization cursors, connection and notification state, timestamps, errors, and review records needed to resolve changes to linked JobRhino appointments.

For calendar assistance, JobRhino checks the selected calendars in the background to keep busy times current. Rhino uses those times and connection status, together with JobRhino records the person asking is allowed to see, to answer scheduling questions. Only the information needed for a requested answer may be shared with OpenAI; native Google event titles, descriptions, locations, and attendees are not sent as calendar context. Monitoring does not give Rhino permission to move or remove events on its own. Supported changes to JobRhino appointments require a clear request from someone with permission to make the change. Ordinary calendar sync, if connected, copies those changes to Google as described below. Rhino does not edit events created separately in Google. JobRhino records who requested the change and its result.

JobRhino may create, update, or remove Google events on an explicitly mapped calendar for JobRhino-owned scheduling records. An event sent to Google contains its JobRhino title and start and end times, plus private identifiers used to recognize the corresponding JobRhino record. A title may itself identify a customer or another person. The current event payload does not send customer contact details, notes, addresses, attendees, or financial fields as separate event fields. If a linked Google event is moved or removed, JobRhino presents the change for an authorized user to review; removing it in Google does not automatically cancel the JobRhino appointment. Google change notifications tell JobRhino when to synchronize again.

We use Google user data only for the visible Calendar connection, calendar assistance, scheduling, busy-time, and change-review features requested by the user; to maintain and secure those features; or as otherwise permitted by the Google API Services User Data Policy and applicable law. Our use and transfer of information received from Google Workspace follows Google's User Data Policy, including its Limited Use requirements: https://developers.google.com/workspace/workspace-api-user-data-developer-policy. We do not sell Google user data, send it to data brokers or advertising networks, use it for advertising or credit decisions, or use it to train a general-purpose AI model. Personnel do not routinely read Google event data. Human access to Google user data is limited to specific data a user affirmatively asks us to inspect, a necessary security or abuse investigation, compliance with applicable law, or permitted aggregate internal operations.

The connected Google account receives the JobRhino events its authorized user directs us to create or update. Providers that host, store, or secure the Calendar feature may process Google-derived data on our behalf only as needed for that user-facing feature, with access restrictions. We do not expose one company's Google Calendar data to another customer. We otherwise transfer Google user data only as allowed by Google's limited-use requirements, including for security or legal compliance, or as part of a business transfer after obtaining the user's explicit prior consent.

A company owner or administrator can disconnect either calendar connection in JobRhino. Disconnecting stops future synchronization or monitoring and clears the access and refresh tokens stored for that connection. Where the connection has created Google copies, the owner or administrator chooses whether future JobRhino-created copies in Google are removed or kept as static events. Past JobRhino-created Google events are not changed merely because the connection is disconnected. JobRhino may retain the connected account's email and identifier, selected calendar identifiers, event links, synchronization and audit records, and historical busy-time records. Imported busy-time records are marked removed or kept as static busy-time information according to the disconnect choice. Rhino cannot use a disconnected calendar for fresh monitoring or new calendar actions. Information already included in a Rhino conversation follows the 30-day conversation period in section 7. Disconnecting does not erase every past record or itself revoke permission on Google's account page. The Google account holder can also revoke JobRhino's access in Google Account settings; Google may apply that revocation to both JobRhino calendar connections, which then need to be reconnected before they can work again.

A company can connect a Microsoft (Outlook or Microsoft 365) calendar instead, in the same way. We then receive the Microsoft account's email and ID and keep its access keys locked (encrypted), sync only the calendars your company picks, and stop syncing and clear those keys when your company disconnects it.

9. Payments

• When your customer pays an invoice online, they type their card or bank details on Stripe's secure page, not ours. JobRhino never sees or stores card numbers. Stripe tells us the amount and whether the payment went through.
• To pay your company, Stripe collects your company's business and bank details and checks identity, as the law requires. That information goes to Stripe.
• Your company's own JobRhino bill is handled by Stripe too.

10. If you are a contractor's customer

The contractor decides what to keep about you and is responsible for it. JobRhino keeps it for them.

• When you open a proposal, an agreement form or a payment link, we note when. Opening or signing an agreement form also records your internet address and browser.
• When you accept a proposal, we keep your typed name, your email, any signature you draw, the time, your internet address and your browser's name with the signed proposal, as proof of signing.
• If you reply to the contractor's email or text, your reply comes into JobRhino.
• If you text STOP, JobRhino records it and stops texts from that contractor to your number.

To see, change or delete your information, ask the contractor first. The contractor can change your details in JobRhino. A contractor cannot delete a customer in JobRhino on their own, so to have your information deleted, you or the contractor can write to chase@jobrhino.pro and we will do it with the contractor.

11. If JobRhino contacts your business

JobRhino keeps a sales list of contracting businesses that might want JobRhino. It holds each business's name and the work details of people there: name, job title, work email and work phone. These come from public lists, such as the National Radon Proficiency Program's list of radon professionals; from business websites and other public business listings, gathered by our own research tool; from companies that sell business contact details, such as Apollo, Clay and Hunter, which we ask about a business or person by name; and from what people tell us, for example when they ask for a demo. The list can also hold a link to a person's public LinkedIn profile and, sometimes, a mobile phone number. We also keep notes of our calls, emails and texts with them.

We make these sales calls through Twilio, and we do not record them. Before a call, JobRhino can use OpenAI to write short notes for the caller from what the list holds about the business and from the business's own website.

We use this list only to tell those businesses about JobRhino. Every sales email sent from JobRhino has a link to stop them. To stop our texts, reply STOP. To stop hearing from us at all, or to ask what we hold about you, write to chase@jobrhino.pro.

12. Texting sign-up (optional)

Before a company can send texts through JobRhino, the phone companies require a sign-up that names the business and a person responsible for it. JobRhino shows Twilio's sign-up form for this. The form is run by Persona, a company Twilio uses to collect and check these details. What you type into the form goes to Twilio and Persona. JobRhino keeps whether the sign-up was approved and the business details it needs to send your company's texts.

Who helps us run JobRhino

These companies handle information for us. Each one gets only what it needs to do its part, may use it only to do that part for JobRhino, and must protect it at least as well as this policy does.

• Railway: hosts JobRhino, its database, its stored files and its server logs. It holds everything stored in JobRhino.
• Cloudflare: the robot check on the web sign-in, account setup and password-reset pages. It sees your internet address on those pages.
• Resend: sends and receives email. It sees the addresses, the message and any attachments.
• Twilio: sends and receives texts, and connects JobRhino's own sales calls. It sees the phone numbers, the message, and call details such as how long a call lasted and how clear it was.
• Persona: runs Twilio's texting sign-up form. It sees what is typed into that form.
• Stripe: payments and billing. It sees names, emails, amounts, and the card and bank details people type on Stripe's pages.
• Google (Firebase Cloud Messaging): delivers alerts to iPhones and Android phones. It sees the push address, the installation ID and the alert text, which names no customer.
• Apple (Apple Push Notification service): delivers alerts to iPhones. It sees the same.
• Your browser's push service: delivers browser alerts. It sees the push address and an alert number.
• Google or Microsoft: calendar sync, only if your company connects a calendar.
• Google (Maps): draws the map of a service address. It sees the address and may set its own cookies.
• OpenAI: Rhino, Ask and Autodraft, and the notes before JobRhino's own sales calls, as described above.
• Sentry: tells us when something breaks. An error report can include details of the record that was open when the error happened.

We may also share information when the law requires it, to protect people or JobRhino from harm, or as part of a sale or merger of JobRhino's business.

Where your information is stored

Today, JobRhino's servers, database and stored files are in Amsterdam, the Netherlands, run by Railway. We plan to move them to the eastern United States, and we will update this page when we do. Several of the companies above, such as OpenAI, Stripe, Twilio, Resend, Google and Apple, are based in the United States and may handle information there.

How long we keep it

• While your company uses JobRhino, we keep its records. Your company can change them at any time. To have a customer deleted, see Deleting your information.
• After a company closes its JobRhino account, it can download its records for 30 days. Ordinary records stay recoverable for 90 days.
• After 90 days, we delete or make anonymous: customers' names, contact details and addresses; messages; notes; imported customer lists; and every stored photo and file, signed copies too. We also remove the sign-ins and personal details of everyone on the company's team. That includes the owner who closed the account. If someone also works for another company that uses JobRhino, they keep their sign-in for that company and lose access to this one.
• Some records stay, as proof of the work done and what was agreed: jobs, appointments, proposals and invoices; who signed what and when, with the signer's name, email, internet address and browser; and text consent and STOP records. They can still show a customer's name and address as written on them.
• We also keep billing and payment records, tax records, security records, and anything the law says to keep.
• Server logs and backup copies are replaced on a schedule. Old ones are deleted.
• A phone stays signed in while you use it at least once every 30 days. Signing out ends it.
• Push addresses and OpenAI records are kept as described above.

Deleting your information

• Your account: in the JobRhino app, open Account (on the Sales side: More, then Account and settings) and tap Delete my account. Or start at https://app.jobrhino.pro/account-deletion, which explains the steps and how to ask by email.
• If you are a team member, your sign-in and your personal details are removed. The work you did stays with your company, because it is the company's record, and it shows as "Former team member".
• If you are your company's only owner, deleting your account starts closing your company's JobRhino account, and you are signed out everywhere. For 30 days you can sign in on the web to download your company's records. After 90 days, your company's records are deleted or made anonymous as How long we keep it says, and your own sign-in and personal details are removed.
• Just this phone: sign out, then delete the app. Signing out alone leaves some things on the phone (see 4).
• A customer's information: ask the company that entered it, or write to chase@jobrhino.pro.
• JobRhino's sales list: write to chase@jobrhino.pro.
• Anything else: write to chase@jobrhino.pro. We may need to check who you are first.

Your choices and rights

You can ask us to show you, correct, delete, or give you a copy of your personal information. Write to chase@jobrhino.pro. We will answer within the time the law requires, and we will not treat you differently for asking.

Depending on where you live, the law may give you more rights. If we say no to a request, you can ask us to look at it again: write to chase@jobrhino.pro with "Appeal" in the subject, and we will answer within the time the law requires. We do not sell personal information or share it for advertising, and we do not use it to make decisions about people that have legal or similarly serious effects.

You can take back an OK at any time:

• Alerts: turn them off in Account, then Your alerts.
• Autodraft: stop using it. Nothing goes to OpenAI for Autodraft unless you tap it.
• Calendar: your company can disconnect it in JobRhino, or the account holder can remove JobRhino's access in their Google or Microsoft account.
• Texts from a contractor through JobRhino: reply STOP.
• Sales emails from JobRhino: use the link at the bottom of the email.

How we protect it

• Everything between your phone or browser and JobRhino travels encrypted.
• Passwords are stored scrambled. Two-step secrets, push addresses and keys for connected services are stored locked (encrypted).
• Each company's records are kept apart from every other company's, and the database itself enforces it.
• A phone's sign-in key lasts 15 minutes and renews quietly. If a phone is lost, your office can sign it out or turn off your access, and the phone stops working with JobRhino on its next request.
• No system is perfectly safe. If something goes wrong that affects your information, we will tell you as the law requires.

Cookies

JobRhino on the web uses one cookie of its own. It keeps you signed in and protects forms from misuse, so JobRhino cannot work without it. Cloudflare's robot check may set its own cookie on the sign-in, account setup and password-reset pages, and Google may set cookies when a map is shown. JobRhino uses no advertising or analytics cookies.

Where JobRhino is offered

JobRhino is offered to companies in the United States. The iPhone and Android apps are listed in the United States only.

Children

JobRhino is made for businesses and the people who work for them. It is not meant for children, and we do not knowingly collect information from children under 13. If you think a child's information is in JobRhino, write to us and we will delete it.

Changes to this policy

When we change this policy, we post the new version on this page with its date. If a change affects how we use your information in a big way, we will email company owners before it takes effect.

Contact

JobRhino LLC, 4655 Osage Beach Pkwy Ste A, Osage Beach, MO 65065

chase@jobrhino.pro