Privacy Policy
What we collect, why, who touches it, how long we keep it, and how to make us delete it. Written to be read.
Who we are
Jottings.AI ("Jottings", "we", "us") is a product of Riley Ventures LLC, d/b/a Acme Studio, 1615 S Congress Ave, Ste 103, Delray Beach, FL 33445, USA. I'm Chris Riley, and I run it. We help business owners find, prepare and license their operational data to AI companies.
This policy covers jottings.ai, the private deal portal, signing in with Google or Microsoft, connecting Microsoft files or mail, and the custody vault where connected data is held. It doesn't cover the AI companies that license data from owners. They have their own policies and are bound by the license agreement the owner signs.
Questions, requests or complaints: hello@jottings.ai. A person reads that inbox.
The short version
- We collect what you tell us, what we need to check that you and your company are real, and normal website analytics.
- Google sign-in only confirms who you are. We never ask for access to your Gmail or Google Drive. If you connect Microsoft 365, we get read-only access to files or mail, only what you choose, only for your deal.
- Connected data sits in an encrypted vault under a key unique to your deal. It goes to a buyer only after it's scrubbed, and only under an agreement you signed with that buyer.
- We don't use connected data for ads, we don't hand it to data brokers, and we don't train our own AI models on it.
- When the deal is done we destroy your deal's key and send you a certificate of deletion.
- You can revoke access at any time.
What we collect
- What you tell us. Your name, email, company name, website and role, and your answers to the calculator, intake and readiness questions (industry, headcount range, systems you use, years in business, whether you've licensed data before and to whom). If someone refers you, we get your business name from them.
- Roughly where you are. Country and state or region, from your IP address via our host. Never your city.
- Your IP address when you submit a form, and the network it belongs to, to spot duplicate and fraudulent signups. We keep the IP address for 12 months and the network for as long as we keep your lead record. It's never shared with buyers.
- Verification material you send. System totals, screenshots and an IT contact.
- Signatures. When you sign a letter of intent or agreement, our e-signature provider keeps the usual audit trail: names, emails, signatures, timestamps and IP addresses.
- Email. Messages between us, and whether you've unsubscribed.
- Website usage. Pages visited, referrer, device and browser, IP address and cookie IDs, through the analytics and advertising tags described under Cookies and tracking.
- Google or Microsoft account data, only if you sign in or connect. See Signing in and connecting.
How we check a lead is real
Buyers pay for real businesses, so we check. After you submit a form we run automated checks on your company, almost all from public sources:
- Whether your email domain accepts mail, and what mail provider and SaaS tools its public DNS records point to.
- Whether your website resolves and loads over HTTPS. We fetch your homepage once and look for your business name.
- How old the domain is (public registration data, RDAP) and when it first appeared in the Internet Archive's Wayback Machine.
You can also prove who you are: by opening a portal link we emailed you (proves the inbox), entering a 6-digit code we send to your work email, signing in with Google or Microsoft, or adding a DNS TXT record to your domain.
We may look up public company facts, like approximate employee count, by your company's domain from a business data provider (People Data Labs or Hunter). One lookup per deal, cached for 90 days. We don't send them your name or email.
We compare what you told us with what we measured, for example the staff count you gave against workspace seats, the data size you gave against your workspace's storage totals, or the record counts you gave against what we actually pulled. When a deal goes to buyers you've authorized, they see a verification summary: a level (green, amber or red), the list of checks that passed, and claimed-versus-measured numbers. Not your domain, email address or the raw evidence. Who you've licensed to before stays with us.
Signing in and connecting Google or Microsoft
Sign-in is optional. Each step is a separate click, and we ask for the least access first. With Google you can sign in and prove you're the admin; that's all. With Microsoft you can also connect files or mail for a deal. Work and school accounts only; personal Microsoft accounts are refused.
openidemailprofile- Microsoft
openidprofileemailUser.Read- Used for
- Confirms your email address at the company. We keep the verified address and when it was verified. No offline access is requested, so no token is kept.
admin.directory.user.readonlyadmin.reports.usage.readonly- Microsoft
RoleManagement.Read.DirectoryLicenseAssignment.Read.AllReports.Read.All- Used for
- Checks whether you're an administrator, counts active accounts, and reads your organization's total mail and file storage from the admin usage reports. We keep your role, the provider, the domain, the tenant ID (Microsoft), the seat count and the two storage totals (in GB, with the report date). We read the directory only to count and the usage reports only for organization-wide totals; we don't read or store per-user data or the list of users.
- Not requested
- Microsoft
Files.Read.AllSites.Read.Alloffline_access- Used for
- Microsoft only. Makes a read-only copy of the files your account can see in OneDrive and the SharePoint sites you can open into your deal's vault, for the deal you're working on.
- Not requested
- Microsoft
Mail.Readoffline_access- Used for
- Microsoft only. Makes a read-only copy of your own mailbox into your deal's vault. Deleted Items and Junk are included.
- Read-only means read-only. None of these scopes can send mail, edit or delete files, share anything, or change settings, and we don't ask for any that could.
- Your account only. Microsoft Connect reads what the signed-in account can see. It doesn't reach other employees' mailboxes or drives.
- Tokens. For Microsoft files and mail we keep a refresh token so a copy can run over hours or days. It's encrypted with your deal's key and stays on our application servers. Copy jobs get a one-hour access token, never the refresh token. Google sign-in keeps no token at all.
- If you connect Microsoft files or mail, your sign-in also counts as proof of your work email, the same as signing in alone.
- Want Gmail or Google Drive in a deal? You download or export it yourself and upload it. We never sign in to your Google account to get it, and nothing is shared with a Jottings account. See Google user data.
What happens to connected and uploaded data
Whether data arrives through Microsoft Connect, a read-only credential you paste, an IT contact, or a file upload (including Google Drive downloads, Takeout or a Workspace export), it's handled the same way:
- The vault. Copies land in our vault on Cloudflare R2 in the United States, encrypted at rest under a key unique to your deal. That key is itself encrypted under a master key we hold.
- Processing. Copy and cleaning jobs run on short-lived machines on Fly.io in the United States. Each machine is destroyed when its job ends.
- You review first. A classification sheet lists what we found. You untick anything you don't want included. By default we leave out credentials, payment data and customer personal data.
- The scrub. Before anything can leave, an automated scrub removes secrets and replaces personal data (names, emails, phone numbers, addresses, dates of birth, account and ID numbers) with consistent stand-ins. It tests itself before every job and stops rather than ship if the test fails. A second, open-source privacy engine runs on the same machines to double-check. No outside AI service sees your data.
- Checking the scrub. To confirm the scrub took out the right things, we review short snippets (about 60 characters) around values it removed. Secrets are never shown. Snippets are encrypted with your deal's key and deleted with it.
- Live keys. If we find live passwords or API keys, we email you to rotate them, and they're removed from anything we ship.
- Delivery. Data goes to a buyer only if you've signed a license agreement with that buyer naming what's included. We deliver only the cleaned package, only to storage we've confirmed belongs to that buyer, and check receipt file by file.
- Nothing else. We don't use your data in our own products and don't deliver it to anyone you haven't signed with.
Google user data and Limited Use
Jottings' use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
What that means here:
- The only Google user data we receive is from sign-in and the admin step: your verified email address and Workspace domain, whether you're an administrator, a count of active accounts, and your organization's total Gmail and Drive storage in GB (organization-wide totals only, never per user). We use it only to verify you and your company.
- We don't use or transfer it for advertising, retargeting or interest-based ads, and we never give it to ad platforms or data brokers.
- We don't sell Google user data. The only thing that leaves Jottings is the verification summary below, and only to buyers you've authorized.
- We don't use it to decide creditworthiness or for lending.
- People at Jottings see only the verification result (your verified address, admin role, seat count and storage totals) when reviewing your deal, or when needed for security or the law.
- Jottings does not use Google user data to develop, improve or train any AI or machine-learning model, and Google user data is never part of a licensed data package.
Jottings does not request access to Gmail or Google Drive content. If you choose to export files or mail yourself (for example, with Google Takeout) and upload them, that upload is handled like any other file you send us, under your license agreement, and not through Google APIs.
Admin verification data (your role, seat count and storage totals) is used only to verify your company. Buyers you've authorized see that the admin check passed and how the seat count and storage totals compare with what you told us. Nothing else from your directory or usage reports.
How long we keep things
- Raw copies in the vault: deleted within 14 days after the buyer confirms receipt.
- Everything else in the vault: within 30 days after the buyer's final payment we destroy your deal's key first, which makes the data unreadable immediately, then delete the files and send you a certificate of deletion. If you opt in to resale, we may keep the cleaned package for up to 12 months for that purpose, then delete it the same way.
- If a deal doesn't go ahead, or you just want out, ask and we'll delete your vault data the same way, key first.
- Microsoft tokens: wiped when you disconnect, when your raw copy is wiped, or when the deal is deleted. Google sign-in keeps no token to wipe.
- Lead, portal and verification records: kept while we're working with you, then as long as we need them for business records, taxes and disputes. Ask and we'll delete what we're not required to keep.
- Your opt-out: if you unsubscribe, we keep your address on a do-not-email list so it sticks.
- Copies a buyer received: governed by your license agreement with that buyer.
What we keep after deletion, on purpose: fingerprints. During cleaning we compute a keyed hash of each file and a small sample (512) of hashed lines, using a secret only we hold. They can't be turned back into your data or checked against guessed content. We keep them to spot the same data being licensed twice, which protects exclusivity for you and for buyers. Your certificate of deletion says this.
We also keep an append-only log of what happened to a deal (connected, pulled, delivered, deleted). It records events, never your data, credentials or tokens.
Turning off access
- In the portal: click Disconnect on a Microsoft-connected item, or email hello@jottings.ai. We delete our copy of the sign-in.
- Google: sign-in keeps no ongoing access, but you can remove Jottings at myaccount.google.com/permissions. Workspace admins can also block or remove the app in the Admin console under Security → Access and data control → API controls.
- Microsoft: go to myapps.microsoft.com and remove Jottings. Microsoft doesn't let an app revoke its own delegated access, so after you disconnect we delete our copy and you remove the app there. Your admin can also remove it in the Microsoft Entra admin center under Enterprise applications.
Revoking stops future copies. It doesn't delete what's already in your vault. Ask us and we will.
We send email through Resend: portal links, deal updates, reminders, verification codes and occasional news. Portal links in our emails carry a code that proves the email reached you. Our emails support one-click unsubscribe in your mail app, or use jottings.ai/unsubscribe. Unsubscribing stops our emails to that address. If you have a deal in progress, tell us how you'd like to be reached.
Cookies and tracking
On our public pages we load these third-party tags:
- Google Analytics, to see which pages people use.
- Meta Pixel, to measure and target our ads on Facebook and Instagram.
- Vibe, to measure our streaming TV ads.
- Bullseye, for advertising measurement.
When you submit a form, we also send Meta a server-side "Lead" event with your email and name hashed (SHA-256), your IP address and browser, so Meta can match it to an ad click. Hashed data is still personal data, so we're telling you.
None of these tags load in your private deal portal. The only cookies the portal and sign-in use are functional: an encrypted, 10-minute cookie that ties the Google or Microsoft round trip together, deleted when you return.
To limit tracking, block third-party cookies in your browser, use Google's Analytics opt-out add-on, or adjust your Meta ad preferences. We don't currently act on Do Not Track or Global Privacy Control signals automatically; email us and we'll stop sending your details to ad platforms.
Who we share with
- Buyers, only as you authorize. Before a license: the deal details you've approved and the verification summary above. After you sign: the cleaned package your agreement names.
- Service providers who run parts of Jottings for us, listed below. They may use your data only to provide their service to us.
- When the law requires it, or to protect people, our users or Jottings from fraud, abuse or harm.
- If Jottings is sold or merged, the buyer takes on this policy. For Google user data we'll ask your consent first.
We don't sell personal information to data brokers.
Service providers
- Vercel
- Hosts the website, portal and application servers
- United States
- Supabase
- Database for leads, the portal, deal records and the audit log
- United States
- Cloudflare (R2)
- The custody vault, encrypted with a per-deal key we hold
- United States
- Fly.io
- Short-lived machines that copy, clean and deliver data; nothing persists
- United States
- Resend
- Sends our email and keeps the unsubscribe list
- United States
- Documenso
- Electronic signatures for letters of intent and agreements
- See provider
- Google Workspace
- Stores verification files and deal documents in our company Drive
- United States
- Google and Microsoft
- Sign-in, and Microsoft connections you choose to make
- Per your account
- People Data Labs or Hunter
- Public company facts looked up by domain, when enabled
- United States
- Google Analytics, Meta, Vibe, Bullseye
- Website analytics and ad measurement, public pages only
- United States
Security
Per-deal encryption keys; temporary storage credentials scoped to one deal and one step, read-only wherever possible; delivery only to buyer storage we've confirmed in person; an append-only audit log; a one-time code for our admin console every 15 minutes; private portal links. Details are on Security.
No system is perfect. If something goes wrong with your data, we tell you directly, in plain language, and quickly.
People who appear in an owner's data
Business data can mention employees, customers or people who emailed the company. The owner decides what's in scope and is responsible for having the right to license it. We scrub personal data before anything is delivered. If you think your information is part of a deal, email us and we'll work it out with the owner.
Your rights
Wherever you live, you can ask us to show you what we hold about you, correct it, delete it, export it, or stop marketing to you. Email hello@jottings.ai. We'll confirm it's you and answer within 30 days. We won't treat you differently for asking.
US state privacy laws (California, Colorado, Connecticut, Virginia, Texas, Oregon and others) give residents rights to know, delete, correct, and opt out of the sale or sharing of personal information and of targeted advertising. We don't sell personal information for money. Our ad tags may count as "sharing" or "targeted advertising" under some of these laws; email us to opt out. You can use an authorized agent. If we turn down a request, reply to appeal and someone other than the first reviewer will look at it.
If you're in the EU, EEA or UK: Riley Ventures LLC is the controller for the data described here. We rely on contract (running your deal), legitimate interests (verifying leads, security, preventing fraud, measuring our marketing), consent (signing in and connecting accounts, and cookies where the law requires it), and legal obligations. You can also object to processing, withdraw consent at any time, and complain to your local data protection authority. Your data is processed in the United States.
Children
Jottings is for business owners and their staff. It isn't meant for anyone under 18, and we don't knowingly collect data from children. If you think we have, email us and we'll delete it.
Changes
When we change this policy we'll post it here with a new effective date. If a change is material, we'll email owners with active deals before it takes effect. We won't use Google user data in a new way without asking you first.
Contact
hello@jottings.ai, or Riley Ventures LLC, d/b/a Acme Studio, 1615 S Congress Ave, Ste 103, Delray Beach, FL 33445, USA.