Privacy Policy

1. Your collection is private

Foilport provides private digital binders and optional photo-based card checks. Your collection, photos, notes, purchase information, and assessments are not published on public catalog pages. Public catalog records are separate. We do not offer public binder sharing, sell personal information, or use your private photos to train our own models.

Necessary service providers process data to deliver the features you choose. A requested live photo check sends necessary card images and identity context to our AI image-analysis providers for identification, photo-quality checks and condition estimates. Provider processing can take place outside Canada. Do not upload unnecessary sensitive information or other people’s personal details.

2. Information we collect

The information depends on how you use Foilport:

• Account information: sign-in user identifier, email address, verification status, and any display name provided through sign-in; account creation/update times, owner approval or rejection status, and security/access records. Our authentication provider handles sign-in credentials; your password is not stored in Foilport’s collection database.
• Collection information you enter: card identity, language, set, number, printing, condition, slab details, quantities represented by physical-card records, binder names and memberships, tags, private notes, purchase amounts and dates, and selected display photos.
• Photos and checks: uploaded card images, image dimensions/type/size and content hash, photo role, submission times, assessment input snapshots, identity results, estimated grades, diagnostics, observations, limitations, retake instructions, processing state, and provider/job records needed to perform and track the check.
• Technical and security information: requests needed to serve the site, sign-in/session information, rate-limit identifiers, and operational records used to prevent abuse, authorize access, investigate errors, and manage provider usage. Hosting, authentication, and email systems may process network addresses and other technical information under their own operational lifecycles.
• Website activity: the limited first-party analytics described below, including normalized page routes, device category, referring domain, selected campaign labels, and approximate network-derived location when available.
• Correspondence: your email address, message, attachments you choose to send, and our replies when you contact hello@foilport.app. Avoid emailing passwords, unnecessary identification documents, or payment information.

3. How and why we use information

We use account and technical information to authenticate you, verify email, administer beta approval, maintain sessions, enforce ownership/access controls, respond to account requests, and protect the service. Registration alone does not authorize access to card tools.

We use your collection entries and photos to store and display your private binders, carry out requested identification or condition checks, preserve assessment evidence, and match supported exact-variant market references. Private notes, account emails, and unrelated photos are not included in card-analysis requests.

We use limited activity, job, and provider records to understand service usage, measure aggregate price coverage and processing outcomes, diagnose failures, administer capacity and spending limits, and improve the service. We use correspondence to answer questions and handle privacy, support, or legal requests.

We send necessary account and service messages, such as verification, password reset, and access-status communications, where configured. The beta does not enrol you in advertising or a marketing mailing list. We do not use private collection data for targeted advertising.

4. Service providers and other disclosures

We use the following categories of service providers for the purposes described here. Their role depends on the feature and whether live processing is enabled. Each processes information only as needed to provide its service to us:

• Authentication: Google/email sign-in, identity and email-verification management, sign-in credentials and related security processing. Choosing Continue with Google also involves Google’s account services.
• Cloud hosting: application hosting and processing, the private database, private image storage, backups, security and operational infrastructure. Authorized personnel can access information only as needed for service administration, support, security, or legal obligations.
• AI image analysis: necessary card photos and card identity context for requested live identification, photo-quality checks and condition estimates. Where available, Foilport asks providers not to store generated responses for reuse; this does not mean zero provider retention. Abuse-monitoring or safety records, image-safety review exceptions, and applicable legal obligations may still require retention under the service arrangement. Results return to your private account.
• Providers may retain information for processing, safety, security, or legal purposes under the applicable service arrangement; Foilport’s expiry schedule is not a promise of immediate deletion from all provider systems.
• Market data: catalog and exact-variant market references. Requests use catalog/variant identifiers and filters, not your private photos, notes, purchase records, or account email.
• Email delivery: transactional email, including recipient email, message contents or action links, and delivery/status information needed for the message.
• Email inbox: receiving, forwarding, storing, and responding to messages sent to hello@foilport.app. Contacting that address sends your correspondence through those systems. The reply mailbox is not listed as the website contact address, but email recipients may see it in message headers.

5. Legal and organizational disclosures

We may disclose information when required or permitted by applicable law, such as responding to a valid legal demand, protecting a person’s safety, investigating unlawful activity or misuse, or establishing or defending legal rights. We limit such disclosure to what is appropriate in the circumstances.

If a merger, acquisition, financing, reorganization, or transfer of the service is proposed, information may be handled where legally permitted and subject to safeguards and restrictions on its use. We will provide notice and obtain consent where required. We do not treat this possibility as permission for unrelated use of your private collection.

6. Processing outside Canada

Foilport and its providers may store or process information in Canada, the United States, or other countries where the relevant provider operates. We do not promise that every copy remains in Canada. Foreign laws may permit courts, law-enforcement agencies, or national-security authorities to access information in those jurisdictions.

We remain responsible for personal information under our control and use appropriate contractual and other safeguards for service-provider processing. You may contact us for information about our providers and cross-border practices. Choosing not to use a feature that needs a provider avoids that feature’s new submissions, but does not erase processing that has already occurred.

7. Limited website analytics

Our first-party traffic analytics do not set an analytics cookie. They record allowlisted page categories, such as a card-detail route template instead of the card’s private identifier; device category; a referring domain without its full path; and only allowlisted source, medium, and campaign labels. Arbitrary query strings, binder names, private notes, photos, account emails, and full browser strings are not stored in analytics rows.

When a trusted network address is available, it is used transiently with browser information and a daily-changing hash to approximate daily unique visitors, and for a local coarse location lookup. Analytics rows store the daily hash rather than the raw address. Approximate country, region, city, and coarsely rounded coordinates may be recorded; this is network-derived, can be inaccurate, and does not use your device’s precise-location permission. Missing location or visitor coverage stays unknown. A returning person on a different day can count again.

We exclude recognized owner traffic, detected bots, and test traffic, although detection is imperfect. The tracker and endpoint honour a Do Not Track value of 1 where your browser supplies it. Analytics events are scheduled for removal after 90 days. This describes the application analytics dataset, not a guarantee that hosting or authentication providers never process a network address.

Foilport’s sole authorized owner can view necessary registration information, including account name/email, verification and access status, registration and account-update dates, and private per-account collection summaries. These summaries include named binders, physical-card counts, available cached USD market references, and missing/stale-price coverage. Overall counts and values do not duplicate a physical card placed in several binders. These operational reports do not offer photo, private-note, purchase-detail, or card-identity browsing, and are separate from the approximate visitor measure. We do not publish per-collector activity or private collection details in public reports.

8. Authentication cookies and browser storage

Foilport uses a session cookie to keep you signed in and protect authenticated requests. Our authentication provider and Google sign-in may use browser storage and their own cookies or similar technologies to complete sign-in and maintain authentication state. These functions are distinct from our cookie-free traffic analytics.

You can clear or block cookies and browser storage through your browser. Doing so may sign you out or prevent account features from working. Signing out ends the Foilport session; it does not delete your collection or necessarily sign you out of Google on other sites.

9. Photos, evidence, and retention

Uploads are validated and re-encoded as resized JPEGs without preserving embedded image metadata such as EXIF location. This does not remove information visibly printed or photographed in the image. The original upload file is not maintained as a separate permanent original in the collection storage.

Unsaved standalone assessments are set to expire 72 hours after creation. Unreferenced uploads, including abandoned uploads, are set to expire 72 hours after upload. A replaced display-only photo that is no longer referenced is given a 72-hour expiry window after replacement. Cleanup removes eligible records and queues image-object deletion. Active processing and retained evidence references can delay eligibility.

When you save a card or keep an assessment attached to a physical-card record, its referenced photos and assessment evidence are retained for that record’s lifetime, until deletion. Replacing the card’s display photo does not remove a photo still used as assessment evidence, and does not alter or rerun the assessment. A binder or membership deletion does not delete the physical-card record.

Analytics events are scheduled for deletion after 90 days. Other account, support, security, audit, delivery, and provider-usage records are retained as needed for the relevant purpose, legal requirements, dispute handling, and service protection. Completed image-deletion receipts are retained for 30 days. We do not promise one fixed retention period for every provider or operational record.

Deletion of image bytes and external authentication records runs asynchronously, with retries if a provider is unavailable. Backups, recovery copies, caches, and provider records can outlast removal from the active application and expire under their applicable lifecycles; deletion is not instantaneous erasure from every system. We do not use retained recovery copies to restore a deleted account for ordinary use.

10. Your controls, access, and deletion requests

You can view your account/access status, edit collection entries, replace display photos, delete individual physical cards, and delete your account using the available account and card controls. Removing a card from a binder or deleting a binder leaves the physical card in All cards. Deleting a physical card removes its assessments and memberships and releases photos that are no longer referenced.

Account deletion disables access, removes collection records and associated assessment/photo records, and initiates deletion of the sign-in identity and stored image bytes. The active account email and display name are removed. Limited account/UID, access-revocation, and audit records remain to prevent unauthorized recreation, preserve ownership/access history, and support security and legal obligations. Revocation of beta access alone does not perform account deletion.

You may ask us to explain our handling of your information, provide access to information under our control, correct inaccuracies, withdraw consent, or address a privacy concern by emailing hello@foilport.app. We may verify your identity using information reasonably necessary for the request and may explain any lawful limit or exception. We will respond within applicable legal time limits; no automatic export feature is promised.

You can choose not to upload photos or request AI checks. Withdrawing consent to processing necessary for a feature may prevent us from providing that feature or maintaining the account. Withdrawal applies going forward and is subject to applicable legal or contractual restrictions and reasonable notice. It does not waive your rights or automatically erase records that must lawfully be retained.

If we cannot resolve your concern, you may contact the Office of the Privacy Commissioner of Canada or the relevant provincial or other privacy regulator. You do not have to give up that right to use Foilport.

11. Security and privacy risks

We use access and ownership checks, verified sign-in, private image delivery, restricted service credentials, and other technical and organizational measures appropriate to the information. Private does not mean that authorized service administration or necessary provider processing never occurs. No internet service, email system, or storage technology can guarantee absolute security or recovery.

Possible risks include unauthorized access, disclosure, loss, and inaccurate automated results. Photos and notes can reveal more than you intend. Use a secure account, avoid unnecessary sensitive content, and contact us promptly about suspected misuse. We assess privacy incidents and provide notifications where applicable law requires them.

12. Consent and young users

We explain necessary processing through this policy and relevant feature notices. We seek consent where required and rely on lawful exceptions only where they apply. Accepting terms is not blanket consent to unrelated purposes. If we introduce a materially different use or disclosure, we will explain it and obtain additional consent where required.

Foilport is intended for people able to understand and validly agree to its terms and privacy practices. Where a young person cannot provide meaningful consent or applicable law requires it, a parent or guardian must authorize the relevant use. We do not require a date of birth as part of the current sign-up form. Contact us if you believe a child’s information has been provided without appropriate authorization so we can review and address it.

13. Policy updates and contact

We may update this policy to reflect service or legal changes and will display its effective date. We will bring material changes to your attention and seek consent for new uses or disclosures where required. A revised policy does not itself authorize an unrelated use of information already collected.

For privacy requests, complaints, or questions about Foilport, contact 15507120 Canada Inc.’s privacy contact at hello@foilport.app. If you need the identity or mailing details of the person responsible for our privacy practices, request them through that address.