Payments stay in the portal.
Cards, saved payment methods, invoices, receipts, and recurring billing are handled inside the yegIT portal and its payment provider. This public site does not store card data.
Trust center
Support that is visible, authorized, and documented.
yegIT uses the customer portal for tickets, invoices, recurring service records, and payment paths. Remote support and account work should be clear to the customer, logged, and tied back to a real request.
Remote support rule
No hidden access. No stealth tools. No surprise sessions.
Remote access is for approved support work and should be connected to a customer request or service record.
MFA is the standard for privileged access.
Technician and admin accounts should use MFA, strong passwords, named users, and least-privilege access wherever the platform supports it.
Remote sessions should be auditable.
Take-control sessions, support launches, and technician actions should be tied to the customer, asset, user, and reason for service.
Secrets are handled separately from normal notes.
Passwords, TOTP seeds, shared links, and secure records should be permissioned, revealed only when needed, and logged when viewed or copied.
Security baseline
What yegIT builds toward
Customer portal access is separated from public website content. Ticket, billing, and recurring payment records live in the portal instead of the marketing site.
Service work should leave a trail: who requested it, who touched it, what changed, and what was communicated back to the customer.
Support tools should have a normal uninstall path. yegIT does not design stealth access, credential dumping, AV bypass, or persistence evasion into customer systems.