1. Data Controller and Processor
getfAIve, Lda., tax ID (NIPC) 519759370, with its registered office at Praceta da Liberdade 10, 4.º esquerdo, 2680-285 Loures, Portugal (hereinafter "getfAIve"), acts in two capacities, depending on the data. It is the controller of the data of platform accounts and users, billing data, the website contact form, security and audit data and the usage report. It is a processor (Article 28 GDPR) for the data of the businesses' end customers (people who leave a rating, redeem a voucher or a promotion, are referred, refer someone, comment on the business's social media posts or open a conversation in the business's chat): the controller of that data is the business (the merchant) that served the person, and getfAIve processes it on its behalf and on its instructions, under the Data Processing Agreement. If you are an end customer of a business, address your requests to exercise your rights to that business; getfAIve helps you exercise them with that business. For any data protection queries, you can contact us at: privacidade@getfaive.pt
2. Data Collected
In the course of using the platform, we may collect the following personal data:
- Platform users: name, email, phone, role, authentication data, IP address and usage data.
- Reviewing customers: name (when provided), email, phone, numerical rating, comment, date and time of review, device data. This data, like that of people who redeem a voucher or a promotion, are referred or refer someone, is processed on behalf of the business that served the person, which is the controller.
- Company data: business name, logo, address, contacts, billing data.
- Google Business Profile data: when the user voluntarily connects their Google account, we access the account name, business locations, customer-published reviews (including author name, rating and comment), and the ability to publish replies on behalf of the owner. This data is obtained through the https://www.googleapis.com/auth/business.manage scope of the Google Business Profile API.
- Data from the Meta connections: when the user voluntarily connects a Facebook Page, the Instagram account linked to the Page or a Threads account, we process the Page's identifier and name, the accounts' identifiers and usernames, the access (token) to the Page and to the Threads account, and the identifier of whoever connected them. We read the public fields of the Page listing and of the Instagram profile (address, contacts, opening hours, description, website, name and biography).
- Comments on social media: on the posts of the business's Page, Instagram account and Threads account, the public name of whoever comments (on Threads, the username), the text of the comment, the business's replies and the dates. This data is processed on behalf of the business, which is the controller.
- Business chat conversations: the messages the interested person (whoever opens the chat) writes and the replies received, the summary and classification of the request (intent, interest and urgency) and, only if the person decides to leave them, the name and contact (email or phone). This data is processed on behalf of the business, which is the controller.
3. Purpose of Processing
Personal data is processed for the following purposes (end customers' data, on behalf of and on the instructions of the responsible business):
- Provision and management of the review collection service;
- Issuing and redeeming vouchers and promotions: the contact details of a customer who saves the voucher in their name (optional) are used to link it to that person and, if it is an email, to send the voucher confirmation; the name and the contact (email or phone) entered at the counter on redemption, of a voucher or of a promotion, which are required to redeem, are used to find the redemption in the voucher or promotion history of the business (people who work at the business can search for it), and the contact is also used to ensure one voucher per person per period and one promotion per person, and to measure redemption results (voucher redemption rate, redemptions per distribution channel of each promotion, purchase value and what was bought); for referrals, the name and the contact (email or phone) of the referrer, entered by the business when it issues the referral, are used to identify the referral and what results from it in the referral history of the business (people who work at the business can search for it by the name, or by the full email or phone number), to ensure that the referrer is not also the referred person and to measure results, and the name and the contact of the referred customer, entered at the counter on redemption, are used for that history, to ensure one referral per person at each business and to measure results (referrals, purchase value and what was bought); the redemption (the name and the contact) can be recorded without a purchase, for vouchers, promotions and referrals alike, and the purchase (the value and what was bought) is linked afterwards to the same record, the completion, which allows the completion rate (the share of redemptions that reach a purchase) to be measured; a person who redeems without buying still uses up the one-redemption-per-person rule; neither the name nor the contact is used to send messages, whether of the person redeeming or of the referred customer, and the referrer’s contact is used to send messages in one case only: if the referrer has given consent, which the business records when issuing the referral (the date and who recorded it), their email is used to send them a notice that one of their referrals has earned a reward, with the business name, the reward, the code and the validity, without advertising and without data about the referred customer, the seller or the purchase; the consent can be withdrawn at any time by asking the business, and with no email or no consent nothing is sent;
- Statistical analysis and generation of satisfaction reports;
- Support communication and operational notifications;
- Import and centralised management of Google Business Profile reviews, including the ability to respond to reviews directly from the platform;
- Publishing for the business on social media (Google, Facebook, Instagram and Threads), reading the comments on the posts and sending the replies written by whoever works at the business, with an AI text suggestion only when that person asks for it;
- Business chat (Opportunities): answering, with an AI assistant, whoever opens the conversation, handing the conversation over to a member of the team and recording the request on the business's opportunities board, for follow-up;
- Compliance with legal and regulatory obligations.
4. Legal Basis
The processing of personal data is based on the following legal bases, under Article 6 of the GDPR:
- Consent: for collecting reviewers’ contact details and for saving the voucher in the customer’s name, given through an express-consent checkbox, and for sending a referrer the email notice of the rewards they earn, given through a separate consent checkbox that the business ticks when issuing the referral after the person has agreed (the date and who ticked it are recorded) and that can be withdrawn at any time by asking the business;
- Contract performance: for the provision of the service to registered users;
- Legitimate interest: for service improvement and usage analysis;
- Legal obligation: for compliance with legal and tax requirements.
4b. Google Business Profile Integration
The getfAIve platform allows users to voluntarily connect their Google account to integrate Google Business Profile data. This integration uses the OAuth 2.0 protocol and requires the user's explicit consent.
Scope used: https://www.googleapis.com/auth/business.manage
Data accessed and purposes:
- Accounts and locations: listing of business accounts and locations for user selection;
- Reviews: import of Google reviews (author name, rating, comment, date) for centralised viewing in the dashboard;
- Replies: publication of replies to reviews on behalf of the location owner.
Token storage: OAuth access tokens are encrypted with AES-256-GCM before storage and are never shared with third parties. Tokens can be revoked at any time by the user in the platform settings.
Revocation: the user can disconnect their Google account at any time, which immediately revokes the platform's access to Google Business Profile data. Deactivating a location also automatically disconnects the associated Google account.
4c. Meta integrations (Facebook, Instagram and Threads)
The getfAIve platform lets whoever manages a business voluntarily connect that business's Facebook Page and the Instagram account linked to the Page, through Meta's login, and the Threads account, through the Threads login. They serve to keep the shop's listing the same on all platforms (Presence) and to publish, read and reply to comments on the business's social media (Social media). We only process data of the business's Page and accounts, never of the personal profile of whoever connects them; the data of whoever comments is processed on behalf of the business.
Data processed: the Page's identifier and name, the identifier and username of the Instagram account and of the Threads account, the access (token) to the Page and to the Threads account (the Instagram account uses the Page's), the identifier of whoever connected them (specific to our app on Meta) and the permissions granted.
Presence: we read the public fields of the Facebook Page listing (address, contacts, opening hours, description and website) and of the Instagram profile (username, name, biography and website), to compare them with the location's listing, and we update the Page listing and the profile and cover photos when whoever manages the business decides so. The Instagram account is only read and compared, never written to.
Publishing: at the request of whoever manages the business, we publish on Facebook, Instagram and Threads the text and image that person chooses, now or at the scheduled time, and we can withdraw a post made by getfAIve. An uploaded image is kept in temporary storage, without metadata, only until the posts that use it have gone out (one that no post uses is deleted after 24 hours); when the network only accepts the image through a public address, a temporary public copy is kept, deleted as soon as the post goes out.
Comments: we read the comments on the posts of the business's Page, Instagram account and Threads account (including those made outside getfAIve), only those written after the connection, by periodic reading and, when Meta sends them, by notices (webhooks) that only say which post to read again. We keep the public name of whoever comments (on Threads, the username), the text, the business's replies and the dates, so that whoever works at the business can see them and reply on the platform. Only at a person's request, the text of the post and of the thread, with the public names, go to Anthropic to suggest a reply, which that person reviews and sends; nothing is answered automatically. We do not access private messages or followers' data.
Where it is kept and for how long: access to the Page and to the Threads account is stored encrypted (AES-256-GCM) and remains while they are connected (the Threads one, valid for 60 days, renews itself). The temporary authorisation to choose the Pages and accounts lasts 15 minutes and is deleted afterwards. The stored comments and replies are deleted 12 months after the last activity in the thread, when the author deletes the comment on the network, when the business disconnects the Page or the account, and on Meta's data deletion requests.
How it is deleted: when you disconnect the Page (in Settings › Platforms) or the Threads account, the access and the comments of that Page or account are deleted immediately. You can also remove the getfAIve app in the Facebook or Threads settings, or request the deletion of the data there; you then receive a code to follow the request, which is completed on the spot. You can also write to us at the contact given in section 11.
4d. Business chat (Opportunities)
The business chat (Opportunities module) is a page, or a bubble on the business's website, where a person (the interested person) asks the business questions. The interested person starts the conversation. The controller is the business, which must state its own privacy policy in the chat and is the one who defines the legal basis for the processing; getfAIve processes the data on its behalf, as processor, under the Data Processing Agreement.
Data processed: the messages the interested person writes and the replies, the summary and classification of the request (what they are looking for, intent, interest and urgency), the location of the conversation and, only if the interested person decides to leave them, the name and contact (email or phone), which let the business follow up the request. You do not need to identify yourself to chat. Whoever works at the business sees the conversation and the contact; the email alerts to the team carry the interested person's first name, if they left it, and the three-line summary of the request, and do not carry the conversation, the email or the phone.
Artificial intelligence: whoever opens the chat talks to an AI assistant, identified as such in every message. It answers only with the information the business wrote for that purpose (the listing, the guide and the frequently asked questions), does not make bookings or orders, does not ask for reviews and never says it is a person. With each reply, the text of the conversation (the interested person's messages and the assistant's) is sent to Anthropic PBC (section 5.1), which does not use it to train models; the name and contact left on the contact card are not sent. The AI classifies the request, never the person, and only a person closes it.
Talking to a person: the «Talk to a person» button is always in view. The conversation is also handed to a member of the team when the interested person asks for it in writing or leaves their contact, when the AI does not have the answer, when the message is a complaint, when the limit of AI replies is reached or when the AI is unavailable; from then on the AI stops replying in that conversation. getfAIve does not send messages to the interested person or contact them again: if they leave their contact, it is the business that contacts them.
Cookies: the chat stores on the device, for 30 days, a cookie with the conversation identifier («getfaive_chat_» followed by the business identifier or, in the chat shown on the business's website, «getfaive_chatw_» followed by the business identifier), so that the interested person can resume the conversation. The cookie is signed and cannot be read by scripts. It is not used for advertising tracking or analytics.
Retention and rights: the conversation (messages, summary, classification and contact) is deleted 12 months after the last activity; those the business closes as won, 24 months after. Requests for access, rectification or erasure go to the business, the controller; getfAIve helps to exercise them and finds the conversation by the email or phone the interested person left (section 7).
5. Data Sharing
Personal data is not sold to third parties. It may be shared with: (a) sub-processors essential to the platform's operation (see section 5.1), under data processing agreements; (b) the contracting company, regarding their customers' reviews; (c) competent authorities, when required by law. All sub-processors are bound by confidentiality and data protection obligations (Article 28 GDPR).
5.1. Sub-processors
getfAIve relies on the following providers for the platform to operate. All have been assessed for GDPR compliance and security. Transfers outside the EEA are made under the Standard Contractual Clauses (SCC) approved by the European Commission.
- Vercel Inc. (USA) — Application hosting and CDN. Transfer under SCC.
- Neon Tech Inc. (servers in EU — Frankfurt) — Managed PostgreSQL database.
- Resend Inc. (USA; sending region configured in the EU — Ireland) — Transactional email delivery (invitations, password recovery, access codes, alerts, reports and, only with the referrer’s consent, the notice of a reward earned through a referral). Transfer under SCC.
- Anthropic PBC (USA) — Analysis and summary of reviews, suggestions and automatic replies to reviews, suggestions of replies to comments on social media, text of the monthly report (with aggregated indicators only) and replies of the AI assistant in the business chat, via Claude (Haiku 5.5 model). Transfer under SCC. Data sent is not used to train models.
- Google LLC (USA) — Google Business Profile API (importing public reviews and posting replies). Only enabled if the user connects their Google account.
- Functional Software Inc. (Sentry) (USA; storage region configured in the EU) — Technical error and performance monitoring. Transfer under SCC. Filters applied to remove personal data before sending.
- Upstash Inc. (servers in EU) — Temporary cache for usage limits (rate limiting). It contains IP addresses and pseudonymised identifiers (for example, the hash of an email or a user identifier), and keeps them only for a time that runs from a few minutes up to a maximum of 48 hours, depending on the limit. It also keeps, for 5 to 15 minutes, cached responses from the Google API (the accounts and locations of the business's Google Business Profile and the results of searches for places, such as competitors). In addition, it keeps the state of a protection circuit (circuit breaker) against Google failures, which is just a technical indicator.
- Meta Platforms Ireland Limited (Ireland) — Facebook and Instagram Graph API and Threads API (reading and updating the Page listing; publishing, reading comments and replying on the posts of the business's Page and accounts). Only activated if whoever manages the business connects a Page or an account.
This list is updated as of November 2026. Material changes will be communicated by email to users 30 days in advance.
6. Data Retention
Personal data is kept for as long as it is needed for the purposes it was collected for. User accounts, and the score and comment of collected reviews, are kept while the client company has an active service. The name, email and phone number of the person who reviewed (when given, with consent) are kept for 24 months after the review (or, if later, after the last voucher or redemption in the same person's name) and are then cleared; the score and comment remain, without the contact details. Some data has its own deadline and is deleted automatically: password recovery links and unaccepted invitations, once they expire; access codes, after their 10 minutes of validity; technical job and API call logs, after 90 days. The client company may at any time request deletion of its data and of its reviewers' data, through the email in the Contact section; the request is carried out within 30 days, unless the law requires the data to be kept. The name and the contact entered when a voucher or a promotion is redeemed at the counter are kept for 24 months after redemption and are then cleared (the redemption itself, the billed amount, the purchase category, the promotion channel and the redemption location are kept). The name and the contact of the referred customer, entered at the counter when a referral is redeemed, are cleared on the same term, counted from redemption (the redemption itself, the billed amount, the purchase category, the position of the referral, the referrer’s rewards and the redemption location are kept); the name and the contact of the referrer, entered by the business when it issues the referral, are also cleared on the same term, but counted from the end of the referral’s validity and of its rewards (whichever ends later); for a referral with no expiry, that term is counted from its last activity (issue, reactivation or a new referral) and restarts with each new referral. The term for the name and the contact of the person redeeming (voucher, promotion or referred customer) is always counted from the redemption, with or without a purchase, even if the completion (the purchase linked to the redemption afterwards) comes later; a completion made after that term has no personal data. The one-redemption-per-person rule (one voucher per period; one promotion only once, whichever channel it came from) is checked with an irreversible signature of that contact, not with the contact itself, and that signature is kept for up to 24 months after the period the redemption belongs to ends (that of the voucher or that of the promotion) or, for a referral (one per person at each business), after the redemption: after that term the “already referred” mark is deleted and the same person can be referred again. For a promotion with no end date, the signature is kept while the promotion is active and, once it is deactivated, for the same term. The name, email and phone number of a customer who saves the voucher in their name (optional) are cleared once all of that person’s vouchers were redeemed or expired more than 24 months ago (for a voucher with no expiry that has not been redeemed, that term is counted from the moment the contact was saved); contact details given in a review, with consent, follow the deadline stated above for the contact details of the person who reviewed. The date of the consent to the referrer’s email notice, and who recorded it, stay with the referral record even after the referrer’s name and contact have been cleared (on their own they identify no one and document the consent for notices already sent); getfAIve keeps no other copy of that email and reads it from the referral record at the moment of each sending. Deletion of the redemption name and contact, and of the referrer’s, can be requested on the same terms; and when a user account is deleted, the redemption name and contact tied to the email of that account are cleared too (including the referrer’s, for referrals), while the signature is kept so that the one-redemption-per-person rule does not reopen.
Comments on the posts on social media (the public name of whoever comments, the text and the replies) are kept for 12 months after the last activity in the thread and are then deleted; they are also deleted when the author deletes the comment on the network, when the business disconnects the Page or the account and on Meta's data deletion requests. Business chat conversations (messages, summary, classification and the contact left) are kept for 12 months after the last activity and are then deleted; those the business closes as won are kept for 24 months. Access to the connected Page and accounts is deleted on disconnecting.
7. Data Subject Rights
Under the GDPR, data subjects have the following rights:
- Right of access: obtain confirmation and a copy of personal data processed (Article 15);
- Right to rectification: request the correction of inaccurate or incomplete data (Article 16);
- Right to erasure: request the deletion of personal data, where applicable (Article 17);
- Right to portability: receive personal data in a structured, machine-readable format (Article 20);
- Right to object: object to the processing of data in certain circumstances (Article 21);
- Right to restriction: request the restriction of data processing (Article 18).
To exercise any of these rights, address your request to the controller: getfAIve, for the data it controls, and the business that served you, for end-customer data (for example, if you left a rating, redeemed a voucher or a promotion, were referred, referred someone, commented on a post of the business on social media or used the business's chat). If you are unsure how to do this with the business, getfAIve will help you. Contact us at privacidade@getfaive.pt
8. Cookies
The platform uses cookies that are strictly necessary for the service to work (authentication and session). No advertising tracking or analytics cookies are used. In addition, the language cookie "NEXT_LOCALE" (1 year) is stored and, on the public review screen, three cookies of 24 hours each: "getfaive_review_cd_" followed by the location identifier (prevents reviewing the same location twice from the same device), "getfaive_cartao_cd_" followed by the contact point identifier (prevents the same device from reviewing again through that card at any branch for 24 hours; stores only the branch reviewed and the expiry) and "getfaive_vale_cd_" followed by the business identifier (keeps the voucher already opened). You can set your browser to refuse cookies, although that may affect how the platform works. The business chat cookies are described in section 4d.
9. Security
We implement appropriate technical and organisational measures to protect personal data against unauthorised access, loss, destruction or alteration. These measures include data encryption in transit (TLS), OAuth token encryption with AES-256-GCM, secure password hashing (bcrypt), role-based access control and a security review of the code before each release.
10. Changes
This Privacy Policy may be updated periodically. Any significant changes will be communicated to users by email or through a notification on the platform, with a minimum of 15 days' notice.
11. Contact
For any questions related to this Privacy Policy or the processing of your personal data, contact us at: privacidade@getfaive.pt
You also have the right to lodge a complaint with the Portuguese Data Protection Authority (CNPD) — .www.cnpd.pt