Privacy Policy
Effective July 11, 2026. This policy explains how CivicParkingOS processes information for public parking portals and administrative services.
1. Who controls the information
CivicParkingOS is operated by Balthrop Logic Operating Systems Inc.. For a municipal or public-agency parking program, the administering entity generally determines why permit, payment, vehicle, enforcement, and applicant information is collected and how long it must be retained. Balthrop Logic processes platform information to provide and support the service.
2. Information processed
Depending on the service and tenant configuration, CivicParkingOS may process:
- Applicant and customer information such as name, email, phone number, and mailing address.
- Vehicle information such as make, model, year, color, license plate, state or jurisdiction, and permit assignment.
- Permit applications, eligibility answers, uploaded documents, approval history, notes, and status changes.
- Parking zone, duration, session, credential, validation, and enforcement lookup information.
- Transaction amounts, fees, refunds, disputes, processor references, reconciliation, and settlement records.
- Administrative account, role, audit, device, browser, IP address, and security-event information.
3. Payment information
Card entry occurs through the payment processor configured by the parking program. CivicParkingOS does not require raw card numbers to be entered into its own public forms. The platform may retain processor identifiers, payment status, amount, fees, refund status, and reconciliation data needed to operate and audit the transaction.
4. How information is used
- Process permit applications, parking sessions, payments, refunds, credentials, renewals, and notifications.
- Support municipal review, enforcement validation, financial reporting, reconciliation, and audit requirements.
- Secure the platform, prevent misuse, troubleshoot issues, and maintain service reliability.
- Comply with contracts, records obligations, legal process, and applicable law.
5. How information is shared
Information may be shared with the administering municipality or public entity, its authorized staff and enforcement providers, the configured payment processor, hosting and email providers, integration vendors, and other service providers needed to deliver the platform. Information may also be disclosed when required by law, court order, public-records obligations, or valid government process.
CivicParkingOS does not sell personal information for monetary consideration.
6. Government records and public disclosure
Information submitted to a public entity may be subject to public-records, retention, audit, litigation hold, or disclosure laws. The administering entity determines how those laws apply to its records.
7. Retention
Retention periods vary by record type, tenant policy, contract, payment requirements, dispute status, audit needs, and law. Data may be retained after a permit or session ends when needed for financial, enforcement, security, legal, or records-management purposes.
8. Security
CivicParkingOS uses administrative, technical, and operational safeguards appropriate to the platform's functions, including tenant-aware access controls, role restrictions, protected credentials, audit history, hosted payment processing, and tokenized public links. No online system can guarantee absolute security.
9. Cookies and technical data
The platform may use essential session cookies and related technical storage for sign-in, security, tenant routing, and workflow continuity. Additional analytics or optional technologies, if enabled, should be disclosed by the administering entity or in an updated notice.
10. Access, correction, and questions
Requests to access, correct, delete, or obtain records should generally be directed to the municipality or public entity operating the parking program. Legal rights vary by jurisdiction and may be limited by government recordkeeping obligations. Platform privacy questions may be sent to admin@balthroplogic.com.
11. Policy changes
We may update this policy as the platform, contracts, or legal requirements change. The effective date at the top identifies the current version.