Privacy policy
What princereyes.com keeps about you, who sees it, and for how long. The site is Prince Reyes's: Sage, the AI assistant that answers questions about his work, and the back office he runs it from.
Last updated 21 October 2026 · Terms of use · Privacy policy
The short version
- You can read the site and talk to Sage without an email.
- Prince reads the chats with Sage. Keep private details (yours or anyone else's) out of them.
- Sage's answers, voice calls and scope checks are made by Google's Gemini, which receives what you write or say for them.
- An email you verify is kept, and Prince sees it.
- No ads, no analytics, no trackers, and we don't sell anything about you.
What we keep, and why
Chatting with Sage
Your browser makes a random key and keeps it, with your chat's ID, so you can come back to the chat. We keep the chat itself (what you write and what Sage answers, with the time), the address of the page you started it on, and how many messages were stopped by our filters. Before a message reaches the model, it's checked against words and phrases Prince has blocked; some words are starred out for readers but kept as you wrote them. Prince reads chats in his inbox, can reply in them himself, and can switch Sage off for a chat.
Asking Prince to join
If you ask Prince to join a chat, you verify your email first, then pick what it's about and describe it. The chat moves to your account's inbox, where only you and Prince read it, and Prince gets an email with your address, the topic and your description.
Your email and account
Signing in, starting a voice call, downloading Prince's resume or asking him to join needs a verified email: we send a six-digit code to it, which expires after 10 minutes. We keep the email to sign you in, send you codes and reply to you, and Prince sees it in his list of people who have signed in, with how many voice calls you've had and when you last opened his resume. You can add a name in Account settings. Your sign-in is kept in a cookie on your browser; our sign-in service may also record the browser you used and the network address the request came from, to keep sessions secure. One account works on both princereyes.com and AyosGawa, Prince's studio site.
Documents and electronic signatures
When Prince sends a document to your email for signature, only your verified email address can open it in Dashboard → Documents. We keep the original PDF, its SHA-256 hash, your name and verified email, and an audit trail of when the document was viewed, when a six-digit signing code was sent, and when it was signed or declined (with the timestamp, browser user-agent string, typed full name, optional uploaded signature image, or decline reason). When signed, we generate and store the signed PDF with its certificate page so both you and Prince can download it.
Messages between members
Signed-in members can message each other. You see each other's name, never the email. Nobody else reads those messages, Prince included, unless you report a chat: then he receives its last 20 messages. Blocking someone deletes the chat.
Voice calls with Sage
A call goes straight from your browser to Google's Gemini Live, for up to three minutes. Google processes the audio and writes it out as text so you can read along; we don't record or store the audio or that text. We keep that you made a call and when.
The scope check
If you describe a feature in one sentence for Sage to check, we remove any links and email addresses, then keep the sentence, the page you were on, a random key your browser keeps for it, and the answer. Gemini writes the answer. Prince can read them.
Client agreements
Prince keeps each contract's client name, company, email and address, scope, clauses, pricing and payment schedule. Sending stores the PDF and its SHA-256 hash and creates a signature request addressed to the named client and email. Issued versions are kept; changes create a new version and withdraw a pending request for the old one. Prince can read these records and download the original and any signed PDF. Gmail invitations contain a link to the client's document, without an attachment.
Paying an invoice
An invoice emailed in pesos can carry a private link to pay it online. Paying happens on PayMongo's checkout: you give your card, wallet or bank details to PayMongo, never to this site. PayMongo tells us the invoice was paid, and we keep the payment's ID, method (such as GCash or card), amount and day with the invoice. Prince can read them. We keep the PDF as it was emailed, which the pay link also opens, and the addresses an invoice was emailed to, so anyone signed in with one of them sees it, and whether it's paid, in their Documents.
In your browser only
Your theme, the keys for your chat and scope checks, and a note that Sage already showed you a hint or a demo this visit are kept in your browser's storage. Clearing it removes them (and you lose your way back to a chat that isn't in an account).
Google accounts and Gmail
Google is never a way to sign in to this site. Only Prince, as the site's admin, can connect a Google account, from Account settings, and only to send his invoices and contract invitations from his own Gmail.
- What we ask for: permission to send email on his behalf (the gmail.send scope), and his Google address to show which account is connected. We never ask to read, change or delete mail.
- How it's used: an invoice or contract invitation is sent only when he reviews it and clicks Send. Gmail sends it from his account; we keep the ID of the Gmail conversation so he can open it, and nothing else from Gmail.
- How it's stored: the access and refresh tokens Google gives us are encrypted in our database and never sent to a browser or written to a log.
- Sharing: Google user data is not sold, not shared with anyone, not used for ads, and not used to train AI models.
- Disconnecting: Disconnect in Account settings removes the connection, and Google's third-party access page revokes it from Google's side.
This site's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Who sees it
- Prince Reyes: chats with Sage, requests to join, verified emails and names, scope checks, client agreements, documents and electronic signature records, and the chats you report.
- The person you message: your name and your messages.
- Google (Gemini): what you write to Sage, say on a call or describe in a scope check, to make the answer, under the Gemini API terms.
- The services the site runs on: Convex (the database and the server), Vercel (the website), Resend (sign-in codes and Prince's notices) and PayMongo (invoice payments). They hold the data for us and use it only to run those services. It may be stored outside the Philippines.
How long
Sign-in and signing codes: 10 minutes. Everything else above (chats, accounts, emails, signed documents and their audit trails, scope checks, the record of calls) is kept until Prince deletes it, or you ask him to. Issued agreements and their version history are retained as business records; contact Prince about access, corrections or retention. A chat between members goes when either of you blocks the other.
Your rights
Under the Philippines' Data Privacy Act of 2012 you can ask to see what we keep about you, have it corrected or deleted, and object to how we use it. You can change your name in Account settings; to delete your account and what's kept with it, or for anything else, reach Prince through Sage's Ask Prince on the home page, or LinkedIn.
Children
The site isn't for anyone under 13.
Changes
When this changes, the date at the top changes with it. See also the terms of use.