Privacy Policy
Effective date: October 17, 2026
Version: 2026-10-17
About this policy
Hyun Jun Na, operating under the ClearOps Labs brand, provides ClearClaim. This policy describes information handled through our marketing website, email inquiries, and the employee reimbursement product. Visiting the website or asking about a demo is separate from using a school account to submit or review reimbursement requests.
Website visits and cookies
The website includes sign-in features provided by Clerk. These features use cookies and similar browser information to support authentication and sessions, including recognizing whether you are signed in. You can manage cookies through your browser settings; blocking them may affect sign-in features.
Serving website pages involves technical request information, such as your IP address, browser information, and the requested page. Hosting and authentication services handle technical information to deliver pages and support sign-in. This information is separate from the reimbursement records you enter in the product.
Email inquiries
Our Contact and demo links open your email application. The website does not submit a demo form. If you email us, your message provides your email address, any sender name, message content, and attachments you choose to include. This may include your school name and whether you are considering a pilot or school-wide operation.
If your inquiry is received, its content can be used to respond and discuss the demo, onboarding, or support you request. Your email service and, when delivery is available, the receiving email service handle the message. Please avoid including reimbursement receipts or other personal information that is unnecessary for an initial inquiry.
Information in the product
Account and school records include account identifiers, names or display names, email addresses, school organization membership, department assignment, role, and membership status. These records support sign-in, school access, and routing requests to the appropriate reviewers.
Reimbursement records include the requester, request title and description, expense dates, vendors, categories, business purposes, amounts, currencies, and request status. Receipt attachments include the file contents, filename, file type and size, uploader, and upload records. Receipts and descriptions can contain personal information you choose to submit.
Approval and payment records include reviewer identities, assigned approval steps, decisions, notes, status changes, and timestamps. Payment recording includes the recorded payment method, reference, notes, amount, and the person recording the payment. These records support review, approval history, finance handoff, and payment tracking.
Receipt scanning is optional. If receipt scanning is available and you choose ‘Scan receipt,’ a new OCR processing run sends the entire uploaded receipt image file to OpenAI for automated extraction. An existing extraction result may be reused without a new image transmission. Extracted fields can include the vendor, date, amount, currency, tax, and receipt number. Successful extraction results and processing records are stored when processing completes, before you choose Save changes for the expense item. Storing an extraction result is separate from applying selected values to the expense item and saving those changes. You choose which suggested fields to apply.
Access and service providers
School access depends on organization membership, role, and the request involved. Requesters can access their own requests. Assigned approvers can access relevant review and decision records. School owners, administrators, and finance users have broader access for their assigned work. Receipt access is checked separately from access to a request. Finance exports can include requester names and email addresses together with expense and payment information.
Server-side product services have privileged access to stored information to perform application operations. This technical access is separate from access by ClearOps Labs personnel.
When the corresponding product services are configured and used, Clerk handles authentication and organization membership, and Supabase handles product records and receipt files. When the website is hosted on Vercel, Vercel handles website hosting. If receipt scanning is available and you choose to scan a receipt, OpenAI processes the selected image. If workflow email delivery is enabled and a notification is sent, Resend receives the recipient email address and message content, which can include a request number, title, amount, workflow event, and link to the request.
When the corresponding product operations run, diagnostic logging can include processing identifiers, error categories, and hashed account or organization identifiers.
Record removal and privacy requests
Requesters can remove or replace receipts while editing their own draft or returned requests. Receipt removal includes file cleanup, and unsuccessful cleanup can remain pending for retry. Removing a receipt does not erase the associated request, approval history, payment records, or all processing records. Deactivating a department preserves its existing references.
For questions about retention, access, correction, account closure, or deletion of other records, contact ClearOps Labs. For school reimbursement records, also contact your school administrator. State the school and the type of request without sending passwords or unnecessary receipt details. A privacy inquiry does not itself automatically delete product records.
Contact ClearOps Labs
Send privacy questions to support@clearopslabs.com.
Changes to this policy
We may update this policy. The effective date and version above identify the current version. We will post an updated policy before it takes effect.