Privacy Policy
Effective date: October 20, 2026 · Last updated: November 2, 2026
PunchAudit is a product of Pacific Rim Software, Inc., a Washington corporation ("Pacific Rim Software," "we," "us"). This policy explains what we collect when you use punchaudit.com and the PunchAudit service (the "Service"), how we use it, and your choices.
1. Summary
- Uploaded timecard files are processed in memory and are never written to disk or our database. Uploads are discarded within about 1 hour, and full reports are purged after 24 hours.
- We do not sell or share personal information, and we do not use your data for advertising or to train AI models.
- Analytics are first-party and use no cookies. There are no third-party trackers or ad pixels. Visitors are counted using a hash that changes daily, and raw analytics events are deleted after 90 days.
- Payments are handled by Stripe. We never see your full card number.
2. Information we collect
a. Account information. We collect your email address (to send sign-in links), your organization name, your role, and your plan and billing status. We also keep a record of when you signed up and signed in.
b. Timecard files you upload ("Customer Data"). These files often contain information about your employees, such as names or IDs, punch times, breaks, and sometimes pay rates. We process them only to produce the review you requested:
- Each file is read in memory and is not saved to disk or to our database. Uploads are discarded within about 1 hour.
- The full report, including employee-level detail, is kept in memory only and is purged after 24 hours. If our server restarts, reports are lost sooner.
- We keep limited metadata about each review: the file name, a SHA-256 fingerprint (hash) of the file, row and employee counts, the date range, the states covered, the rule versions used, and counts of findings by category. This metadata contains no punch data and no employee names.
- To bill by distinct employees per month, we store a salted, one-way hash of each employee identifier. We cannot read the identifier back from the hash.
- If you save a column mapping, we store the column headers and settings only, not cell values.
c. Free tools. Information you type into the free tools (for example shift times) is processed to show the result and is not stored. We record only that the tool was used (see Analytics).
d. Billing information. Stripe collects your payment details on its own pages. We receive and store your Stripe customer and subscription IDs, your plan, your billing interval, your status, and your renewal date. We do not receive your full card number.
e. Analytics (first-party, cookie-free). When you view a page, our server records the page path (report IDs are removed), the referring website's domain only, UTM campaign tags, a device type (mobile, tablet, or desktop), a general browser family (for example "Chrome" or "Safari"; we do not store the full user-agent string), the country if our hosting provider supplies it, whether the visitor appears to be a bot or automated scanner, the time, and your user ID if you are signed in. After a page has been visible for about a second, your browser sends our server a small "page shown" signal with the page path. This signal uses no cookies, local storage, or other identifiers stored on your device; it helps us tell real visitors apart from automated traffic. To count unique visitors without cookies, we compute a keyed hash of your IP address and browser user agent using a random key that changes every day. Those daily keys are deleted after about two days, so hashes cannot be linked across days or reversed. We do not store raw IP addresses for analytics. Raw analytics events are deleted after 90 days. Daily totals (counts only, no visitor hashes) are kept longer.
f. Security and operations. We keep sign-in rate-limit counters (stored as keyed hashes, not raw emails or IPs), an append-only log of administrator actions, and short-lived server logs kept by our hosting provider.
3. Cookies
We use only the cookies needed to run the Service:
| Cookie | Purpose | Lifetime |
|---|---|---|
pa_session | Keeps you signed in | Up to 30 days, extended while you use the Service |
pa_anon | Lets you claim reports you ran before signing in | 24 hours |
We do not use advertising, analytics, or cross-site tracking cookies. Stripe sets its own cookies on its checkout and billing pages for fraud prevention. See Stripe's privacy policy.
4. How we use information
We use information to provide and secure the Service, send sign-in links and service messages, process payments, count employees for billing, respond to support requests, understand overall site usage, and comply with the law. We do not sell or "share" personal information (as California law defines those terms). We do not use it for targeted advertising, and we do not use Customer Data to train machine-learning models.
5. Service providers (subprocessors)
We use these providers to run the Service. Each processes data only on our behalf:
| Provider | Purpose | Data involved |
|---|---|---|
| Render (Render Services, Inc.) | Application hosting; uploads and reports are processed in memory here | All Service traffic, in transit and in memory |
| Neon (Neon, Inc.) | Managed Postgres database | Account, organization, billing status, review metadata, analytics |
| Resend | Sending sign-in emails | Your email address and the sign-in email |
| Stripe | Payments, subscriptions, invoices, and the billing portal | Billing contact and payment details |
| Sentry (Functional Software, Inc.) | Error monitoring. We use Sentry to receive error reports so we can fix problems. | Technical error reports (error message, code location, page path). They are configured to exclude uploaded timesheet contents, names, email addresses, cookies, request contents, and IP addresses. Your browser sends error reports to our own server, not directly to Sentry. |
These providers are located in the United States. We may update this list and will update the date above when we do.
6. Retention
| Data | Kept for |
|---|---|
| Uploaded files | In memory only; discarded within about 1 hour |
| Full reports | In memory only; purged after 24 hours |
| Review metadata and finding counts | While your account is active |
| Employee hashes for billing | 13 months |
| Raw analytics events | 90 days |
| Visitor hash keys | About 2 days |
| Error reports (Sentry) | Up to 90 days |
| Account and billing records | While your account is active, then as required for tax and accounting (typically 7 years for invoices) |
7. Customer Data and your employees
When you upload employee data, you (the employer) decide why and how it is processed, and we act as your service provider (processor). If an employee asks us about their data, we will refer the request to you. Because we keep no employee-level data after the 24-hour report window, there is usually nothing left to provide or delete.
8. Your choices and rights
You can access and update your account information, download your reports while they are available, cancel your subscription, and ask us to delete your account by emailing support@punchaudit.com. We will verify your request and respond within 45 days. We will not discriminate against you for exercising your rights.
California (CCPA/CPRA). Based on our current size and practices, we believe Pacific Rim Software is not a "business" subject to the California Consumer Privacy Act as amended by the CPRA. We have well under $25 million in annual revenue (as adjusted), we buy, sell, or share the personal information of fewer than 100,000 consumers or households, and we earn no revenue from selling or sharing personal information. We nonetheless follow its core principles: we do not sell or share personal information, we limit collection to what we need, and we honor access and deletion requests from anyone, including California residents.
Washington (My Health My Data Act). We do not collect, process, or seek "consumer health data" as Washington's My Health My Data Act (RCW 19.373) defines it, and the Act excludes individuals acting in an employment context. We therefore believe the Act does not apply to the Service. Please do not upload medical or health information.
Other U.S. states. If you live in a state with a comprehensive privacy law, contact us to exercise any rights that apply to you.
9. Security
We use HTTPS everywhere, store sign-in tokens and sessions as hashes, isolate each organization's data with database row-level security, keep uploads out of storage entirely, and limit administrator access. No system is perfectly secure. If a breach affects your personal information, we will notify you as required by law, including Washington's breach-notification law (RCW 19.255).
10. Children
The Service is for businesses and is not directed to children. We do not knowingly collect personal information from anyone under 18 (or under 13 for the purposes of COPPA). If you believe a child gave us information, contact us and we will delete it.
11. International users
The Service is intended for U.S. businesses, and data is processed in the United States.
12. Changes
If we change this policy, we will post the update and change the date above. For material changes, we will notify account holders by email before they take effect.
13. Contact
Pacific Rim Software, Inc. · Washington, USA
Email: support@punchaudit.com (privacy requests: put "Privacy" in the subject line)