What I keep, and why.
I’m Ashley. I use what you share to review your project, reply to you, and arrange a call if we decide to work together. Here’s what happens to that information.
Updated October 5, 2026
Your request
When you register, I save your name and email. If you continue, I also save the problem you describe, the links and access notes you share, my reply, and the status of your review. You can return using your email and a one-time sign-in code. Your browser stores a session cookie; signing out removes access from that browser. Older saved private links still grant access, so keep them private.
I use these details to decide whether I can help and to do the review you asked for. I don’t sell them or use them for ad targeting.
Project access
Public or read-only links are usually enough. If you invite me into a separate service, removing the link from this site does not revoke that invitation. I track accepted invitations for removal in that service and keep unresolved removals on my operator list until they’re verified.
Figma’s file_content:read grant can cover more than the file you share. This app opens only the file you choose. You can revoke the connection in Figma’s settings.
Please don’t put passwords, API keys, or production secrets in your request.
Email, payment, and meetings
Cloudflare hosts the site and its database. Resend sends confirmation and service emails and reports delivery or failures. If you opt in, verify your email, and I recommend more time, I may send optional reminders; you can unsubscribe. Stripe handles checkout; this site keeps payment references and status, not card numbers. Proton Meet hosts calls, with a private room link shown after booking.
Cloudflare Web Analytics measures visits to the public pages: the page path, the referring site, country, browser, operating system, device type, and how quickly the page loaded. It doesn’t record the query part of a link, and Cloudflare says it doesn’t track individual visitors across other sites. The admin and email-preference pages aren’t measured.
Those providers may keep their own operational records under their policies. Email already sent and Stripe payment records are outside this site’s deletion schedule.
Optional preparation and AI chat
You can save four short preparation answers for me without using AI. When enabled, you can separately choose to let TypeSafe’s Jev check these answers or let a Telnyx AI assistant read these answers and your preparation chat. You can also separately choose to let my OpenAI assistant read the four answers and draft a private meeting brief for me. These assistants do not approve your request, handle payments, or book an appointment.
The assistants receive only the preparation text you choose to share, not your contact details, project links, connected files, or access notes. Please do not include secrets or private customer information. Changing the answers or withdrawing consent clears the stored AI suggestions and chat on this site and deletes the saved OpenAI brief; it cannot recall information already sent to a provider. TypeSafe, Telnyx and OpenAI handle shared information under their own policies. You can ask me to remove preparation content from the connected assistant; withdrawing consent prevents further reads but cannot recall information already sent.
Preparation answers, chat and saved internal meeting briefs follow your project’s cleanup schedule. Anonymous provider usage counts may remain to enforce spending limits. Telephone calls and SMS are not enabled for preparation.
My availability
You do not connect a calendar. When I connect my own Google calendars, Vibe Check requests only the start and end of busy periods through Google’s availability-only permission. It does not request event titles, descriptions, guests, or locations.
When configured, the site checks those times before publishing or offering appointments. It does not save the busy periods in customer records or show them to customers. My Google refresh credential stays in server-side Cloudflare secrets until I disconnect it. If the calendars are not connected or Google cannot be checked, calls pause.
Deletion and questions
An unfinished draft reaches its cleanup cutoff seven days after registration. For an unpaid submitted request, the seven-day deadline starts only when you confirm that all project materials are shared; editing does not restart it. A declined request reaches its cleanup cutoff within a week of the decline. A paid written answer or booked call reaches its cutoff within a week after the answer is posted or the appointment ends.
Cleanup usually runs about every 15 minutes after a cutoff. It clears contact details, project content, replies, the paid answer, queued messages, and browser sessions and access through any older private request link from the active site. An uncertain payment, provider failure, backlog, or outage can delay removal. Connected access I control is removed or tracked for verified removal. Separate account invitations require action in the service where you granted them.
Sign-in codes expire after ten minutes; browser sessions last up to thirty days and are removed with the request during cleanup. Sign-in retry limits use short-lived hashes rather than raw email or IP addresses. A keyed hash of your email may remain with an offer redemption to enforce its once-per-customer limit; it does not include your raw email. Payment references, amounts, audit events, campaign labels, email suppression hashes, and references needed to finish access removal may remain. Sent email and provider records follow separate policies. Cloudflare’s database recovery history can retain earlier data for its own recovery window.
For a privacy question or an access-removal request, email [email protected].