Privacy Policy
At NextBlog, we take your privacy very seriously. This policy describes how we collect, use and protect your information.
Effective from 7 November 2026
1. Introduction
Welcome to NextBlog. This Privacy Policy describes our policies and procedures regarding the collection, use and disclosure of your information when you use the Service, and informs you about your privacy rights and how the law protects you.
This policy explains how your data is processed. Browsing the website or accepting this policy does not, by itself, constitute consent to receive advertising.
This policy covers your account data and data from requests and subscriptions made directly to us: the data you provide when registering, purchasing and using the platform, requesting our resources, completing our forms, asking for information or subscribing to our content, where we act as the data controller.
It does not cover the data of the contacts, leads and subscribers you manage through the platform. For that data, you are the controller and NextBlog acts as a processor on your behalf: the applicable terms are those in Annex I to the Terms of Service. You are responsible for informing those individuals and handling their rights requests.
2. Controller of Your Data
The controller of your personal data is:
- Owner: Quim Pallàs Navarro (an individual, sole trader — self-employed in Spain). NextBlog is the service’s trading name.
- Tax ID: 39500378V
- Registered address: Calle Sant Francesc, 14 — 08183 Castellterçol (Barcelona), Spain
- Contact: contacto@nextblog.es
3. Data We Collect
We collect several types of information to provide and improve our Service for you.
3.1. Personal Data
While using our Service, we may ask you to provide certain personally identifiable information that can be used to contact or identify you. The personally identifiable information we collect includes:
- Email address.
- Username and company or business name.
- Billing details required to issue the invoice, including your tax ID. Payment details are collected and processed directly by the payment service provider: NextBlog does not store your full card details.
- The content of any communications you send us regarding support, issues or enquiries.
- Data you provide in our forms or resources: name, email address and, if requested, company, responses, generated results or reports and communication preferences. We may also retain the date, source, version of the information notice and evidence of your authorisations or unsubscribe requests.
We do not request or store your phone number or postal address for use of the platform, other than the billing details specified above.
3.2. Usage Data
Usage Data is collected automatically when you use the Service.
Usage Data may include information such as your device’s Internet Protocol address (for example, IP address), browser type, browser version, the pages of our Service that you visit, the time and date of your visit, the time you spend on those pages, unique device identifiers and other diagnostic data.
When you access the platform from a phone or tablet, this information also includes data automatically provided by your browser: device type, operating system and browser version. NextBlog is a web application and does not have a mobile app, so we do not collect advertising identifiers or app-specific unique device identifiers.
3.3. Google and YouTube data when you connect a channel
The YouTube integration is optional. We only process Google or YouTube data after you click to connect your channel and expressly accept Google’s consent screen.
- Connection data: the identifier, name, custom URL and thumbnail of the channel you authorise; the permissions granted and connection status.
- OAuth credentials: access and refresh tokens, their expiry and the permissions granted. We store them in encrypted form and use them solely to maintain the connection and perform the actions you request.
- Data from posts created through NextBlog: video file, title, description, language, category, audience settings, visibility, scheduled date, identifier, link and the video’s processing or publication status.
The YouTube integration does not request access to your Gmail, Drive, contacts or data from other Google services. Nor do we use Google or YouTube data for advertising, selling data, creating advertising profiles or training artificial intelligence models. Full details are provided in section Google and YouTube.
3.4. Geolocation information
We do not currently collect or store geolocation information. If we decide to do so in the future, this policy will be updated and your explicit consent will be requested.
Google and YouTube: optional integration
NextBlog uses the YouTube API Services (YouTube API Services) so that you can publish the Shorts you create on the platform to your own channel. This section explains, specifically and separately from the rest of the policy, what happens to your Google and YouTube data.
The integration is optional and remains disabled until you activate it. NextBlog does not receive any data from Google or YouTube until you click “Connect YouTube” and expressly accept Google’s consent screen (OAuth 2.0). You can use the rest of the platform without connecting a channel.
Permissions we request and why
https://www.googleapis.com/auth/youtube.upload— upload the video file you select and confirm to your channel.https://www.googleapis.com/auth/youtube.force-ssl— identify the channel you have authorised, check the processing status of the video that NextBlog has just uploaded and then apply your chosen visibility or scheduled date. The upload permission alone does not allow the latter two operations.
This YouTube integration does not request any other Google permissions. You can view the permissions granted on the NextBlog connection screen and in your Google account.
Google and YouTube data we process
- OAuth credentials: the access token and refresh token (refresh token) issued by Google, their expiry date and the permissions granted. They are stored in encrypted form and used only to perform the actions you request.
- Authorised channel data: its identifier, name, custom URL and channel thumbnail.
- The video you select: the file you upload to NextBlog to publish it as a Short.
- The metadata you choose for that post: title, description, tags, language, category, audience declaration (“made for kids”), visibility (public, unlisted or private), and scheduled date and time.
- The result of that post: the identifier and link of the video created through NextBlog, and its upload, processing or publication status.
What we use this data for
- Upload the Short or video you have selected and confirmed to your channel.
- Check that YouTube has processed it correctly and that it meets the Short format requirements (vertical or square and within the permitted duration).
- Apply the visibility setting or scheduled date you specified.
We do not use Google or YouTube data for any other purpose.
What this YouTube integration does not do
- We do not access your Gmail, Google Drive or Google contacts.
- We do not access, read, modify, download or export any videos already on your channel.
- We do not read, post or moderate comments.
- We do not manage subtitles or text tracks.
- We do not give, remove or view ratings (“likes” or “dislikes”).
- We do not create or modify playlists.
- We do not access YouTube Analytics or reports, or your channel statistics.
- We do not search for or collect content from other channels using your authorisation.
- We do not delete videos from your YouTube channel.
- We do not sell Google or YouTube data or use it for advertising, advertising profiling or training artificial intelligence models.
With your Google authorisation, NextBlog only uses four YouTube Data API v3 methods: channels.list (identify your channel), videos.insert (upload the video), videos.list (check its processing) and videos.update (apply visibility or scheduling).
Limited use of Google data (Limited Use)
NextBlog’s use and transfer of information received from Google APIs comply with the Google API Services User Data Policy, including its Limited Use requirements. Specifically:
- We only use this data to provide and improve the YouTube publishing features that you enable and that are visible in the NextBlog interface.
- We only transfer this data when necessary to provide these features, for security reasons, to comply with applicable law or as part of a merger or acquisition with prior notice and consent.
- We do not use this data for advertising of any kind, sell it or disclose it to data or information brokers.
- No person reads this data unless you give us your express consent for specific cases, it is necessary for security purposes (for example, to investigate abuse), it is required by law, or the data is aggregated and anonymised.
How to disconnect and delete data
- Disconnect the channel from NextBlog: we ask Google to revoke the token and delete the credentials and data received from the API for that connection, including the channel ID, name and image, and references to remote videos. We retain your own text and files as local drafts; pending NextBlog tasks are stopped. Revocation in Google may affect other connections authorised with the same Google account.
- Delete all local YouTube data from the same connection screen: in addition to revoking and deleting the credentials, the connection, drafts, publishing history and any video files stored in NextBlog are deleted.
- Revoke access from Google: you can revoke NextBlog’s access at any time from your Google Account security page at myaccount.google.com/permissions (or at security.google.com/settings/security/permissions).
Important: disconnect the channel or delete local data in NextBlog does not delete videos that have already been published on your YouTube channel. Those videos remain yours, and you must manage or delete them through YouTube Studio or the YouTube app itself.
An upload already in progress may be completed as a private video. Scheduled posts already accepted by YouTube may go ahead without NextBlog: to cancel them or modify those videos, use YouTube Studio.
Applicable Google and YouTube documents
4. Purpose of Data Use
NextBlog may use Personal Data for the following purposes:
- To provide and maintain our Service, including monitoring the use of our Service.
- To manage your account: to manage your registration as a user of the Service. The Personal Data you provide may give you access to different features of the Service that are available to you as a registered user.
- For the performance of a contract: the development, fulfilment and performance of the purchase contract for the products, items or services you have purchased, or of any other contract with Us through the Service.
- To contact you: to email you and display in-platform notices about updates or informational communications relating to the features, products or services you have purchased, including security updates, where necessary or reasonable for their implementation.
- To send you newsletters, updates, recommendations and promotional communications when you have requested or expressly authorised them, or when the legal requirements for existing customers and our own similar services are met, always with an unsubscribe option.
- To manage your requests: To respond to and manage your requests to Us.
- To provide the YouTube integration you activate: identify your authorised channel, upload a Short that you confirm, check its processing status and apply the visibility or scheduling option you select.
- For business transfers: We may use your information to evaluate or carry out a merger, divestiture, restructuring, reorganisation, dissolution or other sale or transfer of some or all of our assets, whether as a going concern or as part of bankruptcy, liquidation or similar proceedings, in which the Personal Data we hold about our users is among the assets transferred.
- For other purposes: We may use your information for other purposes, such as data analysis, identifying usage trends, determining the effectiveness of our promotional campaigns, and evaluating and improving our Service, products, services, marketing and your experience.
4.1. Resources, forms and electronic communications
Requesting a resource, completing a form, asking for a demonstration or subscribing to content may result in one or more emails sent manually or automatically: delivery of materials, access or download links, results or reports, confirmations, replies, reminders or follow-up that form part of your request.
Newsletters, recommendations, updates and promotional follow-up sequences are distinct from messages needed to handle your request. They require your request or express authorisation, except in the limited cases permitted by law for existing customers and similar services. Downloading a resource, sending an enquiry, accepting a privacy policy or accepting cookies does not, by itself, authorise these messages.
The purpose, required data and contact channels must be disclosed before the form is submitted. Promotional consent must be optional, specific and separate from resource delivery or handling the request, without preselected boxes. If a channel other than email is offered, it will only be used within the scope disclosed and requested or authorised.
You can unsubscribe from or object to promotional communications using the unsubscribe link in those messages or by emailing contacto@nextblog.es. Unsubscribing does not prevent emails needed to complete a request or provide an active service, and does not affect the lawfulness of previous processing.
5. Legal Basis for Processing Your Data
The legal basis for processing your data is:
- Performance of a Contract: To process your orders and payments and manage your user account.
- Handling resource and form requests: your consent to receive the requested material or information and, where applicable, taking steps you request before entering into a contract or performing a contract. The specific legal basis depends on the purpose disclosed in each form.
- Your Consent: To send newsletters and marketing communications, use certain non-essential cookies and for other specific purposes for which we have requested your approval. You may withdraw your consent at any time.
- Legitimate Interests: To conduct internal analyses and compile statistics, improve our services and prevent fraud, provided that our legitimate interests do not override your rights and interests.
- Compliance with a legal obligation: for billing, accounting, tax obligations and responding to requests from authorities.
Registration, billing and contact details are required to provide the service and issue invoices: if you do not provide them, we cannot register you or maintain your account. All other data is optional, and not providing it will only limit the relevant functionality.
6. Artificial Intelligence and Automated Decision-Making
NextBlog uses artificial intelligence systems as an essential part of the service. We expressly inform you, in compliance with the General Data Protection Regulation and Regulation (EU) 2024/1689 on Artificial Intelligence:
a) Content generation
The articles, social media posts, scripts, newsletters and emails suggested by the platform are created using third-party artificial intelligence models. The generated content is always a draft subject to your review and approval: nothing is published without your involvement, and you are editorially responsible for what is published. To train the assistant in your style, we only process the texts you provide to us.
b) Interaction with AI systems
When you interact with the platform’s assistant, you are interacting with an artificial intelligence system, not a person. The platform makes this clear in the interface, and you can email the contact address in this policy whenever you would prefer assistance from a person.
c) Profiling and scoring of leads
The platform automatically calculates a score and “temperature” (cold, warm, hot) for leads captured through pages and campaigns, based on interaction data such as email opens, clicks, visits and form responses. This score is used to prioritise sales follow-up.
This score does not produce legal effects or similarly significantly affect you within the meaning of Article 22 of the GDPR: it does not determine access to a service, a price or a contractual decision. In all cases, you may request human intervention, express your point of view and challenge the result by writing to the contact address in this policy.
d) We do not use AI for the following
- We do not perform emotion recognition or biometric categorisation.
- We do not use biometric identification of any kind.
- We do not make automated decisions about recruitment, credit, pricing or access to essential services.
- We do not use your data to train third-party artificial intelligence models or share your content for that purpose.
8. Disclosure of Data to Third Parties
We do not sell or disclose your personal data. We do use providers that act as data processors on our behalf, under a signed data processing agreement and subject to confidentiality obligations. The following providers are involved in the service you use within your account:
- Hosting and infrastructure: provider of the application platform and provider of the managed database where your account and content are stored.
- File storage: Cloudflare R2, for the images and documents you upload or generate.
- Artificial intelligence: OpenAI, to generate text and transcribe the voice notes you record in the assistant, solely for the content you request to be generated.
- Email delivery: MailerSend and our SMTP provider, for emails relating to your account (access, notifications and billing) and for newsletters you schedule to be sent to your subscribers.
- Payments: Stripe, which processes payment data in accordance with its own policy.
In addition, if you choose to connect them from your account, the following services are involved. None of them receive any data until you establish the connection, and you can disconnect them at any time:
- Meeting scheduling: Calendly, if you embed a calendar in your lead capture pages.
- Your email inbox: Google or Microsoft, if you connect your inbox so the platform can detect replies from your contacts.
- Social media: LinkedIn, Meta (Facebook and Instagram), YouTube and TikTok, solely to publish content you approve.
If you connect TikTok, we store the identifier and basic profile data returned by TikTok, the permissions granted and the encrypted OAuth tokens required to maintain the connection. For each submission, we process the video, text, visibility, interaction options, commercial disclosures and publication status. NextBlog only sends them to TikTok after your express authorisation; you can disconnect the account and delete the local connection from Integrations.
8.1. Integration with Google and YouTube
When you connect YouTube, we share with Google and YouTube only the data required for the action you have initiated: OAuth authorisation, the video file and the metadata for the post you confirm. We use YouTube permissions to upload the video to your own channel, check the processing status of the video created in NextBlog and update its visibility or schedule according to your selection.
We do not access, analyse, export or manage your existing videos, comments, ratings or subtitles for purposes unrelated to those actions. We do not delete videos from your channel through NextBlog. Disconnecting revokes and deletes local OAuth tokens; local drafts and history are retained until you explicitly request their deletion or delete your account.
NextBlog’s use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including the applicable Limited Use requirements. The following also apply: Google Privacy Policy and the YouTube Terms of Service.
You can request an up-to-date list of the names and locations of data processors at any time by writing to the contact address in this policy.
8.2. Who can access your account within NextBlog
Access to your account data is limited to those who need it to provide you with the service, all of whom are contractually bound by confidentiality obligations:
- NextBlog administration: may access your account where there are reasonable grounds to suspect an irregularity—breach of the Terms, fraudulent or abusive use, a security incident, a legal request or a substantiated request from a connected platform—and when you ask us to resolve a support issue. Access is limited to what is necessary and is logged internally.
- Authorised partners and sales representatives: if your account is linked to a partner or sales representative who registered it, manages your subscription or provides you with support, that person may access it in delegated mode for those tasks. All delegated access is logged with the identity, date and source.
The full terms are set out in sections 4.1 and 4.2 of the Terms of Service. You can request that the link to a partner be revoked by emailing the contact address in this policy.
We may share or transfer your personal information in connection with, or during negotiations for, any merger, sale of company assets, financing or acquisition of all or part of our business by another company. In such cases, you will be notified in accordance with applicable law.
We may also disclose your personal information if required by law or in response to valid requests from public authorities (for example, a court or government agency).
9. Data Security and Security Breaches
The security of your Personal Data is important to Us. We have implemented appropriate technical and organisational security measures to protect your personal data against unauthorised access, alteration, disclosure or destruction. We use database and server services that have their own safeguards and are designed to ensure information security. However, remember that no method of transmission over the Internet or method of electronic storage is 100% secure. Although we strive to use commercially acceptable means to protect your Personal Data, we cannot guarantee its absolute security.
In the event of a security breach affecting your personal data, NextBlog undertakes to notify the competent authorities and affected users within the time frame and in the manner established by applicable law (General Data Protection Regulation - GDPR). We would also contact cybersecurity experts to investigate the breach, mitigate its effects and prevent future incidents.
10. Data Retention Period
Data from our forms and resources will be retained for as long as needed to handle the request and related actions. Subscription data will be processed while the subscription remains active or until you withdraw consent or object. Data may then be retained with processing restricted for applicable legal periods, together with the minimum information needed to demonstrate authorisations and honour unsubscribe requests.
We retain your personal data only for as long as necessary for the purposes described in this policy. The following retention periods apply:
The general time limits in this table do not extend the retention of data received from Google and YouTube: the specific rules in section 10.3 apply to that data, including when you request its deletion.
| Data type | Retention period |
|---|---|
| Account data and platform content | While the account is active, plus 6 months after closure or cancellation. |
| Access records, logs and diagnostic data | 90 days. |
| Backups | Until they expire and are overwritten in accordance with the infrastructure provider’s retention cycle; exclusively for incident recovery. |
| OAuth credentials for integrations | While the connection remains active. They are deleted when it is disconnected. |
| Video files uploaded for publication | For as long as they are needed for the draft or upload; those associated with an article may be retained for reuse. |
| Accounting and tax records | For the periods required by commercial and tax regulations. |
| Data required to handle claims | Until the limitation period for the corresponding actions expires. |
10.1. What happens when you cancel
Following cancellation, there is a six-month grace period during which the blog remains available and you can export anything you want to keep. Once that period has elapsed, we permanently delete the content, contacts, subscribers, metrics, settings and files associated with the account, along with the endpoints serving the blog. We will notify you by email before the deadline, using the address associated with the account. Details are provided in section 16.1 of the Terms of Service.
The only information retained after deletion is what we must keep to comply with legal obligations —accounting and tax records— or to establish, exercise or defend legal claims.
10.2. Backups
After deletion from active systems, data may remain in isolated backups until it expires and is overwritten in accordance with the infrastructure provider’s retention cycle. These backups are retained exclusively to restore the service in the event of an incident, not for queries or any other use. Before the service is reopened following a restoration, deletions must be reapplied and authorisations checked. This cycle does not extend the specific time limits applicable to Google and YouTube data. Checking backup retention forms part of the operational validation of this integration.
For our current MySQL database, Aiven confirms that it creates one full backup per day, retains two backups and removes deleted data from remote backups and recovery logs within approximately 48 hours during normal service operation. Local transaction logs are retained for no more than three days. This period is not guaranteed if the service is switched off or rotation does not operate correctly: switching it off stops backups from expiring. Before suspending or deleting the service, pending deletions must be completed and verified.
Slow query logs for that database, if enabled, may include values entered in SQL queries and are retained for four days according to the provider; disabling them does not immediately delete previous entries. According to Aiven, the Query Insights store retains normalised queries without literal values or data rows. We review exports and additional log destinations separately to prevent copies from being retained for longer.
10.3. YouTube integration
YouTube OAuth tokens are retained only while the connection remains active and are deleted when you disconnect it, locally delete YouTube data or request deletion of your NextBlog account. Original videos provided by you are not downloaded from YouTube. Those associated with an article may be retained for reuse in other posts; for all others, we attempt to delete the source file once the upload has been validated. A storage issue may delay this deletion. Deleting data from NextBlog does not itself delete a video that already exists on YouTube.
An automated task runs every hour and checks connections daily: it verifies authorisation with Google and updates basic channel data and the status of videos created from NextBlog. Renewing a token is not considered an update to this data. If Google reports that authorisation has been revoked or is no longer valid, we delete the API data associated with that connection. If an update fails, API data caches in the active database expire 25 days after their last update and are deleted during the next hourly sweep. This period allows for up to four days of residual retention by the provider and provides a buffer before the 30-day limit, provided that rotation and maintenance operate correctly. Text and files provided by you are kept separate from data obtained from the API.
Deletion requests are handled from the YouTube connection screen. Credentials and API data are deleted from the active database immediately; any issue deleting your own files is displayed so you can retry.
Before displaying or exporting data from your account, we also check locally whether YouTube data has expired and delete any expired data without making new requests to Google. This additional safeguard does not replace automated maintenance or its monitoring.
An old manual restore remains isolated until its YouTube credentials and caches have been removed. To avoid reintroducing even deletions not recorded in that copy, the quarantine procedure removes all YouTube API data from the restored database without contacting Google or deleting remote videos or the user’s original files. The channels must then be reconnected and local tasks reviewed before they are reactivated.
11. User Rights
As a user, you have the following rights regarding your personal data:
- The right to access your personal data and obtain a copy of the information we hold about you.
- The right to rectify your Personal Data if it is inaccurate or incomplete.
- The right to erasure (the right to be forgotten) of your personal data when it is no longer necessary for the purposes for which it was collected, or when you withdraw your consent and there is no other legal basis for processing it.
- The right to object to our processing of your Personal Data in certain circumstances, including processing for direct marketing purposes.
- The right to request restriction of the processing of your Personal Data in specific circumstances.
- The right to the portability of your Personal Data, meaning the right to receive it in a structured, commonly used and machine-readable format and to transmit it to another data controller.
- The right to withdraw your consent at any time for processing based on that consent, without affecting the lawfulness of processing carried out before its withdrawal.
To exercise any of these rights, email us at contacto@nextblog.es stating which right you wish to exercise. We will respond within one month of receiving your request. This may be extended by a further two months if the request is particularly complex, in which case we will inform you of the reason within the first month. We may ask you to verify your identity if we have reasonable doubts about who is making the request.
You can also delete your account yourself from the privacy section of the platform settings. Deletion removes the associated data except for information we must retain to comply with legal obligations or handle claims, and is completed across all storage media within the backup rotation period specified in section 10.2.
If you are a contact, lead or subscriber of a NextBlog client and wish to exercise your rights regarding that data, you must contact the client who collected it: they are the data controller and we only act on their behalf. If you contact us, we will forward your request to that client so they can handle it.
Furthermore, if you believe that the processing of your personal data infringes data protection regulations, you have the right to lodge a complaint with the Spanish Data Protection Agency (AEPD).
12. International Data Transfers
The main database and application hosting are located in data centres within the European Economic Area (EEA).
However, some of the providers listed in section 8 are established outside the EEA, mainly in the United States, or may process data outside the EEA. This applies to the artificial intelligence provider and the services you voluntarily connect from your account. These transfers are covered by the safeguards set out in Chapter V of the GDPR: an adequacy decision where applicable, or standard contractual clauses approved by the European Commission together with any appropriate supplementary measures.
You can request information about the safeguards applied to each transfer and a copy of them by writing to the contact address in this policy.
14. Minors
NextBlog is a service intended exclusively for businesses, professionals and self-employed individuals, and is not intended for anyone under the age of 18. We do not knowingly collect personal data from minors. If we become aware that we have collected personal information from a minor, we will take the necessary steps to delete it.
15. Changes to this Privacy Policy
We may update this Privacy Policy when the service, providers or applicable regulations change. We will publish the new version on this page and update the effective date shown at the beginning of the document. If the change is material, we will also notify you by email or through a prominent notice within the platform before it takes effect.
We recommend reviewing this policy periodically. Changes take effect from the effective date shown at the beginning.
16. Contact Us
If you have any questions about this Privacy Policy, you can contact us:
- By email: contacto@nextblog.es
- By visiting this page on our website: https://nextblog.es
Related legal documents
Effective from 7 November 2026