Skip to content

Contact

Contact Solory: one inbox, one person reads it

Support, billing, data-protection and security questions all go to the same address: support@solory.ch. Solory is operated by one person, who builds the product and answers the mail. This page says what belongs in the first message, what is not promised, and which requests are faster to settle yourself inside the app.

  • 1person operates Solory and reads the support mail
  • 5interface languages: EN, DE, FR, IT, HU
  • 30 daysgrace period on an account-deletion request

One address, and the person who reads it

No queue, no ticket robot, no first-line script.

Write to support@solory.ch. Solory is operated by one person, who builds the product, administers the platform and answers the mail, so a reply comes from someone who can open the code. That is also the limit of it, and the sections below say what that does and does not promise.

No telephone number is published, and the same address takes support, billing, data-protection and security mail. Put the topic in the subject line - Billing, Privacy, Security, or a plain description of the fault.

Email
support@solory.ch, for every kind of request.
Post
Alex Földvári, Im Sand 4, 8105 Watt, Switzerland.
Status page
/status - each component's current state, a 90-day bar, the incident timeline and scheduled maintenance.
Changelog
/changelog - what shipped, and when.

What you write here reaches the operator by email and is kept as an enquiry. Nothing else happens with it.

Post
Alex Földvári, Im Sand 4, 8105 Watt, Switzerland

What to put in the first message

A support answer is only as fast as the first message allows.

  1. The account email

    The address you sign in with. It is how the account is found; a client name is not enough.

  2. What you expected, and what happened

    One sentence each. "The QR-bill did not print on invoice 2026-014: the PDF came out with no payment part" can be reproduced. "Invoicing is broken" cannot.

  3. Where you were

    The screen, the device and the browser. Several faults appear on only one of those, and a reload in a second browser often settles which.

  4. The record, by its number

    Invoice, estimate, contract or expense number. Never paste passwords, card numbers or bank credentials into a support mail.

Support, privacy, billing: where each question goes

One address takes everything, but several of these are faster to settle yourself, in the app.

What you needWhere it happensWhat to send or do
A fault, or how something workssupport@solory.chAccount email, record number, expected against actual.
A copy of your dataSettings, PrivacyRun the export yourself: a ZIP with one JSON document and a README, behind a short-lived link.
Account deletionSettings, PrivacyOpens a 30-day grace period during which you can cancel the deletion. Refused while sent or overdue invoices are unpaid.
Access, correction, objection, restrictionsupport@solory.chName the right you are exercising. Your identity may need to be verified first.
Change or cancel a planSettings, BillingOwner only. Cancelling takes effect at the end of the period already paid for.
Card details and receiptsStripe billing portal, from SettingsA Free account has no billing account to manage yet, and is told so.
A security findingsupport@solory.ch, subject "Security"What you found and how to reproduce it, then stop - see below.

There is no privacy@ or billing@ address. A second inbox with the same person behind it would only slow down whoever guessed wrong.

What is promised, and what is not

The useful part of a contact page is the part that does not flatter itself.

No response time is published, and none is implied here. Professional and Business carry a priority-support flag in the plan, but no number of hours is defined anywhere in the product, so no number of hours is promised.

There is no uptime guarantee either. The 90-day bars on the status page are derived from recorded incidents - a description of what happened, not a contractual figure. No recovery objective, backup frequency or restore-test cadence is published, and no ISO 27001, SOC 2 or third-party penetration test is claimed, because none exists.

Check the status page and the changelog first

Two public pages answer part of the mail before it is written.

/status
Per component: the current state, a 90-day uptime bar, the incident timeline with the updates written while each incident ran, and maintenance announced in advance.
/changelog
What changed and when. If a screen looks different from yesterday, it is written down here.

The bars come from incidents that were recorded, not from a promised figure, which is why the timeline sits directly beneath them. If a component is already marked degraded, a message about it still helps - it says who is affected.

Reporting a security issue

Same address, Security in the subject line, and one rule about how far to go.

  1. Write down what you found

    The URL or screen, the steps that reproduce it, and what an attacker would get. A short recording beats an automated scanner report.

  2. Stop at the proof

    Do not read, alter or download data that is not yours, do not test another person's account, and do not run scanning or load tools against the service. The Terms forbid probing, scanning or testing the systems, and reporting a finding does not suspend that.

  3. Send it to support@solory.ch

    Say whether anyone else has been told and whether you intend to publish, so the fix and the disclosure can be sequenced rather than raced.

  4. Expect a person, not a programme

    There is no bug bounty, no reward and no published triage time. One person reads the report, answers it, and says what was changed.

If an incident affects personal data, notification goes to the account email address without undue delay after the operator becomes aware, with the information reasonably available, so the account holder can meet their own duties towards the FDPIC (EDÖB) and their own clients.

Asking for a data export or an erasure

Both are self-service, and both are explicit about their limits.

Settings, then Privacy, produces a ZIP with one structured JSON document and a README, under the right of access and portability. The link is short-lived, the screen states the expiry, and at most one archive is kept per account. A section that could not be read is named inside the archive and the screen says the copy is not complete - an empty array claiming you have no clients would be worse than an error.

It is an archive, not a handover file: no DATEV, Abacus, Bexio or Banana format, so a Treuhänder wanting a bookkeeping import will not find one. Sealed invoices and signed contracts are included as legal records.

Deletion is requested in the same place. It opens a 30-day grace period with a live countdown, can be cancelled throughout, and is refused while sent or overdue invoices are unpaid, naming which ones. On expiry, sign-in is permanently disabled and the email address removed from it; files, stored credentials and connected channels are deleted; and the rest is irreversibly anonymised. What survives is stated before you rely on it:

  • Accounting records - invoices, payments, expenses - for ten years from the end of the financial year, as OR Art. 958f requires, scrubbed as far as the record still makes sense.
  • Signed contracts, with their signature evidence: an executed agreement is not the operator's alone to erase.
  • The audit log, with name, email, IP address and browser scrubbed out of it.
  • The deletion request itself, as evidence of when it was made and carried out.
  • Backups are not edited; a deletion reaches them as they are rotated and overwritten on their normal cycle, within a few weeks.

A failed step leaves the request open and retried rather than marked complete: you will not be told your data is gone while any of it is not. You can also complain to a supervisory authority - in Switzerland the FDPIC (EDÖB) in Bern, in the EU your local one.

Postal address, and who is behind Solory

The Impressum details in one place, because a contact page that hides them is not a contact page.

Provider
Alex Földvári, sole proprietor trading as Solory.
Postal address
Im Sand 4, 8105 Watt, Switzerland.
Email
support@solory.ch
Legal form
An Einzelfirma, currently not entered in the Swiss Commercial Register.
VAT
Below the Swiss VAT registration threshold and not registered for MWST: no UID or MWST number, prices in Swiss francs without Swiss VAT, and no VAT on a receipt.
Law and jurisdiction
Swiss law; place of jurisdiction Zürich, subject to any mandatory statutory venue.

That address is the one printed in the Impressum, the Terms, the Privacy Policy and the DPA, and it is where notices and service of process go. Email reaches the operator faster, and nothing about running the product requires a letter.

Questions people ask

How do I contact Solory support?

Write to support@solory.ch. It is the only published address and it takes support, billing, data-protection and security questions alike; no telephone number is published. Include the email address you sign in with, the record number in question, and what you expected against what happened.

How fast will I get an answer?

No response time is published, so none is promised. Professional and Business carry a priority-support flag in the plan, but no number of hours is defined anywhere in the product. Before writing about something that looks broken, check the status page: a recorded incident answers the question sooner than a reply can.

Is there a separate address for privacy or billing questions?

No, one address takes everything. Most of those requests are faster in the app: the data export and the deletion request are in Settings under Privacy, plan changes and cancellation are in Settings under Billing, and card details are managed in the Stripe billing portal. Only the account owner can change or cancel a plan.

How do I report a security issue?

Email support@solory.ch with Security in the subject line, describe what you found and how to reproduce it, and stop there. Do not read or alter data that is not yours, do not test another account, and do not run scanning or load tools - the Terms forbid probing, and a report does not suspend that. There is no bug bounty and no reward programme.

How do I get a copy of my data?

Run the export yourself in Settings under Privacy. It produces a ZIP with one structured JSON document and a README behind a short-lived link, and at most one archive is kept per account. If a section could not be read, it is named inside the archive and the screen says the copy is not complete. It is a portability archive, not a DATEV, Abacus, Bexio or Banana import file.

What happens when I ask for my account to be deleted?

A 30-day grace period starts and can be cancelled at any point during it, and the request is refused while sent or overdue invoices are unpaid. Afterwards sign-in is disabled and the email address is removed from it; files, credentials and connected channels are deleted; and the rest is anonymised. Accounting records still survive ten years under OR Art. 958f and signed contracts survive with their signature evidence, so it is not total erasure.

Can the operator see my data while answering a support request?

Yes, an account can be opened in order to answer a support request or investigate a fault, and that is stated rather than hidden. It writes a record to your own audit log, which you can read, it is visible on screen while it lasts, and it is limited to what the question needs. Nobody else has access, and the audit log cannot be edited or deleted.

Write to support@solory.ch

Put the account email and the record number in the first message and most questions are settled in one reply. If something looks broken everywhere at once, the status page will usually say so before an answer can.