Privacy Policy

What we collect depends on how you interact with PerkUp. For Members, Recipients, and administrators acting within an Organization’s program, we hold the data below as that Organization’s processor (Section 2), while PerkUp controls the account, billing, and contract relationship with the Organization (Section 2.3).

3.1. Website visitors. Device and browser data, pages viewed, approximate location inferred from your IP address, and analytics events (including form submissions), collected through the cookies and tools described in Section 7.1, which also describes the support chat widget on our site.

3.2. Demo requests and business contacts. When you request a demo, we collect your work email and anything else you submit through our form-handling provider, and the form records the campaign parameters in the link you arrived from (for example utm_source) so we know which campaign brought you. We store these details in our CRM to respond, schedule, and follow up. For billing, vendor, and partner contacts, we hold names, business contact details, and correspondence. We may also obtain business contact details from publicly available professional sources, such as company websites and LinkedIn. When we first contact you, and in any event within one month of obtaining your details, we point you to this policy, which tells you that your details came from such a source; you can object to further contact at any time by replying or emailing legal@perkupapp.com, and we then stop and delete the record.

3.3. Customer administrators. Account and profile data (name, email, profile picture), Organization settings, roles and permissions, billing records, support conversations, and product usage data (Section 7). Payment-card details are collected directly by Stripe, our payment processor; PerkUp does not store cardholder data and retains only payment tokens and non-sensitive payment metadata, such as card brand, last four digits, and expiration date. When an administrator or sender searches for a GIF or stock image for a reward, template, or redemption page, their browser sends the search terms to Giphy or Unsplash under those providers’ privacy policies.

3.4. Members. When an Organization invites or provisions you, we process:

• identity and contact data: name, work and (where provided) personal email, phone, profile photo;

• employment attributes your Organization syncs from its HRIS or directory: title, department, manager, location, start and end dates, employee ID, employment status, and leave-of-absence information, including any employer-assigned labels (custom fields the Organization chooses to sync);

• your date of birth and start date, which your Organization’s HRIS synchronization includes unless the Organization turns it off, or which it uploads by file, used for birthday and anniversary programs;

• if you request a prepaid card, your date of birth and the IP address of your request, which the card issuer requires; we keep a copy of the cardholder record for the life of the card program and as financial-record law requires (Section 6.5);

• where your Organization connects Slack: the workspace member list (names, usernames, and emails), which we read to match you to your account, your Slack username, the messages we send you there, and your notification preferences;

• reward, order, redemption, and balance data (for Personal Funds you load from your own payment method, PerkUp is the controller, Section 2.3);

• shipping addresses you save, or, where your Organization enables it, a home address synced from its HR system;

• messages you write (recognition posts, gift notes) and images or designs you upload.

Much of this comes from your employer rather than from you: email invitations, roster imports, HRIS synchronization, single sign-on and directory sync, and workspace tools your Organization connects. How we treat what those systems send:

• HRIS synchronization writes only the fields your Organization has chosen to sync; sensitive field names are blocked, and custom fields require an allow-list. If your HRIS supplies a preferred name, we use it as your display name. Other attributes your HRIS transmits in its responses, such as gender, are not mapped to your profile or used for any purpose.

• Directory sync through your identity provider maps your employee ID, division, department, cost center, subsidiary, region, executive flag, country, employment type, leave dates and type and, where your Organization configures it, a shipping address into your profile and its labels. We keep the directory record your identity provider sends, including attributes we do not map, so we can reconcile changes; it is stored with your Member record and deleted with it (Section 8.2).

3.5. Gift recipients, store shoppers, and other people without accounts.

• When an Organization sends you a gift or reward, we email or message you on its behalf so you can claim it, choose options, and confirm or enter your delivery address. If you claim it through a reward link or redemption page, we collect the email, name, shipping address, phone number, and product choices (such as size) you enter, plus any gift message addressed to you. You can stop reminder emails using the link in the message; an unclaimed reward returns to your Organization under its program rules. If you never claim a gift, we keep the contact details the sender gave us only as long as the Organization’s program needs them, and delete them under Section 8.

• Where the destination country requires it to clear or invoice a shipment, we collect a customs or tax identification number with your delivery details: a Brazil CPF or CNPJ, China Resident ID, Korea PCCC, or Mexico RFC. We ask for it only on the delivery form for that country and use it solely to clear or invoice your shipment. It is stored with the delivery address it belongs to, is never used for anything else, and is deleted with that address or with your account or program data under Section 8.

• If you buy in a hosted swag store as a guest, we collect your name, shipping address, email, and order details; your payment card goes directly to Stripe. Guest shoppers receive only order and delivery messages.

• If you play a game at an Organization’s event, we collect, on the Organization’s behalf and under the notice it shows you, the name and email you enter, a shipping address if you win a physical prize, your marketing-consent choice, and a hashed form of your IP address kept with the draw record to detect abuse and audit the result; the Organization decides how long it keeps entries. Where PerkUp itself offers a prize, discount, or gift in exchange for your contact details, that is a financial incentive under California law. You opt in by entering your details on the game or offer form; you may withdraw at any time by emailing legal@perkupapp.com, and we then delete your entry. We estimate the value of your contact details at the retail cost of the prize or discount offered, because that cost is what we spend to obtain them and we do not sell or otherwise monetize them; that estimate is the basis for the incentive.

• When you type an address in the product, your browser sends it to our address-autocomplete provider (currently Mapbox) to suggest and validate it. We also send an Organization’s business address to Google to geocode it and set the Organization’s time zone.

• Where your Organization imports your contact details from its CRM, calendar, or form tools (Section 6.4), we receive the fields it maps and may write reward status back to its record of you at its direction.

• The notices we email you report delivery and engagement events (delivered, bounced, opened, clicked) back to us so we can troubleshoot them, and once your reward link is validated on a redemption page we label the session-replay recording with the email and name on the reward so support can find your session (Section 7.2).

3.6. Where data comes from. Directly from you; from your Organization or the gift sender (including the HRIS, directory, single sign-on, workspace, CRM, calendar, and form systems it connects, Section 6.4); automatically from your device and your use of the Services (Section 7); and from our service providers, such as payment status from Stripe and delivery events from carriers and tracking providers.

3.7. Sensitive data. The Services do not require, and we do not request, special categories of personal data (such as health, biometric, or religious data), payment-card numbers (Stripe collects those directly), or government-issued identification numbers, except the customs or tax identifiers described in Section 3.5. Sensitive information may appear incidentally in free text (for example, a recognition message) or in HRIS fields an employer configures; we do not use it for any other purpose, and we never sell it. Where a privacy law requires opt-in consent to process sensitive personal data, we obtain that consent or do not process the data. The Services are not designed to process protected health information, and PerkUp does not act as a HIPAA business associate; Organizations should not configure programs that require it.