Privacy Policy

RareDex is a place to quietly preserve not only plants, but the time people spend with them. This Policy explains how we care for members’ records and personal information.

1. Information we collect

  • User ID, email address, display name, profile image, and other information needed to authenticate through Google, Apple, or email
  • Optional profile information, including a bio, public ID, and Instagram or X username
  • Submitted content, including plant names, classifications and varieties, photos, arrival dates and locations, Google Maps share links, growing conditions, status, journal entries, comments, and GG reactions
  • Service-use information, including blocks, reports, notification read status, email and push settings, SelectDex activity, and display preferences
  • Information needed for Plant Handoffs, including requests, selections, payment status, shipping method and tracking information, delivery confirmation, and Stripe Connect status
  • Support requests, response history, and information needed to verify identity
  • Technical information needed to operate the service safely, such as access time, browser and device information, and error logs

2. How we use information

  • To register and sign members in, verify identity, and manage accounts
  • To provide MyDex, plant journals, photo display, comments, GG reactions, notifications, blocking, and related features
  • To investigate problems, improve quality, operate the service safely, and respond to abuse
  • To respond to member inquiries
  • To securely handle payment, shipping, delivery confirmation, ownership changes, and refunds for Plant Handoffs
  • To send email or push notifications selected by the member
  • To take action required by law or the Terms of Use

3. Information that may be public

Plants, photos, journal entries, display names, profile images, comments, GG reactions, and other information submitted as public may be visible to other members and anyone on the internet. Do not post information you do not want made public or information that can identify a person.

4. Third-party services

RareDex uses third-party services including Google (authentication, email, analytics, and Maps links), Apple (authentication), Supabase (authentication, database, and image storage), Vercel (hosting and server processing), and Stripe (payments, identity verification, and payouts to owners). Notification email is sent through Gmail SMTP and may also use an email delivery provider such as Resend, depending on configuration. Each provider handles information under its own terms and privacy policy.

For Plant Handoffs, payment and shipping information is collected through Stripe’s standard fields. Stripe handles card numbers, bank accounts, and identity-verification documents. RareDex does not store that information in its database.

RareDex’s server temporarily retrieves from Stripe only the name, address, and phone number needed for shipping and displays them to the owner who will ship the item. RareDex does not store those details in its database, a URL, browser storage, or Stripe metadata. The RareDex database stores only an audit record identifying who viewed the details, when, and for what purpose. The owner may not use, retain, or share the information for any purpose other than shipping and communication necessary for the handoff.

5. Sharing with third parties

RareDex does not provide personal information to third parties except when required by law, with the member’s consent, or to a service provider to the extent needed to operate RareDex.

6. Information security

RareDex uses safeguards designed to prevent unauthorized access, disclosure, loss, or alteration of information. These include limiting access to what is necessary, authentication and permission controls, encryption in transit, review of activity and error logs, vendor selection and oversight, and incident-response procedures. No internet service can guarantee absolute security.

Upon a verified request, RareDex will provide information about its safeguards without unreasonable delay, to the extent doing so does not compromise security.

If a personal-data incident requires a report to an authority or notice to affected people under applicable law, RareDex will make the required report or notice and take reasonable steps to contain the incident.

7. Deletion, correction, and suspension of use

You may be able to delete your own journal entries and comments using features in the service. To delete your account, sign in and begin the “Leave RareDex” process in Settings.

If a handoff, payment, shipment, refund, or safety review is in progress, account deletion may be delayed until that process can be completed safely. Transaction history needed for legal compliance, fraud prevention, or dispute handling may be retained for the required period in a form that does not directly display the individual.

To request notice of the purposes for which retained personal data is used, access, correction, addition, deletion, suspension of use, erasure, or suspension of disclosure to third parties, contact the contact form. Include your registered email address, display name or public ID, and the action you are requesting. After verifying your identity, RareDex will respond without unreasonable delay as required by law. There is no fee for submitting a request.

10. Use by minors

If you are a minor, use RareDex only with the consent of a parent or legal guardian.

11. Personal-information handling business operator and request contact

The business operator responsible for handling personal information is Tomonori Kasuya (service name: RareDex). The operator’s address will be disclosed without unreasonable delay upon a verified request, as described in the Commercial Disclosures.

Questions and requests concerning this Policy, retained personal data, or security safeguards may be submitted through the contact formorraredex.jp@gmail.com.

12. Changes to this Policy

RareDex may revise this Policy as needed. Material changes will be announced through the service or another appropriate method.

Effective June 20, 2026 · Last updated August 31, 2026