What we do with your information.

We collect what you type into our forms (the contact form, and the referral form if someone sends us a referral), a count of page views that can’t identify you, what Stripe needs if you pay an invoice here, and, if you sign an agreement here, your signature and the record of how you signed it. If you book an appointment with a business that uses JRD Booking, our booking service, we hold your booking for that business (section 10). If that business connects its Google Calendar, JRD Booking sees only when the people who work there are busy, never what their events are, and adds your booking to their calendar. If you order from, or reserve an item at, a store that uses JRD Shop, our shop service, we hold your order or request for that store, and Stripe takes the payment on its own checkout page (section 11). No advertising cookies, no advertising pixels, nothing sold. The one place a third party sets cookies is the payment page, where Stripe uses them to stop fraud. If you want something deleted, email us and it’s deleted, except a signed agreement, which is kept unchanged for seven years.

A summary, not the policy. The sections below are.

Who this is

JRD Animation is the trading name of JRD Animation LLC, a Florida limited liability company based in Orlando, Florida, United States. Where this policy says “we” or “us”, that’s who it means. You can reach us at hello@jrdanimation.com about anything on this page.

What we collect

From the contact form, only the fields you fill in: your name, your email address, the project type you select, the budget range you select, and whatever you write in the message box.

From the referral form, which is for people we’ve invited to recommend us: the referrer’s name, email, phone and how they’d like to be paid, and the name, business, contact details, website and needs of the person or business they’re recommending. The form asks the referrer to confirm that person agreed to be contacted. If you were referred to us and didn’t expect to hear from us, tell us and we’ll delete your details. The referral page can also remember the referrer’s own details in their browser, on their device only, so they don’t have to type them again.

From the payment page, if you pay an invoice there: your card or bank details are typed into Stripe’s own fields and go straight to Stripe, our payment processor. They never pass through our servers and we never see the full number. What we get back from Stripe is a record of the payment: your name and email, the card type and its last four digits, the billing postal code, and whether it went through. If something goes wrong while you pay, the page sends us a short report so we can fix it: the invoice, the error you were shown, which payment option was open, your browser and screen size, and your approximate location. It never includes your card or bank details, which the page can’t read.

From the signing page, if you sign an agreement with us there: what you type into the agreement’s fields, any file it asks you to attach (a logo or photos, say), the signature and initials you adopt, and, for each step (opening it, agreeing to sign electronically, signing or declining), the time, your IP address and your browser and device type. We already have your name and email address, because that is where we sent it. That record is what makes an electronic signature hold up, and it is printed on the signed copy you receive. If we pay you a referral fee, the Form W-9 we ask for is signed the same way, and its tax identification number is used only to report those payments to the IRS.

From Vercel Web Analytics, a count of page views. It records the address of the page, the site that sent you, your approximate location, and your browser, operating system and device type. It doesn’t use cookies to recognize you. Vercel tells visitors apart with a hash of the request and discards it after 24 hours, so it can’t follow you from one day to the next or from this site to another. On the payment page the invoice reference is stripped from the address before the view is counted.

From the server, the ordinary request records our hosting provider keeps: IP address, browser type, the page requested and the time. These are generated automatically by the act of loading a web page and we don’t combine them with anything else or use them to identify you.

If you become a client, whatever you send us to do the work: content, images, logins, business details, and the billing information needed to invoice you.

What we don’t collect

We don’t run Google Analytics, advertising pixels, session recorders or heatmaps. The page view count described above is the only analytics on this site, and it identifies no one. We set no cookies for tracking, advertising or profiling, and we don’t buy or receive information about you from anyone else.

The payment page is the one exception on cookies, and it isn’t ours. Stripe’s payment form sets cookies and reads information about your device to detect fraud. It loads only on that page, and only once there is an invoice to pay; no other page on this site loads Stripe at all.

If that changes, this page changes first, and the date at the top changes with it.

Why we use it

To reply to you, to quote and carry out work you hire us for, to invoice you, to run the booking system for businesses that use JRD Booking, to contact a business someone has referred to us and pay the referral fee, and to keep the records a business is required to keep. That’s the whole list. We don’t use your information to market to you, and we don’t add you to a mailing list because you contacted us.

Who else sees it

Only the services that run the site, our booking and shop services, our email, our agreements and our payments:

• Vercel. Hosting, and the page view count. Serves this site, JRD Booking and JRD Shop, and keeps the server request records described above.
• Neon. The database behind JRD Booking and JRD Shop. Stores the bookings, orders, pickup requests and customer details described in sections 10 and 11.
• Brevo. Email delivery. Sends the messages from our forms to our inbox, sends JRD Booking’s booking emails and JRD Shop’s order and pickup emails, sends agreements to be signed and the signed copies, and keeps the list of referrals, which is never used to send email.
• Google Workspace. Our email. Your message sits in our inbox like any other email.
• Google Fonts. The typefaces this site uses. Your browser fetches them from Google, which receives your IP address, your browser and operating system, and the address of the page you’re on. Google says it uses that only to send the fonts and for security, sets no cookies, and doesn’t use it to profile you or for advertising.
• Google Calendar. Only when a business connects its calendars to JRD Booking. JRD Booking reads when that business’s people are busy and adds each booking, with the customer’s details, to the calendar they choose, where Google keeps it under the business’s own Google account. See section 10.
• Push services. Apple, Google, Mozilla and Microsoft deliver JRD Booking’s notifications to the phones and computers of the people at a business who turn them on. Each notification is encrypted so that only that device can read it. See section 10.
• Google sign-in. Only when someone who runs a store on JRD Shop chooses Continue with Google: Google confirms their email address, and we keep their Google account’s number to recognize them. See section 11.
• Cloudflare. Agreement and backup storage. Agreements signed on our signing page, the files attached to them, and the record of each step described in section 02, are encrypted before they are stored with Cloudflare R2, with a key only we hold. A tax identification number on a Form W-9 is locked a second time, with a key that exists only on our own computer, so neither our website nor Cloudflare can read it; everywhere else, your signed copy included, it shows as its last four digits. JRD Booking’s nightly backups are stored there too, encrypted before they leave our servers with a key only we hold, and each is deleted after 30 days.
• PandaDoc. Agreements and W-9 tax forms sent before 2 October 2026, when we built our own signing page. Those went through PandaDoc, which recorded your name, email and signature.
• Stripe. Payments, on the payment page, on the sign-up links for our monthly plans, and for the deposit invoice raised when you sign an agreement that asks for a deposit, for which Stripe receives your name and email. It also takes the payments made in stores that use JRD Shop, in each store’s own Stripe account (section 11). Stripe collects identifying information about the devices that connect to its services and uses it to run and improve them, including to detect fraud. Its privacy policy is at stripe.com/privacy.
• PayPal. Only if someone we pay a referral fee chooses PayPal: the payment is sent to the email address they give us.

Each of these acts on our instructions and under their own privacy terms. Nobody else receives your information. We don’t sell it, rent it, trade it, or hand it over for advertising.

We will disclose information if the law requires it, such as a court order or a lawful demand from an authority with the power to make one. If that happens and we’re permitted to tell you, we will.

How long we keep it

Contact form messages that don’t turn into work: up to 12 months, then deleted.

Referrals that don’t turn into work: up to 12 months, then deleted. Records of referral fees we’ve paid are kept like client records.

Bookings taken through JRD Booking: for as long as the business they were made with uses it, and deleted 90 days after it stops, or sooner if the business or the customer asks, as section 10 describes. Our encrypted backups hold a copy for up to 30 days more.

What Google Calendar tells JRD Booking: the times someone is busy, for at most a day; the access a business gives us, until it disconnects its calendar, as section 10 describes.

Where JRD Booking sends notifications: each device’s address until the person turns notifications off or removes the device, or the push service says it no longer works, as section 10 describes.

Orders and pickup requests taken through JRD Shop: pickup requests, and the emails about requests and orders, 90 days; the customer’s name, email, phone and shipping address on an online order, 90 days after the order is finished, with the rest kept as the store’s sales record; everything of a store’s, 90 days after it stops using JRD Shop, or sooner if it asks, as section 11 describes.

Client records: for as long as we’re working together, and afterwards for as long as United States federal and Florida tax and business record rules require us to keep them.

Signed agreements and the record of how they were signed: seven years from the day they are sent. The signing system has no way to change or delete them, and the storage they sit in is locked against changes and deletion for those seven years, because an agreement is only worth something if neither side can quietly alter it. The same goes for an agreement that is declined, withdrawn or never signed.

Server request records: however long our hosting provider retains them, which is a matter of their retention policy, not ours.

Where it’s stored

On servers operated by the providers named in section 05. Those providers run infrastructure in several countries, so your information may be processed outside the United States, and information stored in another country may be accessible to that country’s courts and authorities under its own laws. If that’s a problem for you, say so before you send us anything and we’ll work out another way.

Your rights

There is no single federal privacy law in the United States that covers a business this size, and Florida’s Digital Bill of Rights applies only to companies far larger than ours. So the rights below are ones we give you because they’re the right ones to give, not because a statute forces us to, which means we can’t quietly withdraw them either, since this page is the promise.

Email hello@jrdanimation.com and you can ask what personal information we hold about you, ask us to correct it, ask us to delete it, or withdraw consent to our using it. We’ll answer within 30 days. The only things we’ll refuse to delete are a record we’re legally required to keep and a signed agreement within the seven years described in section 06, and we’ll tell you specifically which one rather than hiding behind the phrase.

Visitors outside the United States. If you’re in the UK, the EU, Canada or another region with its own data protection law, those laws may give you additional rights, such as access, portability, erasure and objection. Ask and we’ll honor them. Given how little we collect, there is very little to argue about.

Sites we build for other people

If you arrived here from a site we built for a client, this policy does not cover that site. The client controls it and their own privacy policy applies. Where we hold data on their behalf, we hold it under their instructions and we don’t use it for anything of our own.

Client sites we build ship with an editor. The content in that editor belongs to the client.

Bookings made through JRD Booking on a client’s site are covered in section 10, and orders and pickup requests made through JRD Shop in section 11.

Booking with a business that uses JRD Booking

Some businesses use JRD Booking, our booking service, to take appointments on their own website or at book.jrdanimation.com. If you book with one of them, the business decides what it asks and what it does with your booking. We run the booking system for that business and hold your details on its behalf, under its instructions.

What is collected: your name, your email address and your phone number if you give it, the service, person and time you choose, the language you booked in, any note you add, and your answers to the questions the business asks. To keep the system from being flooded, it also counts requests against a scrambled form of your IP address, and those counts are deleted within a day.

Why: to book your appointment, send you the confirmation and any change or cancellation emails (with a calendar file), send you a reminder before the appointment if the business has reminders on, let you move or cancel from the link in your email, and tell the business. Nothing else. We don’t add you to a mailing list and we don’t sell it. The business may contact you about your appointment.

Who sees it: the business you booked with, and the providers that run the system: Vercel, which hosts it; Neon, the database that stores the bookings; and Brevo, which sends the emails. Every night a copy of the database is backed up to Cloudflare R2, encrypted with a key only we hold, and each copy is deleted after 30 days. A booking page may load the business’s font from Google Fonts, which, like any service a web page loads from, sees your IP address. If the business has connected Google Calendar, your booking is also added to its calendar at Google, as described below.

How long: for as long as the business uses JRD Booking. If it stops, its bookings and its customers’ details are taken off its booking page, not used for anything, and deleted 90 days later (sooner if the business asks), then leave our backups within 30 days, as those are deleted. You can ask us to delete your own details at any time, as section 08 describes. The business may keep its own copy, under its own policy.

Your choices: to change or cancel a booking, use the link in your confirmation email. Anyone with that link can open the booking, so keep the email to yourself. To see, correct or delete your details, ask the business you booked with, or email hello@jrdanimation.com and we’ll pass your request to the business and help it answer.

Booking pages set no cookies and store nothing in your browser.

Google Calendar: a business can connect the Google Calendar of each person who works there. This part covers the Google data that connection gives us, for the person who connects a calendar and for you as a customer when you book with them.

What we get from Google: when the person is busy in the calendars they choose, as start and end times only (we never see what their events are, where they are or who is invited); the names of their calendars, so they can choose which ones count (we show the names and keep only the calendars they pick); and the Google account’s email address, to show which account is connected.

What we put in Google Calendar: each booking with that person, in the calendar they choose: the service, the date and time, the customer’s name, email, phone and answers to the business’s questions, the business’s note about the booking, and a link to it in JRD Booking. We update it when the booking moves and remove it when it’s cancelled. We never read, change or delete any other event. If you book with a business that has connected Google Calendar, those details are also kept in that person’s calendar, under their own Google account and Google’s terms.

How we use it: only to keep customers from being offered times when the person is busy, and to keep their calendar in step with their bookings. Nothing else.

How we keep it: the access Google gives JRD Booking is encrypted in our database (Neon) and used only by JRD Booking’s own servers. Busy times are kept for at most a day, so booking pages load quickly, and then deleted. No one at JRD Animation reads Google data, except with your permission to help with a problem, to keep the service secure, or when the law requires it.

Who we share it with: no one. We don’t sell Google data, use it for advertising, give it to data brokers or use it to train AI models. It passes only through the providers that run JRD Booking (Vercel and Neon), on our instructions.

How long, and how to stop it: until the calendar is disconnected. Disconnecting in the JRD Booking app ends our access and deletes the access and busy times we stored straight away. Removing JRD Booking from your Google Account (myaccount.google.com/connections) also ends our access at once; the busy times are deleted then, and the rest when the business disconnects it in the app or stops using JRD Booking. We keep a short record that a calendar was connected or disconnected, with the Google account’s email address and the date, for as long as we keep the business’s booking records. Bookings already added to Google Calendar stay there, because they’re in the person’s own calendar; they can delete them like any other event.

Limited Use: JRD Booking’s use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.

Notifications on phones and computers: the people who work at a business can turn on notifications in the JRD Booking app, so a new, moved or cancelled booking shows up on their phone or computer. For each device that turns them on, we store the address its push service gives us and a name for the device, such as “iPhone” or “Chrome on Windows”, so they can see it and remove it. A notification shows the customer’s first name and last initial, the service, the day and time and who it’s with, never their email, phone, answers or notes, and each person can hide even that on their lock screen. Each one is encrypted on our servers so that only that device can read it, then delivered by the push service of the phone or browser maker (Apple, Google, Mozilla or Microsoft), which can’t read it. We delete a device’s address when the person turns notifications off or removes the device, or when the push service tells us it no longer works.

Buying from a store that uses JRD Shop

Some stores use JRD Shop, our online shop service, for the shop pages on their own website. If you order from one of them, or ask one to set an item aside for you to pick up, the store decides what it does with your order or request. We run the shop system for that store and hold your details on its behalf, under its instructions.

What is collected: when you ask a store to set an item aside, your name, your phone number, your email address if you give it, any note you add, the item, size and store you chose, and the page you asked from. When you buy online, the items, the store you pick up from or your shipping address, and the name, email address and phone number you give on Stripe’s checkout page, which Stripe passes to us with the outcome of the payment. A store takes at most 3 pickup requests a day from one phone number, to keep the system from being flooded.

Why: to set your item aside or take your order, send you an email confirming it if you gave an email address, tell the store, and let the store call you about it. Nothing else. We don’t add you to a mailing list and we don’t sell it. The store may contact you about your order or request.

Payments: card payments go through the store’s own Stripe account, on Stripe’s checkout page. Your card details go only to Stripe; we never see or store them. Stripe uses its own cookies on that page to stop fraud, under its own privacy policy.

Who sees it: the store you ordered from, and the providers that run the system: Vercel, which hosts it; Neon, the database that stores the orders and requests; Brevo, which sends the emails; and Stripe, which takes the payment for the store.

How long: pickup requests, and every email sent about a request or an order, are deleted 90 days after they’re made. On an online order, your name, email address, phone number and shipping address are removed 90 days after the order is picked up, shipped, cancelled or refunded; what was bought, for how much and when stays as the store’s sales record. If a store stops using JRD Shop, its shop comes off its website, its data is not used for anything, and it is deleted 90 days later (sooner if the store asks). You can ask us to delete your own details at any time, as section 08 describes. The store, and Stripe, may keep their own copies, under their own policies.

Your choices: to change or cancel an order or a pickup request, contact the store. To see, correct or delete your details, ask the store, or email hello@jrdanimation.com and we’ll pass your request to the store and help it answer.

JRD Shop itself sets no cookies while you shop. A store’s website may keep what’s in your bag in your browser until you check out.

People who run a store: if you sign in to the JRD Shop app, we keep your email address and name, the stores you can open, when you last signed in, and a record of what you changed (each stock change and each pickup request’s status), which the store sees in its History. Signing in sets one cookie that keeps you signed in on that device for 30 days; we store only a scrambled form of it, with a description of the browser it was made in. Sign-in codes are kept only in a scrambled form and stop working after 15 minutes. If you choose Continue with Google, Google confirms your email address, and we keep only your Google account’s number to recognize you next time. If you turn on two-step sign-in, its secret is stored encrypted.

Children

This site is aimed at businesses and isn’t directed at children. We don’t knowingly collect information from anyone under 13. If you believe a child has sent us something, email us and we’ll delete it.

Security

We use reputable providers, accounts protected by two-factor authentication, and connections encrypted in transit. That is honest but not a guarantee. No one can promise a transmission over the internet is perfectly secure, and you should be suspicious of anyone who does.

Changes to this policy

If this policy changes we’ll update the date at the top. If a change is significant, such as collecting something we don’t collect today, we’ll say so plainly here rather than quietly editing a sentence.

Updated 7 November 2026 to add JRD Shop, our online shop service: what it collects for the stores that use it, how long it keeps it, and what it keeps about the people who run those stores (section 11), and where it appears in sections 05 and 06.

Updated 22 October 2026 to describe the notifications JRD Booking can send to the phones and computers of the people at a business, and the push services that deliver them (sections 05, 06 and 10).

Updated 18 October 2026 to describe JRD Booking’s reminder emails and its nightly encrypted backups with Cloudflare R2, each kept 30 days (sections 05, 06 and 10).

Updated 14 October 2026 to describe how JRD Booking connects to Google Calendar: what it reads from Google, what it adds to a business’s calendar, how long it keeps it, and Google’s Limited Use requirements (sections 05, 06 and 10).

Updated 13 October 2026 to add JRD Booking, our booking service: what it collects for the businesses that use it (section 10), Neon as its database, and how long bookings are kept; and to name Google Fonts, which serves this site’s typefaces (section 05).

Updated 12 October 2026 to describe the short error report the payment page sends us when a payment runs into a problem.

Updated 2 October 2026 to describe our own signing page, the storage of signed agreements with Cloudflare, how long signed agreements are kept, files attached when signing, deposit invoices, and how a tax number on a Form W-9 is kept.

Updated 22 September 2026 to describe the payment page and Stripe, agreements signed through PandaDoc, and the page view count, and to correct the record keeping line in section 06, which named the wrong country.

Questions or complaints

Email hello@jrdanimation.com. If we can’t resolve it between us, you can file a complaint with the Federal Trade Commission at reportfraud.ftc.gov, or with the Florida Attorney General’s office at myfloridalegal.com.