RubyCollect Privacy Policy
Effective October 13, 2026. RubyCollect operates a trading-card collection and marketplace service at rubycollect.ca. Privacy Officer: Kyle Lortie, owner of RubyCollect. Privacy inquiries, access or correction requests, and complaints may be sent to kyle@rubycollect.ca or by mail to RubyCollect, Attn: Privacy Officer, 120 Carbine Rd, Pakenham, ON K0A 2X0, Canada.
1. Information collected
Depending on features used, we process account names, usernames, email addresses, password authentication data, login and security records, seller identity and payout onboarding status, shipping and billing addresses, transaction details, subscription status, card photos and descriptions, collection contents, proof and transfer videos, timestamps and file hashes, messages, inquiries, reports, disputes, moderation reasons and support communications. We may collect device, browser, IP address and security-event information to operate and protect the service. Stripe processes payment-card information; RubyCollect does not intentionally store complete payment-card numbers.
2. Why we use information
We use information to create and authenticate accounts; provide collections, browsing, listings, communications, subscriptions and payments; facilitate shipping and delivery; investigate fraud and disputes; enforce marketplace rules; respond to support and privacy requests; maintain required records; and meet legal obligations. We use optional marketing communications only where permitted and subject to applicable consent and unsubscribe requirements.
3. Public versus private collections
Your collection is private by default. If you enable public visibility, the card information included in your public collection and your displayed profile identity may be seen by other users and shared through its public link. Purchase prices, private notes and non-public account details are not intended to be included in the public collection response. Public visibility may permit other signed-in users to send questions or non-binding offers. You can turn public visibility off; this does not necessarily remove copies previously saved by others.
4. Sharing with other parties
We share only information reasonably necessary with transaction counterparties, payment and payout providers including Stripe, shipping and label providers when enabled, infrastructure and hosting providers including Floot, email-delivery services, fraud and identity-verification vendors, and professional advisers or authorities where legally required. Buyers and sellers may see transaction details necessary to fulfill orders or resolve disputes. We do not sell personal information to advertisers. Vendor processing and data storage may occur outside your province or Canada, subject to applicable legal requirements and safeguards.
5. Security and evidence
We use account controls, access restrictions and technical safeguards designed to reduce unauthorized access. No system can promise absolute security. Required listing proof, trade videos, hashes, timestamps and dispute evidence may be retained for verification, safety, audit and legal purposes, even after a listing is removed. Access should be limited to authorized reviewers and relevant transaction participants.
6. Retention and account removal
We retain personal information while needed for account services and for legitimate operational, tax, payment, fraud, dispute and legal requirements. When an account is removed, access is revoked and its active member profile may be de-identified; historical order and moderation records may remain in restricted systems as necessary. We aim to delete or de-identify information when the reason for retaining it ends. We do not currently promise a universal fixed deletion period for every record category.
7. Your choices and rights
You may update account information, keep collections private, control public sharing, request access or correction, withdraw consent where legally available, and request account deletion or review of retained information by contacting our privacy address. Some information cannot immediately be deleted where retention is required or justified by law, disputes, fraud prevention or payment records. Quebec residents may have additional rights under Quebec privacy law, including applicable rights concerning portability and automated decisions.
8. Cookies, local storage and communications
RubyCollect uses session and authentication technologies and browser storage for features such as region, display currency and preferences. Additional analytics or marketing technologies, if introduced, must be disclosed and managed according to applicable consent rules. Transactional emails may include verification, purchase, dispute and security notices. Promotional emails require the consent or other legal basis applicable to that message and an available unsubscribe mechanism.
9. Children, international transfers and incidents
RubyCollect is restricted to users aged 18 or older. We check submitted dates of birth for eligibility but do not store the dates from our age-confirmation forms; we retain only confirmation status and date. We may use a limited browser-session confirmation for visitors. If you believe a minor has accessed RubyCollect or submitted information, contact us. We assess cross-border disclosures and service-provider safeguards as required by law. We investigate suspected privacy incidents and provide notices or reports where required.
10. Contact and policy changes
For privacy questions, access or correction requests, withdrawal of consent or complaints, contact support@rubycollect.ca and include “Privacy Officer” in the subject. We may ask for appropriate verification before disclosing account information. We will update this policy as our features and vendors change and give additional notice where required.
Vendor inventories, exact retention schedules, cross-border assessments and consent flows must be verified against the production deployment before unrestricted commercial launch.