Security & Delivery

What a company needs before spending serious money

Plain answers to the questions a careful buyer asks first — ownership, credentials, private files, milestones, and proof. No fine print games.

Who's behind GLEE

· The business

GLEE Phoenix — sovereign progress infrastructure. Operated from Alberta, Canada.

· How billing works

Paid work is invoiced through your GLEE account on Square rails — a deposit before work, milestones after. No investment, equity, or token claims.

· Response time

We reply to inquiries within 1–2 business days.

· No secrets in intake

We never ask for passwords, card details, private keys, or bank credentials when you inquire or get scoped.

How work is owned, handled, and delivered

01 Who owns the work product?

You do. Deliverables and source transfer to you on milestone acceptance. GLEE keeps only what's needed to honor the receipt trail.

02 How are credentials handled?

Least-privilege and short-lived. We ask for the narrowest access that gets the job done, and never store secrets in chat, email, or receipts.

03 How are private files transferred?

Over permissioned channels you control. Public-safe work leaves public receipts; private material stays on the private boundary and is not published.

04 How are milestones accepted?

Each milestone has fixed scope and acceptance criteria agreed up front. You review the result and accept before the next milestone — and before further payment.

05 What proof does the client receive?

A receipt trail: what changed, what was tested, what was verified, and what remains. Public-safe outcomes are inspectable in the receipt archive.

06 What happens if scope expands?

It's surfaced, not silently absorbed. If the work grows beyond the agreed slice, you see the change and approve it before it proceeds.

07 What data is public vs private?

You decide per engagement. By default, only work you approve for public proof becomes public; everything else stays private.

What GLEE will never ask for

  • Passwords, private keys, wallet recovery secrets, or bank credentials in chat or email
  • Card numbers over chat — payment is only ever via official invoices and approved rails
  • Production crypto, x402, or agent-native payments (those rails are testnet-only and clearly labeled)
  • Broad standing access when a narrow, revocable grant will do
Request a scoped sprint See public proof →
← Back to Work Mode