Privacy Policy
Version 1.1
Effective Date: 2026-10-25 (America/Chicago)
1. RESPONSIBLE PRIVACY FUNCTION
Pigeon Serve LLC — Privacy Team / Owner is responsible for privacy requests. Contact support@pigeonserve.com or the postal address/phone below. This policy covers the PIGEON website, services and Process Server field app.
2. INFORMATION AND PURPOSES
PIGEON handles legal names and contact details (email, phone and address), account/authentication records, service instructions and uploaded legal documents, case/court information, authorized evidence, communications, transaction records and audit/timestamp data. E-Service also collects date of birth where required by its recipient identity flow. These categories support the requested service, account management, security, payments and legal/evidentiary recordkeeping.
Identity workflows may require front/back government-ID images, one selfie, email verification, device location and capture/framing guidance, followed by authorized human/Admin review. No reusable biometric template or face-geometry profile is intentionally created or retained at launch. Capture-quality guidance is not identity scoring. Automated face matching/liveness is not claimed without verified implementation; any discovered biometric processing is blocked pending notice, consent, vendor and retention controls.
PIGEON Field camera and precise location are collected only when required for authorized field work/attempt evidence, using foreground/user-initiated collection. No continuous background tracking at launch. E-Service/identity sessions may collect location where their approved verification requires it. Authorized access depends on the workload and record. Raw ID images, selfies and identity-review material are restricted to authorized Admin/reviewers. Clients receive their own authorized status and final records, not raw recipient or Student identity evidence. Other Students, Clients and Process Servers do not gain access merely by holding an account. Protected course media requires eligible authenticated Student enrollment.
Student data may include contact/account information, required identity verification, enrollment, access/progress, completion, assessments where used, payment and student-supplied credential/application details. No remote proctoring or automatic government/approving-organization reporting is activated without an approved, implemented and disclosed program.
3. PAYMENT INFORMATION
Stripe handles raw payment and Connect banking details. PIGEON may retain customer/account/reference IDs, PaymentIntent/payment IDs, amount/currency, payment/refund/dispute status, invoice/receipt references, card brand/last four if supplied, Connect onboarding/payout eligibility and earning/payout references. PIGEON does not store full card number, CVV, full bank-account number or raw bank routing credentials.
4. CHOICES, MARKETING AND SENSITIVE COLLECTION
PIGEON does not sell personal information, share personal information for cross-context behavioral advertising, use personal data for targeted advertising, or perform advertising profiling. Marketing promotional email, optional analytics and advertising tracking are disabled at launch. If PIGEON later offers marketing subscriptions, participation requires a separate, optional, unchecked affirmative opt-in, not account creation alone; authorized marketing email includes a functioning unsubscribe option. Promotional consent and transactional account/security/job/payment communication preferences remain separate.
Sensitive ID/selfie/location/signature/evidence collection requires disclosure/consent immediately before the relevant workflow. Withdrawal stops future optional collection/processing where possible but does not invalidate or erase lawfully collected completed-service evidence, legal holds, fraud/security investigations or retained records. Marketing email may be enabled only after separate opt-in, preference storage, unsubscribe controls and applicable requirements are implemented and verified. Required service/security communications remain separate and do not become marketing by default.
5. PROVIDERS AND LOCATION OF PROCESSING
Only verified active providers belong in the final inventory. Google/Firebase/Google Cloud provide functions actually configured for authentication, databases, storage, backend/hosting or security; Google Workspace is business email; Maps is included only where used; Stripe supports payment/Connect infrastructure. Apple/Google Play are distribution/device platforms only where applicable. Courts/filing providers receive information when required for an actual filing. No future EFSP API is represented as active; manual filing is described truthfully.
PIGEON is U.S.-focused and primary production hosting should use approved U.S. regions where available. Providers may process information in locations where they operate under applicable agreements/safeguards; PIGEON does not promise every subprocessor operation is U.S.-only. Final deployed vendor/SDK inventory remains a publication gate.
6. RETENTION AND DELETION
Job/service records: 7 years after completion/closure, including attempts, affidavits, court-filing records, E-Service audit records, field evidence, GPS, evidentiary photographs and job-related communications.
Billing, accounting, payment, refund and payout records: 7 years.
Process Server application, credential and earnings records: 7 years after the relationship ends.
Student enrollment, completion and certificate records: 7 years after completion/withdrawal.
Raw E-Service recipient identity evidence (government-ID front/back images and single-selfie photographs) is scheduled for secure deletion 90 days after the completed identity-review decision, except where lawful preservation requirements apply or a mandatory earlier destruction deadline controls. Necessary E-Service proof, verification decisions, timestamps and audit records are retained separately under the applicable service/evidentiary schedule without unnecessarily retaining raw images. Deletion must verify active disputes, security investigations, statutory requirements, legal holds and record dependencies; an unresolved conflict requires review, not automatic destruction. This E-Service 90-day rule is not a blanket deletion rule for Student identity materials or Texas online-notary journals/recordings, which require their own verified service-specific schedules and legal treatment.
PIGEON does not intentionally create or retain reusable biometric templates or face-geometry profiles at launch. Any actual biometric processing remains subject to separately verified notice, consent, vendor and retention controls. Where Texas biometric-identifier law applies, destruction must satisfy its applicable statutory requirements; the 90-day default does not replace an earlier applicable legal deadline. A hold does not automatically override statutory destruction obligations: any conflict requires documented legal review of the applicable exception. A photograph is not presumed to be a derived biometric identifier merely because it is an ID image or selfie.
Unpaid abandoned drafts: 30 days after last meaningful activity, only where no legal, payment, dispute or preservation hold applies; purge only draft-only protected data that is not referenced by another active/completed service.
Unpaid incomplete Student enrollments: 30 days after last meaningful enrollment activity, subject to the same approved deletion safeguards. Paid/active Student access remains four calendar months; existing course, certificate and audit-record retention is unchanged.
Temporary identity/copies-session artifacts (session, challenge, verification-code, replay/rate and temporary retrieval-authorization state): 30 days after session completion or expiration, except where needed for an active security investigation, dispute or legal hold. This schedule does not govern final service or audit records.
General security, login, IP and technical logs: 12 months, unless needed for an active security investigation.
General support/complaint records not part of a job: 3 years after closure.
Electronic consent/signature audit records: 7 years after the applicable transaction/relationship closes.
Optional cookie preferences, if later enabled with owner approval: 12 months per browser/device.
Deleted production data is removed from active systems under the applicable retention/deletion process. Backup copies expire through the normal approved backup lifecycle rather than individual editing where technically impractical. No fixed backup-expiration period is promised until the actual backup lifecycle and deletion propagation have been technically verified; this notice does not assert immediate deletion from every backup copy. Deleted information must not be intentionally restored into active use. If disaster recovery restores a backup, applicable deletion state must be reapplied before that data returns to active use. Any lawful preservation exception remains subject to restricted access and applicable law.
A legal hold or specific law may require longer retention. Retained records are restricted from unrelated use. This is a proposed launch retention schedule; lifecycle enforcement, applicable legal exceptions and disclosure accuracy must be verified before public activation.
Access, correction, deletion and other rights required by applicable law are handled through verified privacy requests. Verify requester identity before exposing or deleting protected information. Deletion is subject to lawful exceptions, including required legal records, active disputes, fraud/security investigations, payment/accounting obligations, litigation/legal holds and other applicable requirements. Records not subject to those obligations are eligible for verified deletion handling; retained records are restricted from unrelated use. Receipt or review does not itself execute deletion. Before any automated destruction, verify references to signed acknowledgments, affidavits, court-filing reports, certificates, payments, disputes and required audit records; ambiguous or unresolved dependencies prevent automated deletion and require review. PIGEON cannot delete records independently held by courts or other organizations.
7. SECURITY
Protected production documents and identity evidence use private storage, authenticated or narrowly scoped secure-session access, and role, ownership, assignment or enrollment checks. Managed encryption, restricted credentials and audit records support these safeguards. No system is absolutely secure. A request for historical records remains subject to verification and the access controls applicable to those records; this notice does not certify every historical object or promise an unverified backup or deletion process.
8. REQUESTS AND APPEALS
Use /privacy-choices for authenticated access, correction, deletion, portability, consent-withdrawal or appeal requests, or contact support@pigeonserve.com. Account-specific information requires verification. Standard response target: within 45 days of a verified request; one additional 45-day extension if reasonably necessary, with notice. Privacy Team reviews appeals with a written decision target within 60 days. If denied and applicable law requires, the official Texas Attorney General complaint mechanism is provided. These are PIGEON default service standards, not a representation that every statutory threshold necessarily applies.
9. AGE, COOKIES AND CHANGES
All account holders, including Students, must be 18 or older. No minor/parental-account workflow at launch. A minor subject/recipient does not thereby receive an account. Cookie Preferences: /cookie-policy#preferences. Privacy appeal: /privacy-choices?type=appeal. Material practice changes are reviewed and reflected prospectively; retained accepted versions remain auditable.
Pigeon Serve LLC — PIGEON
7250 West Greens Rd, Ste 314, Houston, TX 77064
support@pigeonserve.com · billing@pigeonserve.com · (713) 454-2146