Information collected
Credit Reaper may process account/profile information, company and entity records, credit-line data, transactions, notes, and activity history entered into the product.
Legal review
Privacy Policy
Early access privacy language describing the kinds of data Credit Reaper may process and how future choices should be documented.
Legal
Early access review content.
This copy is intentionally careful and should be reviewed by legal counsel before broad commercial launch.
Account/profile information
Account profile handling may include user names, email addresses, roles, company context, and entity access assignments.
Alpha registration and submitted information
Real individual and business registration information is permitted, including email addresses, company names and business contact details. Financial transactions, balances, agreements and supporting documents should be fictional test information during alpha. This instruction is not a technical filter: Credit Reaper may receive and store information users submit contrary to it. Alpha records are not automatically deleted merely because they are test records.
Authentication and invitations
Clerk provides account authentication, including Google Sign-In when selected. Account information can include your verified email, profile information and authentication identifier. Invitations use the recipient email and requested organization role and entity scope. Registration alone does not grant access to another organization. Organization administrators manage access within their authorized scope; platform administration is separately authorized.
Company/entity/credit data
The product stores business entities, credit lines, balances, statuses, lifecycle fields, and transaction records through the backend API.
Notes/activity/audit data
Internal/shared notes and audit history may contain business context supplied by users.
Documents, notifications and technical records
The application can store uploaded documents, document metadata and versions, membership and invitation records, and operational notifications. Technical logs and security monitoring support troubleshooting and incident response. In-app notification records do not guarantee that an invitation or other email has been delivered. Access to records depends on the applicable organization, entity and sharing permissions.
Cookies/local storage
Credit Reaper may use essential browser storage for product operation and account context. Analytics and marketing cookie programs should be documented before use.
How data is used
Data is used to operate the product, display allowed records, support reports, troubleshoot issues, and improve Credit Reaper.
Sharing and processors
The current service uses Vercel for frontend hosting, AWS for backend services, database and document storage, and operational monitoring, and Clerk for authentication. Google processes Google Sign-In when you choose that method. These providers process information relevant to their services. The complete provider inventory and applicable sharing terms remain subject to review.
Data retention
Retention, export, deletion, and archival rules should be finalized before broad commercial launch.
User choices
Cookie preferences, account settings, data export, and deletion workflows are planned for later product/legal work.
Contact
Use the contact page for privacy questions while the policy is under review.
Next step
Questions about this page?
Use the contact page while final legal, privacy, and compliance materials are prepared.