Privacy Policy

GitCard is designed to help developers publish professional portfolio information. Depending on your settings and actions, public information may include your profile, avatar, cover image, selected repositories or projects, GitHub or GitLab metrics, resume sections, card preview content, public analysis pages, and contact or social links.

Dynamic QR redirect URLs are public by design because printed and shared QR codes need to resolve without sign-in, but destination editing and scan analytics are owner-controlled.

You can manage certain privacy settings in GitCard settings, including profile visibility, email visibility, resume visibility, GitHub metrics visibility, GitLab metrics visibility, and recruiter view preferences. Turning a setting off may hide information from future public views, but cached, indexed, exported, shared, printed, or third-party-copied content may persist outside GitCard's control.

If you use AI resume features, GitCard may process imported resume files, extracted resume text, resume drafts, prompts, model outputs, usage metadata, and estimated provider costs. AI features are available only when the required account entitlement and monthly AI credit checks pass.

GitCard may send relevant resume text, prompts, and context to configured AI providers such as OpenAI or Groq to provide extraction, analysis, scoring support, and section-improvement suggestions. Do not submit sensitive information to AI tools unless you want it processed for that feature.

GitCard uses cookies, local storage, and similar technologies for authentication, session management, security, theme preferences, navigation, and application functionality. We may also use hosting, monitoring, or analytics tools if enabled to understand reliability and usage.

Your browser may let you block or delete cookies, but some GitCard features may not work correctly without session and security cookies.

GitCard does not intend to store full payment card numbers. Payment methods, card details, invoices, and hosted billing management are handled by Stripe. GitCard stores payment and subscription metadata needed to identify your Stripe customer record, subscription status, plan entitlement, current period dates, cancellation status, and payment or checkout events.

If you buy printed cards, GitCard stores order and fulfillment metadata needed to validate payment, submit production orders, support customer service, and maintain required business records.

We retain information for as long as needed to provide GitCard, maintain accounts, support public profile and resume features, complete orders, maintain subscriptions, comply with legal and tax obligations, resolve disputes, enforce agreements, prevent abuse, and operate backups and security systems.

You may delete certain content or request account deletion, but some records may be retained where required for payment, order, security, legal, accounting, fraud-prevention, backup, or compliance purposes. Public content shared outside GitCard may not be removable by GitCard.

GitCard uses technical and organizational safeguards intended to protect information, including access controls, server-side secrets, private storage for certain uploads, owner-scoped data access, webhook verification, and secure payment processing through Stripe.

No online service can guarantee perfect security. You are responsible for using strong passwords, protecting your login credentials, and keeping connected provider accounts secure.

Depending on where you live, you may have rights to request access, correction, deletion, portability, restriction, objection, or information about certain disclosures. You may also have the right to opt out of certain processing if applicable law requires it.

California residents may have rights under the California Consumer Privacy Act, as amended by the California Privacy Rights Act, if those laws apply to Gitcard. These rights may include the right to know what personal information is collected, used, disclosed, sold, or shared; the right to access or receive a copy of personal information; the right to delete personal information; the right to correct inaccurate personal information; the right to opt out of sale or sharing; the right to limit certain uses of sensitive personal information; and the right not to be discriminated against for exercising privacy rights.

Gitcard does not sell personal information for money. If we later engage in activity that is considered a sale or sharing of personal information under California law, we will provide any required notice and opt-out mechanism.

You may make a privacy request, or designate an authorized agent to make a California privacy request where permitted by law, by contacting [privacy email]. We may need to verify your identity and account ownership before fulfilling a request. Some requests may be limited by legal, security, payment, anti-fraud, public-interest, or technical reasons.

GitCard is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided personal information to GitCard, contact [privacy email].

GitCard is operated for a US-first audience. If you use GitCard from outside the United States, your information may be processed in the United States and other countries where GitCard or its service providers operate. Those countries may have data-protection laws different from those in your location.

We may update this Privacy Policy from time to time. The updated version will be posted on this page with a new last-updated date. If changes are material, we will provide notice as required by law or through the service.

Privacy requests and questions may be sent to [privacy email]. General support questions may be sent to [support email].