Política de Privacidad

Última actualización: 14 de marzo de 2026

Data Controller

• Responsible: AEROSAFE SL
• Trade name: BelongBack
• NIF: B05417399
• Registered address: Calle Preciados, 3, Urbanización Urlisa II, 03599, Altea, Alicante, Spain
• Contact email: info@belongback.com

Purpose of this policy

This Privacy Policy dictates the path that BelongBack uses handling user data when engaging directly with platforms, executing service subscriptions or exchanging initial messages.

BelongBack offers specialized intermediary file management loops targeting items considered lost facing entities composed under airport nets, hoteliers, transit operators or regional authorities spanning Spain and broad border setups.

What data do we process

Depending on the case, we may process the following categories of data:

a) Identifiable core and linkage pieces

Name and surname, e-mail tags, phone indicators, registered country space, spoken interaction formats and related postal destination labels.

b) Structural case and file segments

Missing item descriptives, time and point of absence marks, third connection refs, flight/booking/stay markers alongside particular details involving local entities, item pictures, established messages plus anything needed pushing cases along.

c) Credential parameters mapping legitimacy

Background lines providing basis determining if claimant inherently figures directly tagged owning requested assets. Typically, BelongBack tries circumventing total sweeps over user passport layouts providing alternate valid bounds exist.

d) Economic and invoicing tags

Details covering due charges upon action scope boundaries alongside bill generating layouts, rollback dynamics or pure payment bugs, factoring strict fiscal/management limits.

e) Navigational and internal data marks

IP footprints, system IDs, operational logs tracking navigation bounds upon entering forms or message loops linked backwards.

f) User assist related structures

Incoming notes, claim reports, pure messages attached alongside documents supplied amidst commercial engagement runs.

Data items not commonly solicited

BelongBack systematically opts against tapping sensitive personal strings or details spanning historical criminal backgrounds.

Refrain attaching biometrics, ideological traces, health charts or parallel subjective records minus instances purely driving core structural file dynamics standing onto legitimate valid bases.

Similarly we actively try avoiding mandatory ID/Passport capture scans on default. Certain limits apply when third holding forces mandate hard copy validations over item return.

How we obtain data

We process data that:

1. you directly impart filling up structured form sections, starting commercial ties or building initial chats;
2. is constructed amidst actioning related service stages;
3. stems backwards off operators embedded within file action scopes notably hotel nodes, logistic couriers, transport structures and allied third providers;
4. sources inherently from secondary entities commanding process execution where adequate proxy status bounds remain fully guaranteed tracking source consent paths.

Purposes and legal footing regarding process arrays

BelongBack actively tracks parameters targeting following scope fields supported through these valid boundaries:

a) Direct incoming questions, quote structuring or pre-action layouts

Legal basis: Actioning early measures summoned under end user queries.

b) Pushing contract limits and building engaged solutions

Legal basis: Pure contract performance bounds.

c) Managing specific case structural lines matching target recovery marks

Incorporating case study, defining exact action nodes, initiating external holding chats, funneling data strings and keeping back loops mapping general progress updates.

Legal basis: Contract execution alongside matching pre-setup measures aimed under customer favorings.

d) Economic funnels, billing, fiscal and structural bounds

Legal basis: Answering over rigid regulatory constraints.

e) Fighting fake paths, blocking abusive system setups, filtering fraudulent requests keeping overall platform health checks positive

Legal basis: Proper inherent core platform interests aimed guarding baseline system environments from malicious reach.

f) Checking incidence lines, managing broad claims and deploying defensive stances

Legal basis: Strictly observing compliance over mandates paired alongside executing defensive claims limits.

g) Forwarding potential commercial nodes regarding internal product parallels given valid boundaries

Legal basis: Lawful internal interests amidst legally approved constraints or pure consented tracks. Denial spans always remain unlocked.

h) Managing integrated cookies and similar parallel tech marks

Base jurídica: consentimiento cuando sea exigible, de acuerdo con la Cookie Policy.

Data receivers

Targeted info lines could stand shifted towards limits dictated per action case unto:

1. associated transport stations, hoteliers, security nodes, regional entities or potential current operators acting guarding parameters tracking lost assets;
2. delivery counterparts, logistic partners, material securing forces and customs checks when package moving steps dictate such necessity;
3. banking clusters, transaction processing gates alongside attached legal advisory networks;
4. external software hosting counterparts yielding storage space grids, analytics engines and general communication systems aiding daily limits;
5. legal court venues, active regional security forces and tied authorities amidst hard legal requests demanding defensive stands.

BelongBack does not sell personal data to third parties.

International data movement limits

Given inherently global interaction scales, targeted communications potentially drag personal footprints onto networks sitting outside typical EU/EEA limits.

These movement loops usually branch across two different sets:

a) Paths tracing down global tech allies mapping stable bounds

Whenever foreign partners sit far outside native limits incorporating remote access points, those shifts build directly relying on approved EU Commission adequacy decisions paired alongside standard binding contractual clauses and matching complementary layers.

b) Crucial transfers mandated upon filing explicit requests

Should resolving particular claims unavoidably require communicating parameters towards out-of-boundary entities (e.g. oversea hotels or terminal checks), minimal data amounts are forwarded strictly aligning with immediate operational boundaries to fully close out tasks.

Under said assumptions, the communication remains heavily filtered carrying exclusively proportionate amounts discarding excess bulk information via strict minimization criteria.

Certain target nations stand devoid from validated EU backing markers therefore lacking standard protection equivalence. Accordingly BelongBack acts applying rigid proportional rules limiting parameters sent targeting exact required actions.

Si deseas más información sobre las garantías o mecanismos aplicables a una transferencia concreta, puedes solicitarla en info@belongback.com.

Data storing and retention timelines

Information traces rest actively logged mirroring initial collection targets extending afterwards keeping compliance with subsequent fiscal, legal or parallel administrative bounds limiting full release actions.

In general terms:

1. file details will be stored as long as said case continues active plus subsequent required timespans managing related issues, formal claims and attaching liabilities;
2. contractual, checkout and billing inputs stand saved bound strictly over legal mandatory ranges;
3. information strings fueling commercial feeds keep active until withdrawing source consensus or formally rejecting parallel treatments;
4. technical tags alongside system logs are kept for logically sound extents guarding platform continuity, audit tracking, and fraud prevention boundaries.

Where deemed correct, data strings fall under encrypted locks remaining purely available targeting specific authorities or active court bounds mirroring mandatory time frames.

Mandatory and optional nature of provided data

Data items mapped as strictly necessary within form blocks or contract cycles prove essential solving end user requests or securing operational service. Lacking said data might result in failing fully tracking files, closing binding setups or simply continuing management actions.

Accuracy and timely updates regarding information

End users personally guarantee all transmitted inputs portray accurate, true and updated points. Any shifts touching base information strings are expected to promptly reach our channels.

Should third-party tags be relayed over to us, users guarantee maintaining adequate standing doing so, assuring parallelly those subjects were previously briefed covering these exact policies.

Automated system decisions

Generally speaking, BelongBack avoids enforcing binding decisions tied uniquely towards automated algorithms prone to triggering specific legal repercussions or significantly swaying individual statuses.

Assuming future scenarios demanding such automated deployments, specific notifications tracking normative boundaries will be clearly broadcasted.

Rights attached to involved individuals

You may exert, when rightfully matching, following standing rights:

1. base access over your personal inputs;
2. straight rectification touching incorrect or partial fields;
3. full suppression eliminating target data if legally possible;
4. stating opposition blocking process bounds traversing certain domains;
5. requesting tight constraints mapping process limits;
6. demanding external portability regarding data strings subject to legal backing;
7. rolling back previous given consensus tied towards approved systems, without legally voiding actions done beforehand;
8. File a claim with the Spanish Data Protection Agency (www.aepd.es) if you consider that your rights have been violated.

Puedes ejercer tus derechos enviando una solicitud a info@belongback.com, indicando el derecho que deseas ejercitar y aportando la información necesaria para verificar tu identidad.

Information shielding systems

BelongBack enacts tailored technical and organizational boundaries aimed shielding private marks facing unauthorized extraction, modifications, absolute losses or wrongful chats, consistently adapting given item parameters alongside latest process thresholds.

Nevertheless, not a single network or transit method stays perfectly impenetrable, hence total absolute security levels cannot be fully stated.

Underage subjects

BelongBack arrays specifically exclude individuals ranking under 18 years. We firmly avoid grabbing underage tags escaping rightful legitimate bases. Encountering data traces linked towards minors skipping validations entails swift suppression and blocking limits.

Links connecting third entities

Certain sections might branch outwards targeting third party platforms or arrays. BelongBack stays decoupled regarding their bespoke internal privacy policies or pure behaviors. Checking local external regulations remains heavily advised before dropping off sensitive points.

Changes touching privacy policy lines

BelongBack reserves tweaking limits tracing Privacy parameters following legal shifts, technical variations or mere service evolutions. The active standing version matches exclusively what is presently shown publicly over platform boundaries.

Contact Us

Direct doubts hovering alongside Privacy guidelines or spanning broad data treatment constraints can be dispatched reaching out to:

info@belongback.com