Centro privacy MIRA

MIRA Privacy Center

Shared privacy notice for MIRA applications

Version 2026-11-21-business-30-plus-5-v1 · ID 64 · 2026-11-21 06:16:34 UTC

Shared privacy notice for MIRA applications

This notice covers accounts, access, trials, subscriptions, support and use of Business Italia, Business International, Lighting Planner 2D and Lighting Planner 2D + 3D at www.miravisualart.com. Each application’s notice explains its particular content and controls. The website privacy notice and Cookie Policy also apply to purchases and browsing.

Who handles the information

Anila Resuli, trading as MIRA Visual Art, Via Cesare Battisti 37, 25017 Lonato del Garda (BS), Italy, VAT number 04141010985, is controller for processing relating to MIRA’s own relationship with users. For privacy questions and rights requests, contact info@miravisualart.com.

A professional or organisation entering its clients’, staff members’ or suppliers’ information normally determines the purposes and means of that processing. MIRA handles such content on its behalf under the DPA and documented instructions. This notice does not replace the information that the professional must provide to its own data subjects. A user’s potentially solely personal or household use does not exempt MIRA from the obligations applicable to its own processing.

Information involved

We handle account identifiers and contact details, email addresses, relevant business information, access verification, trial and plan details, subscription status, order and billing information, support requests and records of agreements and preferences. Access can use an account or, for the available guest trial, email and a code. Technical records can concern authentication, security and errors.

Depending on the functions used, content entrusted to the apps includes contacts, appointments, quotes, financial and tax information, notes, documents and messages, or lighting configurations, set names and notes. Integration credentials and tokens enable authorised connections. Do not enter health, other special category or criminal offence data into the standard service: a specific agreement and suitable safeguards must first be arranged with MIRA. Free-text notes and transaction descriptions can also reveal such information.

Purposes and legal bases

MIRA purposeLegal basis
Creating accounts, verifying requested access or a trial, supplying the plan and support to the individual entering the contractContract or requested precontractual steps, GDPR Article 6(1)(b)
Managing contacts acting for a customer organisationLegitimate interest in managing that relationship, Article 6(1)(f)
Applicable administrative and tax obligationsLegal obligation, Article 6(1)(c)
Security, abuse prevention and legal claimsLegitimate interest in protecting the service and defending rights, Article 6(1)(f), with an assessment of necessity and balancing
Optional measurement using browser identifiers and activity unnecessary to provide the serviceConsent where required, separately from strictly operational processing; further details in the Cookie Policy and relevant preferences
MIRA newsletters and promotions requested by the userSeparate optional consent, Article 6(1)(a), unless a specific legal exception applies

Acknowledging this notice, entering the DPA and accepting terms do not constitute marketing or statistics consent. Professional customers’ entrusted content is handled under the DPA: the table above concerns MIRA’s own purposes.

Access records, events and statistics

Application records can associate an account or verified trial with the app opened, first and last access, opening counts and the type and time of operations such as starting a set, saving to the cloud or device and authorising a PDF export. Counting an operation does not require copying the set’s content into the event record. Administrators can view trial and usage reports; optional activity measurement has controls separate from operational data.

When enabled, access notifications to MIRA can include the user’s email, app, access method and time. Delivered mailbox copies are separate records. The Planner 2D guest trial uses email verification and also provides an access notification to the operator.

On the website, MIRA Site Insights in local mode sends the page, source category and signature to the site without generating persistent visitor identifiers or writing cookies or local storage in its own JavaScript. MIRA Website Insights is a separate component: it requires an explicit statistics preference and uses random browser and session identifiers; it records the page, day, source and device category. Its device identifier lasts for up to 180 days and the component provides for received records to be pruned after 180 days. Cookies, other trackers and external content are covered by the Cookie Policy; hosting logs remain separate.

The Business apps also keep a prior trial activation reference based on a SHA256 fingerprint of the normalised email, associated with the owner and activation date. This is pseudonymous, not anonymous, separate from statistics, and can remain after account deletion. Requests concerning it are assessed separately against its abuse-prevention purpose; it does not create a general exemption from individual rights.

Recipients and connected services

People assigned administrative, technical and support tasks can access information within their responsibilities. Recipient categories include hosting infrastructure, email and communication delivery, technical support, administrative advisers and payment providers relating to MIRA’s customer relationship. Authorities receive information where required by law. Each recipient’s role follows its service and applicable agreement.

The website uses Aruba S.p.A.’s Hosting Gestito Smart per WordPress. Aruba states that its hosting is provided in its Italian data centres. The provider schedule distinguishes MIRA’s infrastructure providers from integrations configured directly by customers. An available Google, WhatsApp or SMTP feature does not mean that every user has enabled it.

The location of hosting alone does not describe every connected service’s countries. An external recipient can handle data outside the European Economic Area according to its service and agreement. To obtain information about the recipient and country involved in your connection, applicable safeguards and how to obtain a copy, email info@miravisualart.com identifying the feature concerned. The DPA and selection of an integration do not automatically make a new transfer lawful.

Retention, export and erasure

The service retention table distinguishes accounts, working records, access summaries, agreement and abuse-prevention evidence, support, logs and communications. It specifies starting points, periods and exceptions. Professional customers’ content is also subject to the controller’s instructions and the DPA’s return or deletion provisions.

Application pruning has different periods: 365 days from the event for detailed activity history; 90 days from expiry for account-linked Planner trial summaries; 90 days from starting for Planner 2D guest trials, or one day after the last code request where the trial was never started. Scheduled operations require WordPress scheduling to run and do not automatically cover every other record.

The Aruba panel shows complete daily automatic backups for the last seven days. This period concerns automatic hosting copies, rather than all service data. Manual, downloaded or separately stored copies require separate handling. Application controls do not immediately remove information from existing automatic copies.

For Business Italia and Business International version 1.11.0 or later, the trial lasts 30 days. When valid trial/subscription access ends, viewing and self-service export stop immediately. Without reactivation, the inaccessible workspace and its internal copies are automatically erased after 5 days (120 hours), with in-app/email notices and a final entitlement/result check. The account, orders, legal evidence and external copies follow their separate rules. Privacy/return requests remain available without a paid plan. The dedicated Business expiry and erasure policy below gives the complete rules.

Information protection

The Business apps use owner-specific authentication and authorisation checks and require HTTPS for production APIs. Integration tokens and credentials and internal copies use application-level encryption; this does not mean that every contact and transaction record is fully encrypted or inaccessible to infrastructure administrators. The two-step verification confirmed in the provider panel concerns the Aruba account. Business interface support uses a temporary, revocable authorisation; technical hosting and database access is separate. Service measures are described in DPA Schedule B.

Rights, contact and complaints

You can request access, rectification, erasure and restriction; where applicable you can obtain portability and object to processing based on legitimate interests. You can always object to direct marketing and withdraw consent without affecting earlier lawful processing. Email info@miravisualart.com or use the available Privacy Center functions. We verify identity proportionately and respond without undue delay, normally within one month; permitted extensions are communicated with reasons. You may complain to the Italian supervisory authority, www.garanteprivacy.it, or another competent authority.

For requests about content entered by a professional, identify the relevant controller: MIRA assists that controller under the DPA rather than replacing its decisions. Information needed to verify access and supply the service must be available to fulfil that request; optional choices remain separate.

The apps automatically apply technical rules concerning plan expiry, quotas and permissions. You can ask MIRA to examine questions or disputes about access. The displayed document version and date identify the applicable text; material changes are communicated in a way consistent with their impact.

Retention and service closure

The periods below form the service plan to be adopted with this version. Code-based periods require working scheduled tasks; other periods require a corresponding operating procedure. Publishing this text alone does not start deletion. Exceptions for duties or disputes cover only necessary, separated records with a documented reason.

CategoryPeriod and starting point
Account and profileFor the active relationship. Where there are no current subscriptions, orders or unresolved cases, close after 24 months without access, with 30 days’ notice. Only records required for statutory duties or disputes are retained separately.
Business Italia / Business International archives30-day trial; access blocked at effective expiry; automatic workspace/internal-copy erasure after 5 days without reactivation. Existing expired archives receive a notified new five-day transition. See the dedicated Business expiry and erasure policy.
Planner plans after definitive service closureThe Planner-specific 180-day return window after communicated definitive closure and 30/7-day notices remains separate. This is an operating procedure, not a Business retention exception.
Client-requested erasureAct without undue delay, with a contractual target of 30 days after identity and scope verification. Rights responses remain subject to one month from receipt and any permitted extension: verification does not restart that period. Exceptions and residual copies are documented.
Planner 2D guest trialThe component schedules cleanup 90 days after trial start. A code request never followed by a trial start is selected one day after the last request. Cleanup uses scheduled WordPress batches.
Account-linked Planner trial summariesScheduled cleanup 90 days after trial expiry, separate from erasure of plans, orders and accounts.
Detailed app activity historyThe Insights component schedules deletion of events older than 365 days. Business workspace erasure triggers earlier removal of the relevant app/account records under the 30 + 5 policy. Partial cleanup requires intervention. Planner records follow their separate rules.
Identifiable Business access summaries and countersRemoved for this app/account as part of verified workspace erasure where the verified cleanup integration is available. Partial outcomes require intervention. Minimal legal/abuse-prevention/erasure evidence is separate.
MIRA Website InsightsThe reviewed component uses random browser identifiers for up to 180 days and a 180-day database visit window; browser sessions expire after 30 minutes of inactivity. Server cleanup depends on scheduled execution.
MIRA Site Insights aggregate statisticsConfigure a 180-day period for this policy. Summaries made effectively anonymous may be kept separately without a reasonable way to identify visitors. Other trackers follow the specific periods in their inventory.
Ordinary security and audit logsFor logs under MIRA’s control, 90 days after the event. Logs a provider must retain independently under applicable duties follow that provider’s documented rules and are not erased by this plugin. Evidence specifically needed for an incident or dispute is separated and kept until the case ends and the applicable claims period, with documented review.
Pseudonymous prior Business trial record24 months after trial activation. An email fingerprint is not anonymous. Retention and objections or erasure requests are handled separately from ordinary work archives.
Agreement evidence, preferences and rights requestsAgreement evidence: during the relationship and 10 years after closure, restricted to evidence and related claims. Rights requests: 24 months after case closure. Excess identity documents are removed earlier. Disputes are subject to specifically documented preservation.
Support, tickets and related email24 months after the request closes. Unnecessary attachments and excess copies are removed earlier; evidence for contracts or disputes is separated under its own retention rule.
Files for personalised products90 days after final delivery, unless a separate documented request supports a new order or specific dispute evidence must be kept. Promotional reuse requires a separate lawful basis.
Newsletter and marketing objectionsSubscription until withdrawal and no later than 24 months after the last confirmed consent unless renewed and recorded. Minimal objection evidence is kept for 24 months to prevent improper reimports. Every new marketing message still requires a valid lawful basis after that period.
MIRA accounting and tax documentsFor documents subject to the duty, 10 years from the applicable starting point, including the last entry under Italian Civil Code Article 2220; additional statutory or assessment periods are handled separately. This does not apply to every item of app content.
Aruba automatic backupsThe Managed Smart Hosting for WordPress service shows 7 complete daily copies covering the last 7 days. Data erased from live archives may remain until backup rotation. The 7-day period applies to these automatic copies.
Manual, downloaded, additional and staging copiesErasure plan within 30 days after creation unless separately justified for an incident or dispute. Aruba on-demand copies do not expire automatically. Test environments use synthetic or minimised data; prior erasures are reapplied before restored records return to ordinary use.

Business Italia and Business International: access, expiry and erasure

This policy applies separately to each hosted Business workspace with version 1.11.0 or later. It does not change the Lighting Planners’ retention rules. An active subscription for one application does not grant access to the other. A valid 30-day trial permits access without a paid subscription during those 30 days.

30 days of trial, then 5 days before erasure

StageAccess and data
Valid trial or active subscriptionThe workspace is available according to its plan. The trial lasts 30 days from verified activation. Export records you need while access is valid.
Effective expiry without another valid entitlementWorkspace access stops immediately, including viewing, searching and self-service export. Email and WhatsApp sending and scheduled workspace backups stop. The account can still open the renewal/status screen and privacy/rights channels.
Next 5 days (120 hours)The archive remains inaccessible while the user can activate or reactivate the relevant subscription. The displayed notice gives the erasure date and time. In the ordinary trial case, the deadline is 35 days after trial activation.
After the 5-day deadlineIf no valid entitlement has been restored, the system erases the application’s live archive, its internal snapshots and local integration credentials, then verifies the result. Erased records cannot be recovered by purchasing a plan later.

Cancelling renewal while access remains valid for an already paid period does not start the five days early: the period starts when access actually ends. A valid relevant subscription restored before the deadline cancels the scheduled erasure. A subscription to the other Business app does not preserve this workspace.

Accounts already expired when this policy is introduced

Existing expired archives receive a new five-day transition window after the rollout notice has been accepted for sending. They are not erased retroactively on installation. A pre-existing archive with no subscription or trial follows the same notified five-day process. An account with no workspace data is not permission to insert records without a valid trial or subscription.

In-app and email notices

The service explains the policy at trial activation, warns approximately three days and one day before expiry, announces the access block and the exact five-day deadline, sends a final warning about 24 hours before erasure and confirms verified erasure. The locked status screen shows the applicable deadline. These are service messages, separate from marketing consent. Acceptance for sending is not proof that an email reached the inbox; check spam and keep the account email current.

What is erased and what is separate

Erasure covers the relevant Business workspace’s movements, profiles, contacts, appointments, CRM/settings records, local application logs, internal backup snapshots and schedules, email/WhatsApp queues and local configurations, and local Google connection tokens. Related named usage statistics are removed through the available verified cleanup integration; incomplete cleanup is flagged for handling.

The WordPress/customer account, WooCommerce orders and subscription records, immutable agreement records, minimal trial abuse-prevention references and necessary erasure/notice evidence are separate. This process does not automatically close the account or erase data that must be retained for a documented legal duty or legal claim. Such records must be limited to the necessary purpose and period.

Hosting backups are separate from the application’s internal snapshots. Existing external backups, downloaded exports, messages already delivered, recipients’ mailboxes and events already held by Google or Meta are not remotely erased by this operation. Their deletion or expiry follows the applicable provider/backup procedure. A restoration must reapply completed erasures before restored archives become available.

Rights and professional customers’ instructions

You can request access, return, rectification, restriction or erasure through the MIRA Privacy Center or info@miravisualart.com without buying a subscription. This does not reopen the workspace. Professional controllers can give return/deletion instructions under the DPA. Make return requests before erasure: a request is reviewed by MIRA and does not itself pause the scheduled procedure. MIRA must assess and handle any applicable preservation or return instruction separately; records already irreversibly erased cannot be returned.

Scheduled execution and verification

The five-day deadline is fixed. Cleanup and email processing run through WordPress scheduled jobs; a working server cron is needed for prompt execution even without visitors. A delayed job does not extend workspace access. Subscription status is rechecked before destruction; an uncertain status or incomplete deletion is flagged and retried rather than reported as completed. No statement on this page certifies deletion of external copies.

SHA-256 72a7211d7a9a132e179b5029bede9df2d047bfd4929ac140519a2d7bf877ff0b

Data processing agreement for MIRA applications

Version 2026-11-21-business-30-plus-5-v1 · ID 66 · 2026-11-21 06:16:34 UTC

Data processing agreement for MIRA applications

Version 2026-11-20-review1. This agreement takes effect for the business customer upon its documented conclusion in the MIRA Privacy Center or through an equivalent written agreement. The confirmation date and accepted version are recorded separately.

1. Parties, subject matter and precedence

The professional or organisation identified in the service relationship and agreement confirmation, the Controller, appoints Anila Resuli, trading as MIRA Visual Art, Via Cesare Battisti 37, 25017 Lonato del Garda (BS), Italy, VAT number 04141010985, email info@miravisualart.com, MIRA or the Processor, under Article 28 of Regulation (EU) 2016/679. Anyone concluding this agreement for an organisation identifies themselves and confirms their authority to represent it.

Processing concerns content entrusted through Business Italia, Business International, Lighting Planner 2D and Lighting Planner 2D + 3D, limited to activated applications and functions actually used, including a free trial. Annex A describes the subject matter, nature, purposes, data subjects, data and duration. Annexes A, B and C form an integral part of this agreement.

This DPA supplements the service contract and takes precedence over incompatible terms concerning protection of entrusted data. It does not restrict mandatory legal obligations and is not a set of European Commission standard contractual clauses for international transfers. Information processed by MIRA as controller for accounts, purchases, billing, protection of its service relationship, support and its own contractual records is governed by MIRA’s privacy notice and separate legal bases. Solely personal or household use does not require a fictitious business-controller declaration and is addressed separately.

2. Documented instructions and limits of use

The Controller determines the purposes, categories of content, data subjects, recipients and legal bases for processing within its responsibility. It ensures lawful entry of data, appropriate notices to its data subjects and the permissions required for communications and integrations. It remains responsible for access under its control and for using functions consistently with its instructions.

Initial instructions consist of this agreement, its annexes, requested functions and documented service settings. Further instructions may be given through an authenticated channel or a communication whose source is verified. MIRA processes data only to provide the agreed service and support, including instructed disclosures and international transfers. It does not use entrusted content for its own promotions, sale of lists, model training or purposes unrelated to the service.

MIRA promptly informs the Controller if it considers an instruction to infringe data protection law and suspends the disputed operation while it is clarified. If applicable Union or Member State law requires different processing, MIRA informs the Controller before processing, unless that law prohibits the information on important grounds of public interest. Authority requests are verified, limited to what is required and documented to the extent permitted; requests from third-country authorities are also assessed under Article 48 GDPR.

3. Confidentiality and authorised persons

MIRA limits access to people who need it for assigned tasks, authorises and instructs them, and ensures that they are bound by confidentiality or an appropriate statutory duty. Access is reviewed and withdrawn when no longer necessary. Application-interface support and technical administration of WordPress, hosting and databases are separate scopes; an interface restriction does not make a database technically inaccessible to its server administrators.

4. Security and continuity

Throughout the service, MIRA implements and maintains technical and organisational measures appropriate to risk under Article 32 GDPR, taking account of the state of the art, costs, nature, scope, context and purposes of processing. Annex B specifies agreed measures and relevant technical limits. Its organisational duties are commitments to be implemented in service delivery, rather than assertions of historical tests or MIRA certification.

MIRA documents relevant controls, periodically assesses the effectiveness of measures, and manages updates and vulnerabilities according to risk. Technical changes must not reduce the agreed level of protection without appropriate replacement measures. No guaranteed maximum recovery time or maximum data-loss interval is agreed. Controller exports do not replace MIRA’s security and continuity obligations.

5. Subprocessors and changes

The Controller gives general written authorisation for the subprocessors identified by name in Annex C and in the Providers and subprocessors schedule, in the version made available and recorded together with this agreement. No unknown recipient is authorised by a generic formula or merely because an integration exists in the software. Before concluding the agreement, MIRA checks that the list reflects actual processing and providers.

MIRA imposes substantially equivalent data protection obligations on each subprocessor by written contract, including sufficient guarantees for appropriate measures, and remains fully liable to the Controller for the subprocessor’s performance of those obligations.

For additions or replacements, MIRA informs the registered service contact of identity, activities, affected data, countries and safeguards at least 30 days before use for the Controller’s data. This period is a contractual choice in this agreement. The Controller may raise a reasoned data protection objection during that period. The parties seek a documented solution, such as an alternative or disabling the affected function. The disputed change is not applied to the Controller’s data before the objection is resolved; if no solution is possible, the Controller may end the affected service component with return or deletion under this agreement. Urgency does not authorise new subprocessors outside the applicable authorisation.

6. Integrations and international transfers

Services contracted directly by the Controller, such as its own SMTP, messaging or calendar service, must be distinguished from providers engaged by MIRA. Configuring an integration documents an instruction to transmit within the displayed scope, but does not automatically make Meta, Google or another provider a MIRA subprocessor. The role follows the actual contract, account and data flow. If MIRA instead engages a service to process entrusted content, the subprocessor requirements apply.

The known hosting infrastructure is in Italy, as set out in Annex C. This does not mean that every external service, message recipient or remote access remains in Italy. Before a transfer outside the European Economic Area, MIRA ensures documented instructions, verifies recipients and countries, and implements an applicable Chapter V GDPR transfer mechanism, including any necessary assessments and supplementary measures. Selecting an integration does not replace those checks. MIRA provides the Controller with relevant information and, where applicable, copies of safeguards, subject to necessary protection of third-party data and confidential information.

7. Data subject requests and assistance

MIRA forwards requests received about entrusted content to the Controller without undue delay and does not independently determine their merits unless required by law. Taking account of the nature of processing and available information, it assists through appropriate technical and organisational measures with access, rectification, erasure, restriction, objection and portability in time for the Controller’s response.

The parties proportionately verify identity, competence, scope and third-party rights. Deleting one record is not equated with removing every reference, message already sent or copy. The coordination contact is info@miravisualart.com; requests submitted through the Privacy Center are verified and do not by themselves trigger archive deletion.

8. Breaches and assistance under Articles 32–36

Once it becomes aware of a personal data breach affecting entrusted data, MIRA informs the Controller without undue delay through the registered service contact. MIRA’s contact for incidents and data protection is info@miravisualart.com. The initial notice does not await completion of the investigation and contains available information about the event’s nature, categories and approximate numbers of affected data subjects and records, likely consequences, measures taken or proposed, and a contact point. Missing information is provided progressively without further undue delay.

MIRA contains the incident, preserves relevant evidence and cooperates on risk assessment, supervisory-authority notification and communication to data subjects. It assists the Controller with Articles 32–36 GDPR, including impact assessments and prior consultations, taking account of the nature of processing and information available. The Controller’s responsibility for its own duties and deadlines is not transferred to MIRA.

9. Information, audits and responsibility

MIRA makes available the information necessary to demonstrate compliance with this agreement and allows and contributes to audits, including inspections, conducted by the Controller or its appointed auditor. The parties agree arrangements proportionate to the purpose, protecting other customers’ data, security and relevant confidential information. Organisational arrangements must not undermine the audit right or obstruct the authority’s powers. Additional activities and costs are agreed without making statutory compliance impossible.

MIRA informs the Controller of material deficiencies established and relevant corrective action. Commercial liability terms do not prejudice data subjects’ rights or the mandatory allocation of liability under the GDPR.

10. Duration, return and deletion

For Business Italia and Business International version 1.11.0 or later, the trial lasts 30 days. When valid trial/subscription access ends, viewing and self-service export stop immediately. Without reactivation, the inaccessible workspace and its internal copies are automatically erased after 5 days (120 hours), with in-app/email notices and a final entitlement/result check. The account, orders, legal evidence and external copies follow their separate rules. Privacy/return requests remain available without a paid plan. The dedicated Business expiry and erasure policy below gives the complete rules.

On final termination of the service relationship, notified to the Controller, the Controller chooses between return in a usable format followed by deletion and direct deletion, unless legal retention is required. Unless it chooses earlier deletion, the contractual return window is 180 days from final termination. MIRA gives notice of impending deletion at least 30 days and 7 days before that deadline through the service contact. Business return can use the export function; other data is returned through available tools or verified assistance. An instruction for earlier deletion takes precedence over the remaining window.

Following a verified deletion instruction, MIRA acts without undue delay and completes removal of the affected operational data within 30 days of proportionate verification of identity and scope, unless retention is required by law. In that case it explains the basis, categories and applicable duration, restricts access and prohibits further uses. Verification is not used to arbitrarily delay handling. This operational deletion period does not change the response deadlines for data subject rights: without undue delay and normally within one month of receipt, subject to legally permitted extensions notified within the statutory timeframe.

Complete automatic hosting backups are made daily and retained on a rolling basis for the last seven days. Data deleted from the operational archive can therefore remain in existing automatic copies until rotation. Manual on-demand backups, downloaded copies and other copies under MIRA’s control do not expire through that rotation: this agreement requires MIRA to identify and delete them within 30 days after deletion of the affected operational data, unless a documented legal retention requirement applies. This is an organisational commitment to be implemented during service delivery; it is neither an automatic plugin function nor an expiry imposed by Aruba.

Residual copies remain protected, limited to recovery and excluded from ordinary service use. Following recovery, MIRA reapplies previously received deletion instructions before putting the affected data back into use. It documents completion and legal exceptions. WordPress accounts, orders and MIRA’s own documentation have separate procedures and purposes; they do not justify indiscriminate retention of entrusted content. Data already held by services contracted directly by the Controller and copies downloaded by the Controller remain within its control, without prejudice to MIRA’s assistance duties.

https://www.miravisualart.com/?page_id=90538&mpc_lang=en#mpc-retention

Annex A — Entrusted processing

ElementScope
Services and subject matterStorage and processing of content in activated Business Italia, Business International, Lighting Planner 2D and Lighting Planner 2D + 3D applications, including trial and closure.
Data subjectsThe Controller’s customers, prospective customers, contacts, collaborators and suppliers; people mentioned in contacts, appointments, notes and documents. Minors only for relevant ordinary data lawfully entered.
Business dataOrdinary identification, contact and tax data; profiles and preferences; appointments, services and quotes; transactions, revenue, expenses, amounts, descriptions, counterparties and documents; messages, templates, recipient permissions and objections; integration settings and references.
Planner dataSaved plans and sets, names and notes potentially relating to people, operational configurations and owner or trial identifiers. This DPA applies insofar as such content contains personal data processed for the Controller.
Operations and natureCollection through requested entry or import, recording, organisation, storage, authorised consultation, updating, search, export, deletion, internal copies, backup and recovery; transmission to requested integrations within the agreed scope.
PurposesProviding selected functions and support for the Controller according to its instructions; no independent MIRA promotional purpose for entrusted content.
Frequency and durationAccording to Controller use and instructions, throughout processing and closure as governed by section 10.
Special-category and criminal-offence dataExcluded from the standard service. Admission requires a prior specific agreement on purposes, legal bases, data, instructions and safeguards. Free-text fields, descriptions and documents must not be used to bypass this restriction.

Annex B — Service technical and organisational measures

The specifications below distinguish application controls from operational duties MIRA undertakes for service delivery. Availability of a function does not establish every setting of the installation or external services. MIRA verifies and documents relevant configurations before relying on a measure.

AreaMeasure and contractual limit
Separation and authorisationReviewed Business operations associate and filter content using the authenticated owner’s identifier; cloud plans are associated with the relevant account or trial. MIRA checks read, edit, export and deletion paths with separate accounts after relevant changes and limits privileged access.
Authentication and transportBusiness APIs require authentication and a WordPress nonce and provide for HTTPS in production. Application responses carry private-cache and non-storage instructions. MIRA maintains HTTPS and checks that caches and proxies do not expose restricted content. Two-step verification is active for the Aruba account; this is not an assertion of MFA on WordPress accounts.
Secrets and encryptionIntegration tokens and credentials in the reviewed modules and internal Business copies use application-level AES-256-GCM encryption with keys derived from WordPress secrets. Full application-level encryption of address books and transactions or end-to-end encryption is not asserted. MIRA limits key access, protects keys and preserves recovery requirements without disclosing secrets through reports or support.
Support and administrationThe Business interface provides temporary, revocable owner authorisation lasting 24 hours. This is the permission duration, not a guaranteed support-response time. MIRA verifies the source and necessity of requests and separately governs technical access to WordPress, hosting and databases.
Records and confidentialityModules provide records of relevant authorisations and operations. MIRA limits access and retention according to defined purposes, avoids unnecessary content and ensures instructions and confidentiality for authorised persons.
Copies and continuityInternal Business copies are encrypted but remain in the same database; they are not independent hosting backups. Aruba’s Hosting Gestito Smart per WordPress plan provides seven daily complete automatic backups on rotation. MIRA checks availability and scope of actual copies, documents recovery checks it performs and assesses additional copies according to risk. Completed recovery tests or guaranteed RTO/RPO values are not asserted.
Updates and incidentsMIRA inventories relevant components, follows security notices, applies updates and mitigations according to urgency and risk, checks outcomes and maintains a process for incident reporting, containment, evidence and communications. Custom-plugin updates and correct application configuration must be governed even where hosting manages other updates.
Export and deletionBusiness applications provide archive export and deletion with outcome checks, including internal copies and module data within the command’s scope; partial outcomes require handling. In the Planners, plan deletion removes content while identifiers or counters may remain for plan administration. MIRA also checks relevant records and affected copies and applies section 10’s deadlines and procedure. Archive, account and order deletion are separate.

Annex C — Subprocessors and integrations

EntityFunction, data, country and terms
Aruba S.p.A.Via San Clemente 53, 24036 Ponte San Pietro (BG), Italy; VAT number 01573850516. Hosting Gestito Smart per WordPress for the MIRA website: infrastructure for application databases and files and service recovery copies, within requested delivery. Aruba states that hosting is provided in its Italian data centres. It acts as subprocessor for professional content entrusted to MIRA; appointment and further subprocessors follow the applicable hosting contract and Article 28 obligations. Current public terms include an appointment in Article 23; this does not replace checking the version applicable to the relationship.

Aruba is the subprocessor identified by name in the information available for this agreement. The Providers and subprocessors schedule in the Privacy Center, in the version recorded with confirmation, must complete any additional service actually engaged by MIRA before it processes the Controller’s content. This table does not provide blanket authorisation for SMTP, payment gateways, consultants, messaging, calendars or other unidentified recipients. Purchase data processed independently by MIRA and services contracted directly by the Controller are separate; their role follows the actual function.

MIRA obtains information about relevant further providers and countries from its providers, imposes necessary obligations and manages changes under section 5. Contact for instructions, requests, audits and incidents: info@miravisualart.com.

Retention and service closure

The periods below form the service plan to be adopted with this version. Code-based periods require working scheduled tasks; other periods require a corresponding operating procedure. Publishing this text alone does not start deletion. Exceptions for duties or disputes cover only necessary, separated records with a documented reason.

CategoryPeriod and starting point
Account and profileFor the active relationship. Where there are no current subscriptions, orders or unresolved cases, close after 24 months without access, with 30 days’ notice. Only records required for statutory duties or disputes are retained separately.
Business Italia / Business International archives30-day trial; access blocked at effective expiry; automatic workspace/internal-copy erasure after 5 days without reactivation. Existing expired archives receive a notified new five-day transition. See the dedicated Business expiry and erasure policy.
Planner plans after definitive service closureThe Planner-specific 180-day return window after communicated definitive closure and 30/7-day notices remains separate. This is an operating procedure, not a Business retention exception.
Client-requested erasureAct without undue delay, with a contractual target of 30 days after identity and scope verification. Rights responses remain subject to one month from receipt and any permitted extension: verification does not restart that period. Exceptions and residual copies are documented.
Planner 2D guest trialThe component schedules cleanup 90 days after trial start. A code request never followed by a trial start is selected one day after the last request. Cleanup uses scheduled WordPress batches.
Account-linked Planner trial summariesScheduled cleanup 90 days after trial expiry, separate from erasure of plans, orders and accounts.
Detailed app activity historyThe Insights component schedules deletion of events older than 365 days. Business workspace erasure triggers earlier removal of the relevant app/account records under the 30 + 5 policy. Partial cleanup requires intervention. Planner records follow their separate rules.
Identifiable Business access summaries and countersRemoved for this app/account as part of verified workspace erasure where the verified cleanup integration is available. Partial outcomes require intervention. Minimal legal/abuse-prevention/erasure evidence is separate.
MIRA Website InsightsThe reviewed component uses random browser identifiers for up to 180 days and a 180-day database visit window; browser sessions expire after 30 minutes of inactivity. Server cleanup depends on scheduled execution.
MIRA Site Insights aggregate statisticsConfigure a 180-day period for this policy. Summaries made effectively anonymous may be kept separately without a reasonable way to identify visitors. Other trackers follow the specific periods in their inventory.
Ordinary security and audit logsFor logs under MIRA’s control, 90 days after the event. Logs a provider must retain independently under applicable duties follow that provider’s documented rules and are not erased by this plugin. Evidence specifically needed for an incident or dispute is separated and kept until the case ends and the applicable claims period, with documented review.
Pseudonymous prior Business trial record24 months after trial activation. An email fingerprint is not anonymous. Retention and objections or erasure requests are handled separately from ordinary work archives.
Agreement evidence, preferences and rights requestsAgreement evidence: during the relationship and 10 years after closure, restricted to evidence and related claims. Rights requests: 24 months after case closure. Excess identity documents are removed earlier. Disputes are subject to specifically documented preservation.
Support, tickets and related email24 months after the request closes. Unnecessary attachments and excess copies are removed earlier; evidence for contracts or disputes is separated under its own retention rule.
Files for personalised products90 days after final delivery, unless a separate documented request supports a new order or specific dispute evidence must be kept. Promotional reuse requires a separate lawful basis.
Newsletter and marketing objectionsSubscription until withdrawal and no later than 24 months after the last confirmed consent unless renewed and recorded. Minimal objection evidence is kept for 24 months to prevent improper reimports. Every new marketing message still requires a valid lawful basis after that period.
MIRA accounting and tax documentsFor documents subject to the duty, 10 years from the applicable starting point, including the last entry under Italian Civil Code Article 2220; additional statutory or assessment periods are handled separately. This does not apply to every item of app content.
Aruba automatic backupsThe Managed Smart Hosting for WordPress service shows 7 complete daily copies covering the last 7 days. Data erased from live archives may remain until backup rotation. The 7-day period applies to these automatic copies.
Manual, downloaded, additional and staging copiesErasure plan within 30 days after creation unless separately justified for an incident or dispute. Aruba on-demand copies do not expire automatically. Test environments use synthetic or minimised data; prior erasures are reapplied before restored records return to ordinary use.

Business Italia and Business International: access, expiry and erasure

This policy applies separately to each hosted Business workspace with version 1.11.0 or later. It does not change the Lighting Planners’ retention rules. An active subscription for one application does not grant access to the other. A valid 30-day trial permits access without a paid subscription during those 30 days.

30 days of trial, then 5 days before erasure

StageAccess and data
Valid trial or active subscriptionThe workspace is available according to its plan. The trial lasts 30 days from verified activation. Export records you need while access is valid.
Effective expiry without another valid entitlementWorkspace access stops immediately, including viewing, searching and self-service export. Email and WhatsApp sending and scheduled workspace backups stop. The account can still open the renewal/status screen and privacy/rights channels.
Next 5 days (120 hours)The archive remains inaccessible while the user can activate or reactivate the relevant subscription. The displayed notice gives the erasure date and time. In the ordinary trial case, the deadline is 35 days after trial activation.
After the 5-day deadlineIf no valid entitlement has been restored, the system erases the application’s live archive, its internal snapshots and local integration credentials, then verifies the result. Erased records cannot be recovered by purchasing a plan later.

Cancelling renewal while access remains valid for an already paid period does not start the five days early: the period starts when access actually ends. A valid relevant subscription restored before the deadline cancels the scheduled erasure. A subscription to the other Business app does not preserve this workspace.

Accounts already expired when this policy is introduced

Existing expired archives receive a new five-day transition window after the rollout notice has been accepted for sending. They are not erased retroactively on installation. A pre-existing archive with no subscription or trial follows the same notified five-day process. An account with no workspace data is not permission to insert records without a valid trial or subscription.

In-app and email notices

The service explains the policy at trial activation, warns approximately three days and one day before expiry, announces the access block and the exact five-day deadline, sends a final warning about 24 hours before erasure and confirms verified erasure. The locked status screen shows the applicable deadline. These are service messages, separate from marketing consent. Acceptance for sending is not proof that an email reached the inbox; check spam and keep the account email current.

What is erased and what is separate

Erasure covers the relevant Business workspace’s movements, profiles, contacts, appointments, CRM/settings records, local application logs, internal backup snapshots and schedules, email/WhatsApp queues and local configurations, and local Google connection tokens. Related named usage statistics are removed through the available verified cleanup integration; incomplete cleanup is flagged for handling.

The WordPress/customer account, WooCommerce orders and subscription records, immutable agreement records, minimal trial abuse-prevention references and necessary erasure/notice evidence are separate. This process does not automatically close the account or erase data that must be retained for a documented legal duty or legal claim. Such records must be limited to the necessary purpose and period.

Hosting backups are separate from the application’s internal snapshots. Existing external backups, downloaded exports, messages already delivered, recipients’ mailboxes and events already held by Google or Meta are not remotely erased by this operation. Their deletion or expiry follows the applicable provider/backup procedure. A restoration must reapply completed erasures before restored archives become available.

Rights and professional customers’ instructions

You can request access, return, rectification, restriction or erasure through the MIRA Privacy Center or info@miravisualart.com without buying a subscription. This does not reopen the workspace. Professional controllers can give return/deletion instructions under the DPA. Make return requests before erasure: a request is reviewed by MIRA and does not itself pause the scheduled procedure. MIRA must assess and handle any applicable preservation or return instruction separately; records already irreversibly erased cannot be returned.

Scheduled execution and verification

The five-day deadline is fixed. Cleanup and email processing run through WordPress scheduled jobs; a working server cron is needed for prompt execution even without visitors. A delayed job does not extend workspace access. Subscription status is rechecked before destruction; an uncertain status or incomplete deletion is flagged and retried rather than reported as completed. No statement on this page certifies deletion of external copies.

SHA-256 d8fa86af8f98ceb7ea9f9967a301837527ede46d0102e90f0486c03d3e5d4c1b

Data use terms for MIRA applications

Version 2026-11-21-business-30-plus-5-v1 · ID 65 · 2026-11-21 06:16:34 UTC

Data use terms for MIRA applications

These terms concern data use in Business Italia, Business International and the MIRA Lighting Planners. They supplement the commercial service terms without replacing prices, renewals, withdrawal rights, warranties or support. The DPA also applies to content processed on a professional customer’s behalf.

Users and roles

If acting for a business or organisation, identify that entity and confirm your authority to enter the agreement and give instructions. You remain responsible for your processing purposes, the lawfulness of entrusted information and the notices and choices you must provide to your clients. MIRA retains its own provider and processor obligations within the DPA’s scope.

Solely personal or household use, where supported by the service journey, is separate from professional or mixed use. A potential exclusion for the user’s household activity does not automatically extend to MIRA. Do not declare household use to avoid duties relating to a business activity.

Permitted information and minimisation

Enter only information relevant to the functions used and which you may lawfully entrust to the service. Check rights and authorisations before uploading documents, images or third-party information. Limit free-text notes and detail in transaction descriptions, appointments and set names.

The standard service is not intended for medical records, criminal offence documents or other special category archives. If your activity requires such information, contact MIRA before uploading it to arrange a separate scope and suitable safeguards. A free-text field does not authorise every category of data.

Communications, consent and objections

When using email or WhatsApp, check recipients, content and the legal grounds for sending. A contact in an address book, a booking or a purchase does not automatically constitute consent to promotions. Selections and imported lists must represent choices actually obtained and documented. Check withdrawals, objections and do-not-contact requests before sending.

Technical message delivery is separate from individually tracking opens or clicks. Before enabling such tracking, check recipient information, the applicable legal ground and refusal and withdrawal arrangements. Provider settings must respect the same choices. The DPA does not give MIRA a right to use your clients’ contacts for its own promotions.

Privacy acknowledgement, acceptance of terms and conclusion of the DPA are separate from optional preferences. A privacy request does not by itself update every list or campaign: also use the relevant controls or unsubscribe functions to stop a flow and report problems to MIRA.

Integrations and account security

Connect only accounts you are authorised to use. Google Calendar, WhatsApp and email services are involved according to the enabled feature and applicable provider relationship. Before activation, check transmitted information, recipients and countries, including the provider schedule. Do not send tokens, passwords or entire address books through unagreed channels.

Disconnecting an integration affects future use according to the available controls; it does not automatically delete information previously delivered to the external provider. Protect credentials and access codes, avoid shared accounts and restrict collaborator access to those who need it. Report incidents or suspicious access to info@miravisualart.com. Support messages should contain only necessary information, with unrelated data obscured.

Export, service closure and erasure

Exports can contain personal data: protect them and share them only with authorised recipients. Internal application copies are separate from hosting backups. Deleting a contact or one item can leave references in transactions, appointments, messages and related records.

For Business Italia and Business International version 1.11.0 or later, the trial lasts 30 days. When valid trial/subscription access ends, viewing and self-service export stop immediately. Without reactivation, the inaccessible workspace and its internal copies are automatically erased after 5 days (120 hours), with in-app/email notices and a final entitlement/result check. The account, orders, legal evidence and external copies follow their separate rules. Privacy/return requests remain available without a paid plan. The dedicated Business expiry and erasure policy below gives the complete rules.

Erasing an application archive does not, by itself, remove the MIRA account, orders, tax records, all agreement evidence or external copies. Deleted Planner content and functional counters have different scopes. For a complete request, identify the account, application and information concerned: the request is checked against the relevant records.

The Business trial abuse-prevention reference, based on an email fingerprint and activation details, is pseudonymous and separate from working content and statistics. It can survive account deletion. It is handled under the retention table and assessment of individual requests; it does not waive individual rights.

Documents, versions and requests

The notice, data terms, DPA and provider schedule are available in the MIRA Privacy Center. The displayed version and any recorded confirmation identify the applicable text. To clarify roles, permitted data categories or additional instructions, contact info@miravisualart.com before starting the relevant processing.

Business Italia and Business International: access, expiry and erasure

This policy applies separately to each hosted Business workspace with version 1.11.0 or later. It does not change the Lighting Planners’ retention rules. An active subscription for one application does not grant access to the other. A valid 30-day trial permits access without a paid subscription during those 30 days.

30 days of trial, then 5 days before erasure

StageAccess and data
Valid trial or active subscriptionThe workspace is available according to its plan. The trial lasts 30 days from verified activation. Export records you need while access is valid.
Effective expiry without another valid entitlementWorkspace access stops immediately, including viewing, searching and self-service export. Email and WhatsApp sending and scheduled workspace backups stop. The account can still open the renewal/status screen and privacy/rights channels.
Next 5 days (120 hours)The archive remains inaccessible while the user can activate or reactivate the relevant subscription. The displayed notice gives the erasure date and time. In the ordinary trial case, the deadline is 35 days after trial activation.
After the 5-day deadlineIf no valid entitlement has been restored, the system erases the application’s live archive, its internal snapshots and local integration credentials, then verifies the result. Erased records cannot be recovered by purchasing a plan later.

Cancelling renewal while access remains valid for an already paid period does not start the five days early: the period starts when access actually ends. A valid relevant subscription restored before the deadline cancels the scheduled erasure. A subscription to the other Business app does not preserve this workspace.

Accounts already expired when this policy is introduced

Existing expired archives receive a new five-day transition window after the rollout notice has been accepted for sending. They are not erased retroactively on installation. A pre-existing archive with no subscription or trial follows the same notified five-day process. An account with no workspace data is not permission to insert records without a valid trial or subscription.

In-app and email notices

The service explains the policy at trial activation, warns approximately three days and one day before expiry, announces the access block and the exact five-day deadline, sends a final warning about 24 hours before erasure and confirms verified erasure. The locked status screen shows the applicable deadline. These are service messages, separate from marketing consent. Acceptance for sending is not proof that an email reached the inbox; check spam and keep the account email current.

What is erased and what is separate

Erasure covers the relevant Business workspace’s movements, profiles, contacts, appointments, CRM/settings records, local application logs, internal backup snapshots and schedules, email/WhatsApp queues and local configurations, and local Google connection tokens. Related named usage statistics are removed through the available verified cleanup integration; incomplete cleanup is flagged for handling.

The WordPress/customer account, WooCommerce orders and subscription records, immutable agreement records, minimal trial abuse-prevention references and necessary erasure/notice evidence are separate. This process does not automatically close the account or erase data that must be retained for a documented legal duty or legal claim. Such records must be limited to the necessary purpose and period.

Hosting backups are separate from the application’s internal snapshots. Existing external backups, downloaded exports, messages already delivered, recipients’ mailboxes and events already held by Google or Meta are not remotely erased by this operation. Their deletion or expiry follows the applicable provider/backup procedure. A restoration must reapply completed erasures before restored archives become available.

Rights and professional customers’ instructions

You can request access, return, rectification, restriction or erasure through the MIRA Privacy Center or info@miravisualart.com without buying a subscription. This does not reopen the workspace. Professional controllers can give return/deletion instructions under the DPA. Make return requests before erasure: a request is reviewed by MIRA and does not itself pause the scheduled procedure. MIRA must assess and handle any applicable preservation or return instruction separately; records already irreversibly erased cannot be returned.

Scheduled execution and verification

The five-day deadline is fixed. Cleanup and email processing run through WordPress scheduled jobs; a working server cron is needed for prompt execution even without visitors. A delayed job does not extend workspace access. Subscription status is rechecked before destruction; an uncertain status or incomplete deletion is flagged and retried rather than reported as completed. No statement on this page certifies deletion of external copies.

SHA-256 da26c639769bda2166d646fb387b41759ee0a5ee92af0c422926e98f78ee1f09

Providers and integrations for MIRA applications

Version 2026-11-20-review1 · ID 26 · 2026-11-20 20:36:30 UTC

Providers and integrations for MIRA applications

This schedule distinguishes MIRA’s infrastructure, integrations enabled by users and services relating to the commercial relationship. It applies with the privacy notice and, for professional customers’ content, the DPA. A recipient’s role follows its activities, instructions and applicable agreement; a plugin name does not, by itself, identify a data recipient.

MIRA hosting infrastructure

ProviderService and roleInformation involved
Aruba S.p.A., Via San Clemente 53, 24036 Ponte San Pietro (BG), Italy, VAT number 01573850516; www.aruba.itHosting Gestito Smart per WordPress for miravisualart.com. Processor for processing where MIRA is controller, and subprocessor for content MIRA handles on professional customers’ behalf, within the applicable agreement and instructions.Website files and databases, accounts, application records, technical data and recovery copies included in the service.

Aruba states that its hosting is provided in its Italian data centres. The MIRA service panel shows seven complete daily automatic backups for the last seven days and two available on-demand manual backup slots. Availability does not establish that two manual copies exist. Manual backups do not have the same automatic expiry as daily copies; downloaded or separately stored copies have a distinct lifecycle. Copies and erasure are handled under the retention table and DPA.

The provider relationship includes the terms and appointment applicable to the service. Aruba’s public terms are available on its website; referring to a public version does not replace the agreement accepted for MIRA’s relationship.

Services connected directly by users

Optional featureInformation and connection purposeRole distinction
SMTP or another email service selected in the Business appSender and recipients, message content, credentials or tokens, technical delivery results, relevant preferences and unsubscribe information.The provider and relationship depend on the configured account. A user’s direct contract is separate from a service supplied by MIRA.
WhatsApp Business Platform and any intermediariesNumbers, messages, templates, tokens, delivery states and objections, according to the authorised feature.Account ownership, agreements with Meta and any intermediaries determine the recipients involved. An available module does not prove activation.
Google CalendarCalendar identifiers and authorisation, events and information selected for synchronisation.The customer authorises its own account and requested operations; the corresponding Google relationship is separate from MIRA’s service.
Postmark or other optional email transportsInformation needed for delivery, technical results and any measurement choices when the connection is actually enabled.An available function does not identify the contractual entity by itself or authorise open or click tracking.

Before enabling a connection, the actual account and provider, transmitted data, countries, role, agreements and applicable safeguards must be identified. A user’s selection documents the technical transmission instruction but does not replace legal requirements or automatically make every service MIRA’s subprocessor. Disconnection does not automatically erase information already transmitted.

MIRA email, payments and other recipients

Access, service and support messages use the sending infrastructure configured for the website. Transport providers and recipients’ mailboxes handle addresses, content and delivery information within their respective scope. This is separate from the email service each user configures to communicate with its own clients.

Orders, payments, subscriptions and administrative support relating to MIRA can involve relevant payment providers and advisers. This does not make them recipients of the customer’s entire Business archive. Website statistics, advertising, spam protection, translation and external content are covered by the website notice and Cookie Policy: their presence does not authorise them to receive application address books or documents.

WordPress, WooCommerce and server-executed plugins are software components. Their producer becomes a recipient only where a relevant data flow exists, such as a remote service, telemetry, support or external content. A software inventory is therefore not equivalent to a list of processors.

Countries, changes and information

Italian hosting does not mean that all external connections, recipient mailboxes or remote access remain in Italy or the European Economic Area. Recipients, locations and transfer grounds must follow the actual service and relationship. For information about your connection and applicable safeguards, contact info@miravisualart.com.

The DPA’s change and objection provisions apply to MIRA’s subprocessors. This schedule does not authorise unknown recipients or future services merely because an integration is technically available. The published version and any communications about the processing chain are separate from a user’s marketing preferences.

SHA-256 c539b113ae06618d1196f18b4306afbdbdc664e2bbe1458c0f4f6eb6517a15f5

Sign in for your documents and data requests