Home solar in Cyprus: request an archive before account closure

Ask what remains before closing a monitoring account

A household changing its solar-monitoring arrangement may want to remove an old account. Before giving that instruction, find out what the account holds and what the manufacturer says account closure does. A downloaded picture, an energy-data file and a registered equipment document are different records. The owner should decide what information it wants to retain before assuming that another login will preserve everything.

The Fronius Solar.web FAQ says deleting a user account permanently deletes generation and consumption data associated with the system. The page also explains that some personal information connected with certain purchases must be retained by the manufacturer. Check the current account-specific position directly with Fronius. An owner's desire to close an account is not evidence that all related information will disappear or remain recoverable elsewhere.

This guide helps commission an archive and clarification task. It does not instruct the reader to delete an account, alter equipment or transfer another person's information. Use the manufacturer's supported process and the authorised account holder's decision. Obtain appropriate advice where privacy, a dispute or legal retention obligations require it.

Separate the questions being asked

Write down the reason for the proposed closure. Perhaps an owner wants to stop using an old email address, remove a redundant login or leave a particular platform. Those goals may involve different supported processes. Ask the manufacturer which process addresses the actual problem before treating deletion as the only option.

Name the information the household uses. This could include historical generation records, copies of reports it already purchased or equipment documents it has obtained. Describe the records without assuming the platform offers an export for every one. The provider should confirm what it can retrieve and in which format.

Keep operation and records separate. A question about an online account does not establish what a particular inverter, service agreement or other system will do afterwards. Refer those questions to the relevant manufacturer and installer, using the actual equipment references. Do not infer an operational result from a statement about data deletion.

Build a small archive-request register

This fictional example concerns an owner called Household H. The references describe requested documents, not files promised by a manufacturer.

A1 does not become complete because the owner downloaded A2. A report may summarise a period without supplying its underlying records. A3 may be held by the installer rather than the monitoring platform. The register makes those differences visible before anyone marks "backup done".

The fictional owner already has R3 in an email folder. Receiving another copy of R3 would not satisfy the request for R4. Check the document reference and date, rather than treating any attachment with a familiar filename as the final report.

Test the archive as a reader

Ask the commissioned provider to identify each file and the period or equipment it concerns. Open the files through the owner's ordinary authorised process and check that the expected information is readable. Keep this as a document check. It does not establish measurement accuracy or certify the technical condition of the installation.

For fictional A1, the returned file might cover January through November while the request asks for twelve months. The owner can identify the missing December period without filling it with invented numbers. Ask the provider whether the requested information exists and what additional work, if any, it can offer.

Record the answer. If December is unavailable, mark that limitation in the archive index. A complete explanation of an incomplete dataset is more useful than a folder named "full year" that hides the gap. Do not interpolate values simply to make the file look complete.

Obtain a response about the proposed action

Send the manufacturer a precise account enquiry through its supported channel. Identify the action being considered and ask what happens to the relevant records. Supply only the information it appropriately requests. Keep passwords, recovery codes and unnecessary household details out of a general service quotation pack.

Ask whether the answer concerns deleting a user, changing an account detail, removing access or another process. Those descriptions can be confused in ordinary conversation. Copy the exact action named in the manufacturer's response into C1 so the owner can see what was answered.

If the reply describes a different action, ask for clarification. The household should not apply instructions about removing a guest user to closing the owner's account. A familiar screenshot is not a substitute for confirmation about the intended process and the authorised person.

Commission the work as a defined service

Ask whether the provider offers document retrieval, archive organisation or account enquiry support, and what it excludes. Request its fee basis, VAT treatment, expected deliverables and the way additional requests are approved. A technical service visit and an administrative archive task can require different appointments.

Solarpanel is a starting point for a household-solar service enquiry with the named archive requests. If the records belong to a business and need accounting review, Accountly provides a relevant enquiry route for that separate professional scope. Confirm what the actual providers accept. Neither link establishes a data-retention period or authorises account closure.

The account holder should retain control of the final instruction through the supported process. A provider preparing an archive can report its completed work without deciding whether the owner should close the account. Keep that distinction in the proposal and handover.

Leave a usable archive index

At completion, list the files received, the periods covered, unresolved gaps and the manufacturer's actual response. In the fictional case, A2 closes only when R4 is identified, while A1 stays partly unresolved if December is missing. A3 can close when the installer supplies E2, independently of the platform enquiry.

The owner can then make a decision with the limits visible. Keep the archive in the owner's chosen storage arrangement and check it remains accessible through that arrangement. The purpose is to preserve identifiable records before an account action, rather than assume that data will be recoverable after an irreversible deletion.