Privacy
Privacy Policy
How XPLENDOR handles personal data and advertising data of its customers, including the data received from Meta (Facebook and Instagram).
On this page
- 1. Data controller
- 2. Who this policy applies to
- 3. Account and Platform usage data
- 4. Data received from Meta (Facebook and Instagram)
- 5. Where Meta data is stored, for how long and how it is deleted
- 6. Measurement on customer websites
- 7. Quotes
- 8. Content approval by link
- 9. XPLENDOR invoices and payment reminders
- 10. Management by agencies
- 11. Sharing with third parties
- 12. International transfers
- 13. Security
- 14. Your rights (GDPR)
- 15. Changes to this policy
1. Data controller
The controller of the data described in this policy is:
- Entity: SIMON COSTA, UNIPESSOAL LDA, which operates the XPLENDOR brand
- Tax number (NIF): 517343355
- Address: Rua Camilo de Oliveira, 101, 4.º Esq., Rio Tinto, Gondomar
- Privacy contact: xplendorcar@gmail.com
XPLENDOR is the business management and marketing analytics platform available at xplendor.tech and in the related web application (the "Platform").
2. Who this policy applies to
This policy applies to:
- visitors of this website;
- companies that are customers of the Platform and the users they authorise;
- visitors of customer websites that installed the XPLENDOR measurement script (section 6);
- people and companies to whom XPLENDOR sends quotes (section 7);
- people who receive a content approval link (section 8);
- companies managed by an agency on the Platform and the agencies that manage them (section 10).
3. Account and Platform usage data
- Account data: name, email address and password (stored only as an irreversible hash).
- Company data: legal name, company tax number, contacts and other data the customer enters.
- Business data the customer enters or imports (for example vehicles, sales, expenses, aggregated bookings).
- Server technical logs (for example requests, errors and synchronisation dates).
Purpose: to provide the contracted service. Legal basis: performance of the contract with the customer (Article 6(1)(b) GDPR).
Contact form on this website: name, email and message, sent through the Formspree service so that we can reply. Legal basis: steps taken at the request of the data subject prior to entering into a contract.
4. Data received from Meta (Facebook and Instagram)
This section specifically describes the data XPLENDOR receives from Meta through Facebook Login. There are two separate connections, each with its own permissions: the advertising connection (the Meta ad account) and the social media connection (the company's Facebook Pages and Instagram professional accounts). Each connection is started by an administrator of the customer company or, when the company is managed by an agency on the Platform (section 10), by an administrator of that agency, with the customer's authorisation. The customer can disconnect each connection at any time without affecting the other.
4.1 Permissions requested
Advertising connection: XPLENDOR requests only the ads_read permission, to read the performance data of the ad account selected by the customer.
Social media connection: XPLENDOR requests only three permissions:
- pages_show_list, to list the Facebook Pages the customer manages, so that the customer can choose which ones are linked to the company;
- pages_read_engagement, to read the follower count of the chosen Pages;
- instagram_basic, to identify the Instagram professional account linked to each Page and read its follower count.
XPLENDOR only reads data. It does not publish, create, edit, pause or delete campaigns, ads, audiences, posts or any other content on Meta.
4.2 What we collect and why
- Access token: the long-lived token issued by Meta and its expiry date. It is used only so that the Platform can request the data below on the customer's behalf. It is stored encrypted (AES-256-CBC) in the database and is never shown in the browser.
- The ID of the ad account chosen by the customer.
- Campaign structure: IDs and names of campaigns, ad sets and ads, and the status of each ad (active, paused, etc.).
- Daily performance metrics: spend, impressions, clicks, reach, frequency, CPM, CTR and CPC, per account, campaign and ad.
- Metrics aggregated by age range and gender (impressions, clicks, spend and reach). These are statistical totals provided by Meta and do not identify individuals.
- Ad set targeting settings (for example the ages, locations and interests chosen by the advertiser), and interest searches in Meta's targeting catalogue.
- Custom audience metadata: ID, name, type, approximate size, delivery status and last update date. XPLENDOR does not receive or store the list of people in those audiences.
Purpose (advertising): to show the customer how much they spent on advertising, what results they obtained, which ads relate to each product (for example each vehicle), and to relate that spend to the sales the customer records in the Platform. From this data the Platform calculates indicators such as cost per contact and records Meta spend as a marketing expense of the customer.
In the social media connection:
- Access tokens: the long-lived token issued by Meta for this connection, its expiry date and the numeric ID Meta assigns to the Facebook account that authorised it; and the token of each chosen Page. They are stored encrypted (AES-256-CBC) in the database and are never shown in the browser.
- Facebook Pages: ID, name and profile picture. Instagram professional accounts: ID, name, username and profile picture. We store only the ones the customer chooses, and which one is the main account of each network. The profile picture is copied at most once a week and is deleted on disconnection.
- Follower count, read once a day, of each chosen Page and account; for the Instagram account, also the number of accounts followed and of posts. A daily history is kept per company.
Purpose (social media): to show the customer, in the Brand Profile, the current followers and their growth over time, to adapt the post format suggestions to the size of the audience and to show the account's real name and profile picture in the post previews.
Legal basis: performance of the contract with the customer, who expressly authorises the connection.
4.3 What we do not collect
- Data about individual Facebook or Instagram users (profiles, contacts, messages, comments or audience member lists).
- Meta lead form data, Pixel data or Conversions API data.
- The content of Pages and Instagram accounts (posts, comments, messages, post statistics) or the list of followers: only the total follower count.
- Ad account billing data.
4.4 Limited use
Data received from Meta is used only to provide the Platform to the customer who authorised it. It is not sold, not used for third party advertising, not shared with other customers and not used to train artificial intelligence models.
5. Where Meta data is stored, for how long and how it is deleted
Where: in the Platform database, on servers hosted by Hostinger (Hostinger International Ltd.) in Paris, France, in the European Union, separated by customer company. Each company can access only its own data.
How long: campaign performance and structure data is kept while the customer's Platform account is active, to allow historical comparisons. There is currently no automatic deletion based on age.
When the customer disconnects the integration in the Platform:
- XPLENDOR asks Meta to remove only the ads_read permission from the customer's account and then deletes the access token; the integration stops requesting advertising data from Meta; the social media connection, if any, is kept;
- if Meta does not accept the request (for example because the token has already expired), the disconnection still completes and the customer can remove XPLENDOR in their Facebook settings (Settings and privacy, Business integrations);
- the customer chooses what happens to the data already received: by default, the history (metrics, campaign structure, audience metadata and calculated expenses) is kept in the account for reference; alternatively, the customer can immediately delete all data received from Meta, after explicit confirmation;
- when deleting, the sales recorded by the customer are kept, without any link to campaigns or ads.
When the customer disconnects the social media connection in the Platform:
- XPLENDOR asks Meta to remove, one by one, only the three social media permissions (pages_show_list, pages_read_engagement and instagram_basic); the advertising connection is not affected;
- the access tokens and the chosen Pages and accounts are deleted and XPLENDOR stops reading followers;
- the customer chooses what happens to the follower history: by default it is kept for reference; alternatively, the customer can immediately delete the counts read automatically from Meta, after explicit confirmation. Values the customer entered manually are kept.
The follower history is kept while the customer's Platform account is active, unless the customer deletes it earlier.
When the customer switches to a different ad account, the metrics and ads of the previous account are deleted.
When the customer's Platform account is closed, all company data, including the data received from Meta, is deleted from the database.
Later deletion: if the history was kept, the customer can delete it later in the Platform (Integrations) or request deletion by email, without closing the account. Instructions and timeframes are on the Data Deletion page (/en/data-deletion/).
Technical logs: server logs may contain account and campaign IDs and error messages returned by Meta; they do not contain access tokens. They are kept for 14 days and then deleted automatically.
Backups: [DESCREVER CÓPIAS DE SEGURANÇA E PRAZO].
6. Measurement on customer websites
Customers may install an XPLENDOR script on their own website to record visits coming from ads. The script stores a random visitor and session ID, the page visited, the campaign parameters in the URL (UTM), the ad ID and the advertising platform click ID (for example fbclid or gclid), and interactions such as clicks on phone, WhatsApp or form.
In that case the customer is the controller towards the visitors of their website, and XPLENDOR acts as a processor on the customer's behalf. The customer is responsible for informing its visitors and obtaining any required consent.
7. Quotes
When XPLENDOR sends a quote, it also sends a link to a page where the recipient can view it, download it as a PDF and respond: accept it, in full or in part, refuse it or ask for changes. Each link gives access to a single version of the quote, cannot be guessed and the page is not indexed by search engines.
7.1 Customer data in the quote
Name, email, phone number and tax number of the person or company the quote is for, the proposed services and the amounts. They are used to prepare the proposal and, if it is accepted, to start the service. Legal basis: steps taken at the request of the data subject prior to entering into a contract.
7.2 Link opens
We record when the link is opened, so that the team knows whether the proposal was seen and when a follow up makes sense. For each open we store only the date and time and the type of device (mobile or computer).
- We do not store the IP address: it is used only at the moment of the request, to limit abusive requests, and it is not recorded.
- So that reloading the page in the same browser counts as the same open, the page stores a random identifier in the browser. On the server, that identifier is kept only in irreversibly hashed form and does not identify the person.
- Automatic link previews (for example from WhatsApp, social networks or email link checkers) and opens by the XPLENDOR team are not recorded.
- The page does not use cookies or third party analytics tools. The Platform base font is loaded from Google Fonts, which receives the browser IP address in order to deliver that file.
Legal basis: XPLENDOR's legitimate interest in following up the proposals it sends.
7.3 Record of the response
When the quote is accepted, we store the name and email provided, the confirmation that the terms were read and accepted, the date and time, the accepted services and the resulting totals. When it is refused or changes are requested, we store the reason or message, if given, and the date and time. This record is the proof of acceptance and the basis for starting the service. Legal basis: pre-contractual steps, performance of the contract and compliance with legal obligations.
7.4 Retention
- opens: 12 months, then deleted automatically (only the total number of opens of the quote is kept);
- acceptances, refusals and change requests: 10 years, the retention period for commercial records, then deleted automatically;
- the quote itself (customer data, services and amounts): for as long as needed for the business relationship and XPLENDOR's legal obligations.
You can request access to or deletion of this data as described in section 14 and on the Data Deletion page (/en/data-deletion/). Acceptance records are kept for as long as there is a legal obligation to keep them.
8. Content approval by link
Platform customers can send the person who approves their content (for example, the brand manager) a link to a page where they see the prepared posts, with an approximate preview of how they will look on the networks, and approve them, ask for changes or comment, without needing an account. Each link only gives access to the posts in that batch, cannot be guessed, expires after 14 days (the sender can extend or revoke it) and the page is not indexed by search engines. Post files only open through temporary addresses, valid only for that batch and while the link is active.
When the customer company sends the link, it is the controller of this data and XPLENDOR processes it on its behalf, as the Platform provider.
8.1 Data about the link recipient
The recipient's name and email, if the sender provides them, to send the link and a single reminder if the posts are still waiting. Legal basis: performance of the contract with the Platform customer and legitimate interest in getting the approval in time.
8.2 Link opens
We record opens as for quotes (section 7.2): only the date and time and the device type. We do not store the IP address; the random identifier the page stores in the browser is kept on the server only as a hash; automatic link previews and opens by the XPLENDOR team and by the agency that manages the company are not recorded; the page does not use cookies or third party analytics. They let the sender know whether the batch was seen and when a reminder makes sense. Legal basis: legitimate interest.
8.3 Record of decisions and comments
When a post is approved or changes are requested, we store the name given by the person deciding, the decision, the message (if any), the post version, the date and time and the device type. Each version accepts only one decision. Comments are stored with the given name and the date. This record is part of the post history and is the proof of approval. Legal basis: performance of the contract with the Platform customer.
8.4 Retention
- opens: 12 months, then deleted automatically (only the total number of opens of the link is kept);
- decisions, comments and the recipient's name and email: while the customer's account is active, as part of the post history; they are deleted with the account or at the customer's request;
- post files: according to the Platform rules (files of replaced versions are deleted after 30 days; originals of published posts are kept for 12 months).
You can request access to or deletion of this data from the company that sent you the link or from XPLENDOR, as described in section 14.
9. XPLENDOR invoices and payment reminders
XPLENDOR does not issue invoices on the Platform: it issues them with certified invoicing software and uploads the invoice PDF to the Platform, so that the customer can see it, follow the payment status and receive reminders. The invoice appears in the customer company's Expenses (read only) and on its own page, opened by a link sent by email, where the PDF can be downloaded and "I have paid" can be indicated, without an account. Each link only gives access to that invoice, cannot be guessed, stops working when the invoice is cancelled or 90 days after it is paid, and the page is not indexed by search engines. A company's XPLENDOR invoices are only visible to that company's users and to XPLENDOR (never to an agency that manages the company).
9.1 Data processed
- the company name, the amount, the description, the invoice date and the due date, and the invoice PDF;
- the company's billing email or, if there is none, the name and email of its administrators, where the emails are sent;
- the date of the emails sent (a new invoice, on the due date and then on Mondays, until it is paid, cancelled or payment has been indicated; never more than one a day);
- when the customer indicates payment: the date and time, the channel (link or Platform), who indicated it (inside the Platform), the note and the proof of payment, if attached (PDF or image, up to 10 MB);
- XPLENDOR's confirmation or refusal of the payment, with the refusal note.
Reminder emails are only sent if the company turns them on ("Send payment reminders", off by default); the company can turn them off at any time in the company profile. Legal basis: performance of the contract with the customer and compliance with legal obligations.
9.2 Link opens
We record opens as for quotes (section 7.2): only the date and time and the device type. We do not store the IP address; the random identifier the page stores in the browser is kept on the server only as a hash; automatic link previews, email link checkers and opens by the team are not recorded; the page does not use cookies or third party analytics. Legal basis: legitimate interest in knowing whether the invoice was seen.
9.3 Retention
- opens: 12 months, then deleted automatically (only the total number of opens is kept);
- invoices, proofs of payment and the payment record: 10 years, the legal retention period for accounting records;
- the billing email and the reminders setting: while the customer's account is active.
You can request access to this data as described in section 14. Accounting records are kept for as long as there is a legal obligation to keep them.
10. Management by agencies
An agency can manage a customer company's account on the Platform: when the company accepts, on the Platform, a management request from the agency, or when XPLENDOR sets up that relationship at the request of both parties.
- Roles: the customer company is the controller of its data; the agency processes it on the customer's behalf, as the customer's processor; XPLENDOR provides the Platform, also as a processor.
- What the agency sees and does: it works in the company's active areas (for example the Editorial Line, Blog and Brand Profile), sees results and alerts, and agency administrators can connect integrations on the company's behalf. The agency does not manage the company's users or access, does not approve content on its behalf, does not change or delete the company's data and does not see XPLENDOR invoices.
- Who at the agency has access: the whole agency team or, when the agency limits it, only the people assigned to the customer. Production notices for that customer go to those people and to the agency's notification email.
- Management requests: the agency identifies the company by its tax number (NIPC) or by an administrator's email. The answer to the agency never reveals whether the company exists. When the tax number or email does not match any company, it is deleted 30 days after the request expires or is withdrawn.
- End of the relationship: the customer can end the relationship at any time, on the Platform; the agency and XPLENDOR can also end it. The agency's access is removed immediately and the data stays in the customer's company. Meta connections made by the agency are kept or disconnected as the customer's administrator chooses.
- Company without an administrator: if the relationship ends and the company has no administrator, the company is archived (no access) for 90 days, with a notice to the company's contact at the start and 7 days before the end, and the connections made by the agency are disconnected. At the end of the 90 days, the working data is permanently deleted; only XPLENDOR invoices and charges are kept, for 10 years, as required by law, together with the company's minimum identification (tax number and name).
12. International transfers
The Platform and its database are hosted in the European Union (Paris, France). Some providers may process data outside the European Economic Area (EEA):
- Anthropic: the contract is with Anthropic Ireland, Limited. Data may be processed outside the EEA, including in the United States, by Anthropic and its sub-processors. The applicable safeguard is the European Commission's standard contractual clauses (Implementing Decision (EU) 2021/914, modules two and three), incorporated in Anthropic's data processing addendum, which forms part of its commercial terms.
- OpenAI: the contract is with OpenAI Ireland Ltd. Where it transfers data to other OpenAI group companies or to third parties outside the EEA, including in the United States, it does so on the basis of the European Commission's standard contractual clauses (modules two and three) or an adequacy decision of the European Commission (Article 45 GDPR), under OpenAI's data processing addendum.
- Formspree (this website's contact form): [CONFIRMAR LOCAL DE TRATAMENTO E GARANTIA APLICÁVEL].
To learn about the applicable safeguards or obtain a copy, write to the contact given in section 1. [CONFIRMAR: DATA DE ACEITAÇÃO DOS ACORDOS DE TRATAMENTO DE DADOS DA ANTHROPIC E DA OPENAI E SE FOI FEITA UMA AVALIAÇÃO DE IMPACTO DAS TRANSFERÊNCIAS].
13. Security
Access tokens for external platforms are stored encrypted. The Meta app secret exists only on the server. Access to the Platform requires authentication and every request is checked so that a user can only access the data of their own company. Communications use an encrypted connection (HTTPS).
14. Your rights (GDPR)
Under the General Data Protection Regulation you may, at any time, exercise:
- the right of access to your data;
- the right to rectification of inaccurate or incomplete data;
- the right to erasure (deletion) of your data;
- the right to restriction of processing and the right to object;
- the right to data portability for the data you provided;
- the right to withdraw an authorisation you gave, for example by disconnecting the Meta integration, without affecting processing carried out before that.
To exercise these rights, write to xplendorcar@gmail.com. We reply within one month of receiving the request, extendable in the cases provided for in the GDPR, and we may ask the requester to confirm their identity.
You also have the right to lodge a complaint with the Portuguese data protection authority, Comissão Nacional de Proteção de Dados (CNPD), at www.cnpd.pt.
15. Changes to this policy
This policy may be updated to reflect changes to the Platform or to the law. The date of the last update is shown at the top of the page. Relevant changes are communicated to customers by email or in the Platform.

