Privacy Policy
1. Who We Are
U.S. Software Professionals, Inc. ("USSP") is an Illinois corporation operating Aria, a customer intelligence product for family-entertainment-park operators. Contact us with any questions about how we handle your data.
2. Two Kinds of Data
Customer Data — data about an Aria customer's end-customers (park visitors, members, party guests). USSP processes this on behalf of the Aria customer. Data ownership, retention, breach notification, and security commitments live in Sections 4–8 of the SaaS Terms.
Portal User Data — data about Aria customer staff who use the Aria portal (name, email, password hash, sign-in logs). USSP is the controller. This Privacy Policy governs.
3. What We Collect About Portal Users
- Name and email (for sign-in)
- Password (stored as a salted hash, never plaintext)
- Sign-in timestamps and IP addresses (for security)
- Routes visited (for usage analytics, when implemented)
4. Why We Collect It
- To provide and secure the service
- To investigate abuse or security incidents
- To improve the product (in aggregated, de-identified form)
We don't sell portal data. We don't use it for advertising.
5. Subprocessors and Where Data Is Stored
USSP uses third-party services to operate Aria. All data is stored in the United States. The current list of subprocessors:
| Subprocessor | Purpose | Region | Data categories |
|---|---|---|---|
| Neon (Neon Inc.) | Postgres database hosting | United States | All Customer Data |
| Railway (Railway Corp.) | Application/portal hosting | United States | Portal-rendered Customer Data, sign-in logs |
| Twilio (Twilio Inc.) | SMS sending and receiving (parks not yet moved to Telnyx) | United States | Phone numbers, message content, send/receive logs |
| Telnyx (Telnyx LLC) | SMS sending and receiving; marketing email sending for parks that enable email | United States | Phone numbers, email addresses, message content, delivery and engagement events (delivered, bounced, opened, unsubscribed, complained) |
| OpenRouter (OpenRouter, Inc.) | AI gateway for all AI features (SMS reply classification and tagging, reports and readouts, email drafting and checking). Requests are routed to the underlying model providers, currently OpenAI for most workloads, with Anthropic and MiniMax models used for some. | United States (gateway); the underlying model provider processes the request | SMS reply text; park-level aggregated analytics and park-authored content used to draft reports and emails. Not used to train models on Customer Data. |
| Railway Storage Buckets (Railway Corp.; storage provided by Tigris) | Object storage for generated reports, uploaded documents, and (for email) brand images and published email pages | United States | Reports and documents containing Customer Data; park logos and photos |
| AgentMail (AgentMail) | Transactional notification email to park staff (for example, an alert when a customer replies to a text) | United States | Staff email addresses; the customer's reply text and phone number in reply alerts |
| Stripe (Stripe, Inc.) | Billing for the Aria subscription and messaging credits | United States (Stripe-managed infrastructure) | Aria customer (park) billing contact name and email, subscription and payment records. No park visitor or end-customer data. Card details are entered on Stripe-hosted pages and never reach USSP. |
| Google Fonts | Web fonts on the public landing page | Global Google CDN | IP address (visitor only — no Customer Data) |
| GitHub Actions | Scheduled background jobs (data refresh) | United States | Operational secrets only (no Customer Data flows through Actions logs) |
Customer-controlled tools (e.g., Klaviyo, Meta) are not USSP subprocessors — Customer exports CSVs from Aria and uses their own credentials with their own platforms. USSP does not process payment card numbers of end-customers (park visitors); Stripe is used only to bill Aria customers.
USSP gives Customer at least 30 days' notice before adding a new subprocessor. See SaaS Terms Section 5.
5A. Marketing Email Sent on a Park's Behalf
When an Aria customer (a park) enables email, USSP sends marketing email for that park, such as birthday reminders, offers, and event news, as the park's processor. The park is responsible for holding any required email marketing consent (SaaS Terms Section 4). USSP processes the following Customer Data for this purpose:
- Email addresses and message content of the park's adult customers and account holders. USSP does not email minors.
- Engagement data: opens (measured with a small tracking image, and approximate because some email apps load images automatically) and clicks (measured with tracked links). Clicks may be used to credit a booking to an email.
- Unsubscribes, bounces and complaints, which USSP and its email provider honor right away. Every marketing email has a one-click unsubscribe link. An unsubscribe applies to that park only and is separate from text message opt-outs.
Emails are sent through Telnyx and stored images and pages through Railway Storage Buckets (Section 5). USSP does not sell this data or use it for any purpose other than the park's own email program.
6. Security
USSP applies layered safeguards to Customer Data and Portal User Data:
- Encryption. TLS in transit; cloud-provider-managed encryption at rest.
- Access controls. Role-based access, salted password hashing, least privilege. USSP staff with access to Customer Data are bound by confidentiality obligations.
- Logical separation. Customer data is partitioned by
park_id; portal queries are park-scoped so one customer cannot see another's data. - Vendor security. Subprocessors (above) are required to handle data with reasonable security commitments.
- Incident detection. USSP monitors key services for outage and intrusion signals.
- Breach notification. Confirmed personal-data breaches are notified to Customer within 72 hours per SaaS Terms Section 7.
- Audit. Once per 12 months, on at least 30 days' written notice, Customer may request written confirmation of USSP's compliance with these commitments.
What we don't do: sell Customer Data, cross-target across customers, hold payment card numbers, or train AI models on Customer Data without explicit permission.
7. How Long We Keep It
- Active portal user records: while the user is active, plus 12 months after their last sign-in.
- Sign-in logs: 24 months.
- Customer Data (separately): typically 30 days after termination unless the customer requests earlier deletion. See SaaS Terms Section 8.
- Backups: deleted or anonymized within 90 days of termination.
8. Your Rights
If you are an end-customer of an Aria customer (e.g., a park visitor whose visit was logged), please contact the park directly. They control your data.
If you are an Aria customer staff user, you can ask us to (a) tell you what we have about you, (b) correct it, (c) delete it (subject to legal retention obligations), or (d) stop processing it (this typically means terminating your portal account). Contact us to exercise these rights.
9. Children
Aria isn't directed at children. The product processes data about families and may include child names and ages because that's what the Aria customer provides. Aria customers are responsible for the lawful collection and use of children's data under COPPA and other applicable law.
10. State Privacy Rights (CCPA/CPRA and Similar)
We don't sell or share personal information for cross-context behavioral advertising. State-specific rights are honored where applicable. Contact us to exercise them.
11. Cookies
The Aria portal uses session cookies (essential — required to keep you signed in). It does not currently use advertising or analytics cookies.
12. Changes
If we materially change this policy, we will update the "Last Updated" date and email portal users at least 14 days before the change takes effect.
13. Contact
Contact USSP
U.S. Software Professionals, Inc., Illinois