Role and responsibilities: Brandon Perez, CTO and co-founder, Greenlight Date

Download as PDF · Plain text

Prepared November 4, 2026 for Greenlight Date company documents.

Summary

Brandon Perez is the Chief Technology Officer (CTO) and a co-founder of Greenlight Date (greenlightdate.com). He is responsible for the company's product and technology in full: the member-facing web app, the Android app, the systems behind them, security and member data privacy, the technical side of legal compliance, and the tools the team uses to run the service. He has built and operated all of it since the company's first code on May 14, 2026.

Areas of responsibility

Product and engineering

He owns the design, construction and release of the Greenlight application.

• The web app frontend (the screens members use) and the API (the server that stores and returns data).
• Feature design and build, from specification to release.
• The API contract, a written definition of how the app and the server talk to each other.
• Automated tests that check the code before release.
• Code review and the release gates every change must pass.

Infrastructure and operations

He owns the hosting, data storage and day-to-day operation of the service.

• Hosting of the web app on Cloudflare Pages and of the API on Google Cloud Run.
• The Supabase Postgres database and Supabase authentication (member sign-in).
• Google Cloud Storage for member photos and video.
• Database migrations (recorded changes to the database structure), with a backup taken before each one.
• A tested rollback (a way to return to the previous version) for every release.
• Error tracking and uptime monitoring.

Security and member data privacy

He owns the protection of member accounts and member data.

• Account isolation, so no member can reach another member's account or files.
• Removal of EXIF and GPS data (hidden location and device details) from every uploaded photo and video.
• Upload limits and rate limits (caps on how often a request can be made).
• Bot protection on signup and login.
• An audit trail of staff actions.
• Data retention and deletion policies, and a privacy policy kept accurate with every product change, including any change to message scanning.

Legal and compliance, technical side

He owns the technical implementation of the company's legal obligations.

• Retention of evidence for member reports, as New York law requires.
• Fraud-ban notices to New York members.
• Written policies: the DMCA takedown policy, the child-safety (CSAM) response procedure, the admin holds operator guide, the fraud ban notification policy, and the Didit data protection assessment.
• He works with Jude on legal requirements and implements them in the product.

Identity verification and trust and safety

He owns the systems that confirm member identity and keep members safe.

• Identity document checks through Didit.
• A manual verification path for staff when the vendor service cannot be used.
• Photo moderation.
• Scam scanning of chat messages and offer notes.
• Blocking, unmatching and reporting.
• Selfie-to-profile face matching, built and running in evaluation mode, not yet member-facing.

Payments and billing

He owns the payment systems.

• Stripe subscriptions and checkout.
• The billing portal where members manage and cancel subscriptions.
• Refund lookup for staff.
• Payment correctness and reconciliation.

Member communications

He owns the systems that send messages to members.

• Transactional and campaign email: welcome, confirmation, reminders, weekly availability and event invites.
• Push notifications.
• The SMS program on Telnyx, including carrier campaign registration and consent design that meets the Telephone Consumer Protection Act (TCPA).
• The public SMS opt-in page.

Product design and brand

He owns the visual design and written content of the product.

• The design system, the written rules that govern every screen.
• The visual design of the app and the marketing site, including dark mode and themes.
• All in-app copy.
• The marketing site.

Analytics

He owns the measurement of how members use the product.

• First-party product analytics (collected by the company, not shared with ad networks).
• The admin analytics panel.
• Measurement of member activity, with a standing ban on session replay (screen recording of member sessions).

Admin console and support tooling

He owns the internal tools staff use to run the service and support members.

• One screen per member, and staff actions for pause, delete, email change, refund lookup, photo review and ID review.
• The signup queue, the member timeline and risk labels.
• Live-event tools: event-only Discover, the host raffle, and event and partner referral links.
• Email templates and batch send.
• Routing for the support@greenlightdate.com mailbox.

Mobile

He owns the Android app.

• Built with Capacitor (a framework that packages the web app as a native app).
• Packaged for distribution through Google Play.

Creative and marketing assets

He owns the production of the company's video and print marketing assets.

• Member testimonial videos, edited and delivered: captions, end cards, audio cleanup, encoding, and a private review site.
• Demo walkthrough videos, including the investor demo now in production.
• Flyers, posters and social ads.
• Signup QR codes.
• He supplied the logo and references for the event banner.

Vendors and tooling

He owns the company's technical vendor relationships and engineering tools.

• He selects, configures, secures and manages every technical vendor: Cloudflare, Google Cloud, Supabase, Stripe, Didit, Telnyx, Resend, PostHog and GitHub.
• He owns the engineering tooling and automation the company builds with.

Decision authority

Brandon Perez holds final authority over the company's technical decisions. Legal, finance and company policy decisions belong to Jude. Where those decisions have a technical side, he implements it. He decides:

• Technical architecture and the technology stack.
• Vendor selection for technical services.
• Release go or no-go, and rollback.
• Security posture and incident response.
• Implementation of data retention and privacy requirements.
• Engineering process and review standards.

Systems and vendors

Record of work to date

The figures below are as of November 4, 2026, on the main code branch.

Milestones

• May 14, 2026: first code.
• Jun 6, 2026: privacy policy and terms of service.
• Jul 17, 2026: automated tests and first security work.
• Jul 19, 2026: tracked database migrations.
• Jul 25, 2026: design system.
• Aug 14, 2026: full end-to-end release test.
• Sep 1 to 13, 2026: written product plan and engineering documentation.
• Sep 9, 2026: error alarms.
• Sep 10, 2026: product analytics.
• Sep 21, 2026: referral links.
• Sep 23, 2026: face match evaluation mode begins.
• Oct 2026: SMS program designed and Telnyx carrier campaign submitted.
• Nov 4, 2026: post-date reviews live.