who is responsible
Retriever is inventory software for robotics teams, operated by Rishaan Jain, an individual operator located in California, United States. Privacy questions and requests: rishaanjain188@gmail.com.
This policy describes the service as currently implemented. It has not been reviewed by a lawyer, and it should be before the service takes payments from the public.
information the service handles
Account information includes your email address, display name, password, and account identifiers. Accounts are created with an email address and a password; there is no third-party sign-in. Supabase manages authentication and stores your password in hashed form.
Workspace information includes team names, memberships, invitations, inventory, storage locations, requests, notes, and shipment details you enter. Other authorized members of your workspace may see shared workspace information.
Stripe processes payments. Retriever stores Stripe customer and subscription identifiers, plan, subscription status, and billing period information. Payment card entry happens on Stripe-hosted pages; Retriever does not store full card numbers or security codes.
Optional integrations receive information needed for features you enable. Linked Discord identifiers and channel settings may be stored, and inventory or request information may be sent to configured channels. Do not enter sensitive personal information into inventory notes.
how information is used
Information is used to authenticate accounts, provide shared inventory features, manage permissions and subscriptions, send transactional messages, investigate failures and abuse, and respond to support requests. Hosting and service providers may process technical logs, such as IP addresses, request information, and error details, to operate and secure their services.
service providers and sharing
The current implementation uses Supabase for authentication and database services, Stripe for billing, and Resend for transactional email delivery. Discord is an optional integration. Their own privacy notices describe processing on their services. The hosting provider and processing locations must be confirmed before launch.
Information may also need to be disclosed to comply with applicable law, protect users and the service, or complete a business transfer with appropriate notice and safeguards. The operator must confirm whether any additional sharing, sale, advertising, or marketing practices apply.
cookies and analytics
Authentication uses cookies to maintain your session. Browser storage saves your theme and analytics preferences. Optional PostHog analytics counts visits to public pages only after you choose “Allow analytics.” You can decline or withdraw permission using “Analytics preferences” on public pages.
Analytics sends the public page path and a randomly generated identifier held in memory. It excludes query strings, invitation and authentication links, account identifiers, and private workspace content. Session recording, autocapture, and person profiles are disabled. PostHog’s US service receives requests and may process connection information such as IP addresses; events request no geolocation enrichment. Analytics retention and the final legal basis must be confirmed before launch.
retention, security, and your choices
Canceling a subscription does not immediately delete anything. A workspace becomes eligible for deletion 14 days after paid access ends. Account and workspace records may be kept until then, and financial records may need to be kept longer where law requires it.
You may have rights to request access, correction, deletion, restriction, objection, or a copy of your personal information, depending on where you live. California residents have rights under the CCPA, including access and deletion. Write to rishaanjain188@gmail.com to make a request. Shared workspace records may be handled differently from personal account data, because deleting one member’s entry would alter records belonging to their team.
Authentication, access controls, and provider safeguards help protect information, but no service can guarantee absolute security. International processing arrangements and any required transfer safeguards still need confirmation.
children under 13
Retriever is not directed to children under 13, and accounts for children under 13 are not permitted. Creating an account requires confirming that you are 13 years of age or older. The service does not knowingly collect personal information from a child under 13.
If we learn that an account belongs to a child under 13, the account and its personal information are deleted. A parent or guardian who believes a child under 13 has created an account may write to rishaanjain188@gmail.com and the account will be removed.
Robotics teams often include minors aged 13 to 17. A school, team, or parent remains responsible for deciding whether a minor should use the service and for any authorization their own rules require. Inventory records are shared with other members of a workspace, so members should not enter personal information about themselves or anyone else into inventory fields.
updates and contact
Material changes are communicated with an updated effective date and, where required, notice before they take effect. Privacy contact: rishaanjain188@gmail.com.