Privacy Policy

Last updated: October 31, 2026

1. What we collect

When you subscribe, we collect your name, email, and the business details you provide during intake. Payment card details are collected and stored by our payment processor, not by us.

Booking a time on /call loads Calendly's scheduler in your browser. Calendly receives the name, email and time you enter there. We do not keep a copy of that booking.

If you are a person on a customer's business card and you sign in to edit your own card with Google, Microsoft or Apple, we read only the following, and only to pre-fill your own card editor:

  • Google — the link to your Google profile picture.
  • Microsoft — only when we have switched this on: the mobile and business phone numbers held on your Microsoft account, if any.
  • Apple — nothing beyond your name and email address.

These appear as suggestions on your own editing page. Nothing is added to your card unless you press Save. When you sign in to the web card editor we may store your Google profile photo link and, if we have switched it on, your Microsoft work and mobile phone numbers as these pre-fill hints. Your next sign-in replaces them, and we keep them for 90 days at most. We keep them only while you are on the card, and we delete any older than 90 days. That clean-up runs when someone signs in to edit a card, so deletion, including when the business takes you off the card, is not instant.

When we have switched this on, signing in to your RavenPower account with Google also keeps the link to your Google profile picture, so that Use my sign-in details or Use my Google sign-in photo can put that photo on your own card. We keep the link only, not the picture, and apart from your account record. Each Google sign-in replaces it, or removes it if Google sends none. We fetch the picture from Google only when you press one of those buttons, and only from Google's profile-photo servers. It is then stored with your card like a photo you upload, and appears wherever your card photo appears, until you change it. Our hourly clean-up deletes the link 90 days after the Google sign-in that stored it, or once Google is no longer a way you sign in, and it is deleted with your account. Signing in with Microsoft or Apple gives us no photo.

If you choose Connect LinkedIn on your card, we ask LinkedIn for your name, your profile photo and, if LinkedIn has verified it, your email address. LinkedIn does not give us your job title or company. We show you what LinkedIn sent before anything on your card changes, and hold it for up to 30 minutes while you decide. Only what you pick with Use selected goes on your card. Anything you don't use is deleted: at once when you choose Use selected or Discard, and otherwise by our daily clean-up after the 30 minutes. What you use appears on your public card, in the contact file people download from it, and on your Wallet pass, and your name and photo can appear in the preview shown when your card link is shared. We don't use it for anything else, and we don't keep your LinkedIn login. Your name and email then stay on your card like anything else you type there, until you change them. The LinkedIn photo is deleted when you remove it, upload a different photo, delete your account, or 12 months after you last connected.

When we have switched them on, Scan a business card and Start from text in the card builder send what you give them to Anthropic, whose Claude model reads it and suggests your card's fields: the photo of the card, or the text you paste. A business card can carry another person's name and contact details. We send it only when you press the button, and you check every suggestion; nothing goes on your card unless you press Save. We do not keep the photo or the text: neither is saved to our database or file storage, and our logs record only which account asked, when, the result, and a one-way fingerprint of what was sent, from which it cannot be rebuilt. Anthropic handles what we send under its commercial terms, and its own retention rules apply to it.

Security and abuse prevention. When you use our site, forms or sign-in, our hosting provider (Cloudflare) receives your IP address as part of delivering the request. To stop spam, abuse and repeated sign-in attempts, we count requests using a keyed, one-way hash of your IP address network, or of the email, phone number or account involved. We do not store your IP address itself in these records. We delete each record automatically 2 days after its counting window starts (most windows are an hour or less, and the longest is one day). We keep separate security event records for sign-ins and account changes for 400 days; where those include a network identifier, it is also a keyed hash. We use this information only to keep the service secure, on the basis of our legitimate interest in protecting the service and its users.

When our staff change something in our admin tools, we keep a record that names the staff account, the action, what it was done to, the time, and, for some actions, the old and new value or status of what changed. We keep these records for as long as we need them to show who changed what, for security and accountability.

1a. Sharing your details from a RavenPass card (RavenPass Connect)

If you scan or open someone's RavenPass card and use RavenPass Connect — the "Connect with …" form on their card — what you type in that form is sent to the owner of that card. We act for the card owner here: they decide what to do with your details, and we store them on their behalf. Separately, and for our own purposes, we run spam and bot checks on this form, including Cloudflare Turnstile when it is triggered. We do this on the basis of our legitimate interest in keeping the service safe. We do not store your IP address; rate-limit records hold only a keyed hash and are deleted after 2 days. We do not store the Turnstile challenge token. To access or correct your details, contact the card owner, or write to us at [email protected] and we will pass the request on.

Nothing is filled in or sent unless you do it. We do not pre-fill that form from cookies, from your IP address, or from any third-party data source — only from your own browser's autofill, your phone's contact picker, your own RavenPass card if you are signed in, or your Google, Microsoft or Apple account if you tap "Share with" and sign in there. That last one reads only your name and email address, creates no RavenPower account and no sign-in for you, keeps nothing from the provider beyond those two values, and discards them two minutes later if you do not send the form. Opening a card or sending the form sets no cookie and uses no analytics or tracking: we load no analytics on /c/* and /card-exchange/* and /card/new/* and /card/new and /f/* and /s/* (see section 4). If you choose "Share with" and sign in with Google, Microsoft or Apple, we set short-lived, strictly necessary cookies to complete that sign-in securely; they are not used for tracking. If our spam check (Cloudflare Turnstile) is triggered, it runs in your browser only to tell people from bots.

How long we keep it. The card owner chooses the period, between 1 and 24 months (12 by default). The form names the number before you send, we count it from the moment you ticked the consent box, and then we delete it. If the owner shortens the period later, your details are re-dated to the shorter one; if they lengthen it, nothing already stored is kept any longer, because you did not agree to the longer period.

You can have it deleted sooner, and you do not have to ask us. If you gave an email address, request a deletion link — or use the one-time link in the confirmation email we sent you — and pressing the button on it removes every set of details we hold for that address, from every card. If you gave only a phone number there is no link we can email you, so ask us to delete your details and a person will check and action it within 30 days.

What deletion cannot reach, stated plainly. Two copies survive a deletion and we would rather say so than imply otherwise. First, the notification email already delivered to the card owner is in their mailbox and outside our control. Second, our database provider (Cloudflare D1) keeps a point-in-time restore window — "Time Travel" — of up to 30 days, so a deleted row can persist in that restore window until it ages out. We do not read from it except to recover from a failure.

We never use what you shared for our own marketing, for building audiences, for enriching it against other data, or for training models.

2. How we use it

We use your information to build and operate your website, to bill your subscription, and to contact you about your service, and to keep the service secure and prevent spam and abuse. We do not sell your personal information for money. If you allow advertising cookies, some information about your visit is shared with advertising partners such as Google to measure and show ads, which some U.S. state laws treat as a "sale" or "sharing". See Your privacy choices to opt out.

Legal bases (EEA/UK visitors). We use your account, subscription and card details to perform our contract with you; billing records because tax law requires it; security data on our legitimate interest in protecting the service; and analytics and advertising cookies only with your consent. We keep account and card details while your account is active and delete them as described in section 4b. Our providers process data in the United States; where the law requires, transfers rely on the EU-U.S. Data Privacy Framework or Standard Contractual Clauses.

We send account, security and billing emails as part of the service. We send product news or offers only if you opt in, each includes an unsubscribe link, and we stop within 10 business days of your request.

If you join our waitlist, we keep your email address, business type, the time you agreed, and a keyed hash of your IP address (for abuse prevention) so we can invite you. We delete them when you ask, 12 months after sign-up if you're never invited, 90 days after an invite expires if you don't join, or 30 days after you create an account. If you ask to be removed, we keep only a keyed hash of your email so we don't add you again.

If someone invites you to their organization, we use your email only to send that invitation; you can ask us not to send further invites.

3. Processors we rely on

We share data only with the service providers needed to deliver the service:

  • Stripe — Payment processing & subscription billing
  • Cloudflare — Hosting, CDN, security, and form handling
  • Email delivery: Cloudflare, Inc. (Cloudflare Email Service) sends our transactional emails, including RavenPass Connect messages. Resend, Inc. may be used as a backup delivery service if Cloudflare is unavailable. Each receives only the recipient's email address and the message content needed to deliver it.
  • Google — Website analytics (Google Analytics via Google Tag Manager), and sign-in if you choose Google
  • Microsoft — Sign-in, if you choose a Microsoft account
  • Apple — Sign-in, if you choose Sign in with Apple
  • GitHub — Source-code hosting and deployment tooling for our platform
  • Cloudflare Email Service — Free-card account, security, and inactivity emails
  • Resend, Inc. — Backup delivery of free-card emails
  • Anthropic — Reading a business-card photo or pasted text to suggest your card fields, when you use Scan a business card or Start from text
  • Calendly — Scheduling the intro call on /call. Calendly receives what you type in that scheduler; we do not keep a copy

4. Cookies, analytics and advertising

We use Google Analytics 4 to understand how people find and use this site. We may also advertise RavenPower through advertising partners such as Google (for example Google Ads), and measure "conversions", such as a visitor who clicked one of our ads later starting a subscription, booking a call or submitting a form. These tools load through Google Tag Manager and set cookies or similar identifiers in your browser only for the categories you allow (see below). Advertising tags run only if you allow the Advertising category.

Not on RavenPass card pages or public form pages. We load no Google Analytics, no Google Tag Manager and no other analytics on /c/* and /card-exchange/* and /card/new/* and /card/new and /f/* and /s/*. Those are the pages where someone opens a card, sends or deletes their contact details, or fills in a public form that a RavenPass customer has published. Section 1a tells card visitors we write nothing to their browser there, and a form's answers are for the customer who published it, so the tag does not run on any of those pages at all, rather than that promise being qualified.

What we collect for analytics and advertising

  • Pages you visit, how you got here (for example the referring site, ad click ID or campaign tags), and actions you take on the site, such as starting checkout or submitting a form.
  • Device and browser information, approximate location derived from your IP address, and the cookie or device identifiers set by these tools.

We do not use these tools to collect payment card details, and we do not knowingly target ads to children.

Categories of cookies and similar technologies

CategoryWhat it doesExamplesDefault
Strictly necessarySign-in, security, checkout and remembering your cookie choice. The site cannot work without these.Session cookie, consent-choice recordAlways on
Analytics (analytics_storage)Counts visits and measures how the site is used.Google Analytics _ga, _ga_*Off until you allow it*
Advertising (ad_storage, ad_user_data, ad_personalization)Measures ad conversions, sends ad-related data to Google, and allows remarketing (showing our ads to past visitors).Google Ads / GA4 conversion cookies such as _gcl_*Off until you allow it*

* This applies to every visitor, wherever you are: analytics and advertising stay off until you choose to allow them.

Google as a third party

Google receives the data described above as an independent provider of analytics and advertising services. To learn how Google uses it, see How Google uses information from sites or apps that use our services.

Google Consent Mode

We use Google Consent Mode v2 to pass your cookie choice to Google's tags. Google's tags do not load at all until you allow at least one category. Once you have allowed a category, the tags for any category you have not allowed do not set or read cookies for it, but they may still send limited "cookieless pings" without cookie identifiers, which can include the page, a timestamp, browser and device information, and whether you have consented. Google uses these pings to produce aggregated, modelled measurement. They are not used to build an advertising profile about you. If you later allow a category, the tags work normally from that point on.

You can change your choice at any time with the Cookie settings link in the footer of every page. U.S. residents can also use the Your Privacy Choices link in the footer. Withdrawing consent stops future collection for that category. It does not undo data already collected, but you can ask us to delete data we hold (see section 5). You can also clear cookies in your browser.

Your privacy choices and opt-outs

  • Our cookie banner: choose "Reject all" or turn the Advertising category off.
  • Global Privacy Control (GPC): if your browser sends a GPC signal, we treat it as a request to opt out of the sale or sharing of your personal information and of targeted advertising for that browser. We switch off advertising cookies and ad-data sharing, and we do not ask you to confirm.
  • U.S. state privacy rights (including California, under the CCPA as amended by the CPRA, and other states with similar laws): we do not sell personal information for money. However, allowing advertising cookies may count as a "sale" of personal information, or as "sharing" it for cross-context behavioral advertising, and as processing for "targeted advertising". You can opt out of all of these by choosing "Reject all" in the banner or in Cookie settings, by using the Your Privacy Choices link in the footer, by sending GPC, or by emailing us. We do not knowingly sell or share the personal information of anyone under 16. We will not discriminate against you for using these rights.
  • Google: manage ad personalization at Google Ads Settings (My Ad Center), and block Google Analytics with Google's Analytics opt-out browser add-on.
  • Industry tools: you can also opt out of interest-based ads from many companies at optout.aboutads.info and youronlinechoices.eu.

Opting out does not affect your ability to use the site or your account. You may still see ads, but they will not be based on your activity on this site.

Visitors in the EEA, UK and Switzerland

If you are in the European Economic Area, the UK or Switzerland, then as for all visitors, we set analytics and advertising cookies only after you have actively given consent, and consent is our legal basis for them (ePrivacy Directive / PECR and GDPR / UK GDPR, Art. 6(1)(a)). Rejecting is as easy as accepting, and we never treat silence, scrolling or continued browsing as consent. Google may process this data outside your country. Where it does, the transfer relies on safeguards such as the EU-U.S. Data Privacy Framework or Standard Contractual Clauses. You have the rights described in section 5 and the right to complain to your local data protection authority.

How long we keep it

  • Your cookie choice: 180 days, after which we ask again.
  • Google Analytics cookies: up to 2 years. Event data in our Google Analytics property is kept for 2 months, then deleted automatically by Google Analytics.
  • Advertising cookies (for example _gcl_*): up to 90 days. Google keeps ad data under its own policies.

Notes we save in your browser (not cookies)

When you fill in our project brief, we save your answers on your own device so you do not lose them if you reload the page. This can include your email, your business name and what you typed. It is kept in your browser under the name rp-intake-v1. It stays on your device until you send the brief, when we remove it, or until you clear your browser data. It is not sent to us until you press Submit. If you are signed in and have no saved draft with us yet, your account page may copy it into your account draft once. We do not use it for ads or tracking. Our cookie choices do not control it, but you can clear it in your browser settings.

4a. Sharing your details from a RavenPass card (RavenPass Connect)

If you scan or open someone's RavenPass card and use the RavenPass Connect form, what you type in that form is sent to the owner of that card. For those details the card owner is the controller: they decide how your details are used. We act as their processor (or "service provider"): we store your details for them, email them a copy and delete them on schedule. The owner's name, and company if any, is shown on the form before you send anything.

Nothing is filled in or sent unless you do it. The form uses only your browser's autofill, your phone's contact picker or your own RavenPass card if you are signed in. It never uses cookies, your IP address or third-party data sources. Card pages (/c/…) and the RavenPass Connect pages (/card-exchange/…) set no cookies and load no third-party tracking or analytics; the Google Analytics and advertising tools described in section 4 are not used on them. We count card views with our own first-party counter, which stores nothing in your browser. A Cloudflare Turnstile spam check may appear only when our spam controls trigger (see below).

How long we keep it. We keep what you sent for the period shown on the form, counted from when you ticked the consent box, and then delete it. The card owner chooses that period between 1 and 24 months; it is 12 months unless they change it. If the owner later shortens the period, your details are deleted sooner. They are never kept longer than the form said.

Deleting your details. You can withdraw your consent and have your details deleted at any time:

  • If you gave an email address, use the one-tap link in the confirmation email we send you.
  • Or ask us to delete your details. We check and act on the request within 30 days.
  • You can also ask the card owner directly. Our terms require businesses that use RavenPower to act on deletion requests within 30 days.

What deletion cannot reach. The notification email already delivered to the card owner, and any copy they exported, are outside our control. Our database provider (Cloudflare D1) keeps a point-in-time restore window of up to 30 days, so a deleted record can persist there until it ages out. We use that window only to recover from failures.

Our own limited use (spam and abuse protection). To keep the form safe for everyone, we run spam and bot checks as an independent controller, based on our legitimate interest in securing the service. These checks may include a Cloudflare Turnstile challenge and rate limits. We do not store your IP address; rate-limit records hold only a keyed hash and are deleted after 2 days. We do not store the Turnstile challenge token. We do not store browser details with your details. We keep a record of the exact consent wording each version showed.

We never use what you shared for our own marketing, for building audiences, for enriching it with other data, for selling or sharing it, or for training models. For access or correction, contact the card owner, or contact us (section 6) and we will pass your request on. Our processors for this feature are listed at /legal/subprocessors.

4b. The RavenPower iOS app and RavenPass App Clip

  • What the app collects: your account and sign-in details (name, email, and the account ID from Google, Microsoft or Sign in with Apple); your card content (name, title, business, phone, email, website); an optional headshot; and your subscription status. If you send your details to a card owner through the app or the App Clip, section 4a applies.
  • Sign-in: we use provider data only to sign you in. We never decide who owns an account by matching email addresses.
  • Headshot: optional and off by default. We use it only to put your photo on your Apple Wallet pass, never on a Google Wallet pass. It is deleted when you remove it or delete your account.
  • Pass sharing: Apple Wallet lets people forward a pass. Anyone who receives your card can pass it on without you knowing, and it shows whatever is on your card.
  • Purchases: You can subscribe on ravenpower.net (billed by our payment processor) or in the app through Apple. For Apple purchases, Apple handles payment and we never see your card. Apple bills, renews and refunds in-app purchases under Apple's terms. Apple sends us App Store Server Notifications and transaction data: product, original and current transaction IDs, purchase, renewal and expiry dates, storefront country, price and currency, and refund or revocation events. We use these only to switch your plan on and off and to keep billing records. We keep the raw App Store notifications for 90 days, and Apple transaction records as billing records for 7 years after the last transaction.
  • Booking: booking links open the card owner's booking provider, whose own privacy terms apply.
  • NFC tags carry only your public card URL.
  • No tracking: the app contains no advertising, analytics or tracking SDKs, and we do not track you across other companies' apps or websites.
  • Deleting your account in the app: Account → Delete account deletes your account, cards, headshot and leads. A Wallet pass already on a phone becomes blank the next time the phone checks in, and we stop sending it updates. If you used Sign in with Apple, we revoke our access with Apple. We delete your account data within 30 days of your request, and it leaves our backups within 30 days after that. We keep billing records for up to 7 years where tax law requires it, and a minimal record that your deletion request was completed (no profile details) for 3 years. Deleting your account deletes your own profile and data. Your organization's web subscription is cancelled immediately (no further charges; fees already billed aren't refunded; see our refund policy) only when the organization is deleted: when you are its only member, or when you choose to delete it. If you own an organization that has another admin, ownership passes to its longest-serving admin; the organization and its subscription continue, and we remove your card on file so they can add theirs within 30 days. If you own an organization with members but no admin, you can make a member the owner or delete the organization; your account is deleted either way, and if you don't choose, we delete the organization after giving members 30 days to export. Billing errors are still corrected. Deleting your account does not cancel a subscription bought through Apple; cancel it in iOS Settings → [your name] → Subscriptions. We void passes for deleted cards; a pass already on a device is cleared the next time that device checks in with Wallet.
  • Leads: leads saved to a card are kept for at most 24 months after your last contact with that person, or deleted sooner on request.

4c. Free cards

Free cards. A free card is a web card, and where offered it can include a RavenPower-issued Wallet pass. We delete a free card, and void its pass, after 12 months with no views and no sign-in by its owner, and we email you 30 and 7 days before. If you add the pass to Wallet, we keep the device registration identifiers and push tokens Wallet sends us only while the card exists. You must have permission to publish anyone else's details on your card, and anyone named on a card can ask us to remove their details.

Drafts stay in your browser until you press Create. If an AI assistant or another app prepares a card for you, it gives you a link to ravenpower.net/card/new with the draft in the part of the link after "#". Browsers do not send that part of a link to our servers, and our page removes it from the address bar as soon as it loads. The draft is held only in that browser tab's temporary storage, never in cookies, and we receive nothing until you sign in, review the preview and press Create. It is erased when you create the card, discard the draft, sign out or close the tab, or after a short time. Our analytics and error tools do not record it. Copies of the link itself may remain wherever it was kept, for example in your assistant's chat history, your messages or your browser history, and those are outside our control.

If you connect an AI assistant to your website brief. When you use Agent Connect, you can let an AI assistant fill in your brief. The assistant is run by another company. That company sees what the assistant reads and what you tell it, and we do not control it. We hide some answers you typed yourself, such as contact details, from the assistant, but not all of them. For each connection we keep a record: your account and brief, the name the assistant gave itself, when it connected and last used the connection, how many answers it wrote, and when it ended. For each answer the assistant writes, we keep which question it was, whether you accepted it, and a fingerprint of the answer. We make the fingerprint with a secret key that only we hold, so it cannot be turned back into your answer. We use it only to tell whether an answer is still the one the assistant wrote. We delete a connection record 7 days after the connection ends. Fingerprints of answers you accepted or typed yourself stay while your brief draft exists. We delete them 7 days after the draft is removed, or when you delete your account, whichever comes first. When you submit your brief, we keep two numbers with your submission: how many answers the assistant wrote, and how many of those you had not yet accepted. That record holds the numbers only, not the answers. When you delete your account, we delete the connection records, answer fingerprints and answer counts tied to your account, whoever wrote the answer. Records for a brief that another active account on your plan still uses stay with that account. This is on the same schedule as the rest of your account data (section 4b).

Each time a connection is used while Agent Connect is on, we keep an audit entry. That includes failed tries to connect. It holds the time, what happened, the result, internal IDs for your account, your brief and the connection, a one-way code made from your IP address with a secret key, and a one-way code made from the names of the questions. It holds no answers, no IP address and no browser details. We keep audit entries 400 days and then delete them. If you delete your account, we do not delete these entries early. They stay until that time is up. They carry internal IDs, not your name or email, but we could link them to you with our other records. We use them only to keep the service secure and to look into abuse.

What we keep when you create a free card. Your account details, the card content you publish, and a record of your acceptance: the Terms version, the wording of the confirmations you ticked (that you are 18 or older, and that you are authorised and have permission to publish everyone's details shown), the time, your account, and whether you chose to get product tips and upgrade offers. You decide what goes on your card, and we host it at your direction. We delete the card as described above. We keep the acceptance record for 3 years after the card is deleted, as evidence of the permissions you confirmed.

Free-card emails. We send account and security emails, and the inactivity notices described above, as part of the service. Inactivity notices contain no offers, and we send them even if you have unsubscribed from offers. We send product tips and upgrade offers only if you ticked the box asking for them. Each one has an unsubscribe link that works with one click, without signing in, and asks for nothing but your email address. We stop within 10 business days of your request, and usually at once. So that we keep honouring your choice after your card or account is deleted, we keep a keyed hash of your email address on a do-not-email list.

Who sends these emails. We send free-card emails through Cloudflare Email Service, with Resend, Inc. as a backup provider. Each acts as our processor and receives only your email address and the message it delivers. Both are listed in section 3 and on our subprocessors page.

If you are named on someone's card. If your name, photo, title or contact details appear on a card and you did not agree, use the Report this card link (choose "remove my details") or email [email protected]. We may ask you to confirm the details are yours. We hide them while we review your request, answer within 30 days, and remove them unless they are not about you. We tell the card owner that details were removed at the request of the person named, but we do not give them your email address unless you agree. You can also use the rights in section 5.

Reports. If you report a card, we keep your report, any email address you give us and what we did about it for 3 years after we close it, so that we can handle appeals and apply our abuse and repeat-infringer rules. Copyright notices and counter-notices are handled, and may be shared, as described on our Copyright (DMCA) page.

5. Your choices

You can ask for access to, correction of, or deletion of your personal information, or object to how we use it, by emailing us. We may ask you to confirm your identity, and we answer within 30 days. We don't sell your personal information for money, and we never sell or share card or lead data. If you are in the EEA or UK, you can also complain to your data protection authority. If you cancel, your live site goes offline and your RavenPass features end at the end of the paid period; we keep billing records for 7 years where tax law requires it. Account deletion is described in section 4b.

If a security incident affects your personal information, we will tell you without undue delay and within the time the law requires — in Florida, no later than 30 days — and tell you what happened and what you can do.

5A. Children

RavenPower is for businesses and professionals and is not meant for anyone under 18. We do not knowingly collect personal information from children. If we learn that a user is under 18, we disable their cards and delete their account data within 30 days. If you believe a child has given us personal information, contact us (section 6) or use the Report this card link.

6. Contact

Privacy questions: [email protected]. Data controller: Raven Power LLC, 4805 Nahane Way, Saint Johns, FL 32259.