Privacy Policy

Text revised: 24 September 2026

This policy explains how Aera Vibe collects, uses, stores and discloses personal information when you visit the website, use an account, analyse interiors or contact support.

For privacy questions, access or correction requests, or complaints, contact contact@aera.rent. The operator is responsible for handling these requests.

01

Who runs Vibe, and what this covers

We apply the privacy commitments in this policy to all users. The Australian Privacy Principles and the New Zealand Privacy Act 2020 and Information Privacy Principles are the standards we adopt, including as additional commitments where they are not mandatory. The operator’s location in Georgia does not by itself exclude those laws. Applicable mandatory privacy rights in Australia, New Zealand and other countries are preserved; this policy does not claim a regulatory exemption or certification.

Aera Vibe is operated by Sergei Kovalev, a natural person, at 19 Pirosmani Street, Batumi, Adjara 6000, Georgia. In this policy, “we” means the operator, who is responsible for the service’s handling of personal information.

Contact the operator at contact@aera.rent or +995 585 890 610. The same contact handles privacy requests from every country.

This covers people with accounts, people who visit without one, people who write to support, and people who can be recognised in material somebody submits. It does not make you our agent, and it does not give you permission to upload another person’s information.

The registration form links to this policy. Analysis and import interfaces provide notices relevant to those actions. Optional permissions are managed separately in Privacy settings; accepting this policy does not itself authorise every optional use.

02

What we hold

Not all of this applies to everyone. If you have never run an analysis there is nothing under photographs; if you have never written to support there is nothing under support.

What Vibe holds about you
What
Your account
Examples
Email address, display name, language, theme, preferences, account status.
Worth knowing
Passwords are stored as hashes, not as readable passwords. Hashing reduces exposure but does not eliminate security risks.
What
Sign-in and security
Examples
Session records, sign-in events, two-factor enrolment, recovery codes, security alerts, abuse signals.
Worth knowing
Recovery codes are shown when generated; their stored hashes are used for verification. Support does not request your password or two-factor secret.
What
Photographs and their file details
Examples
Images you upload or import; file name, type, size, timestamps, and any metadata the file carried.
Worth knowing
A photograph of a room can say more than it looks like it does. Every image is re-encoded before analysis, which strips the original file metadata — including any GPS location the camera wrote into it.
What
Imports
Examples
The listing address you gave, the source site, which images you chose, and whether it worked.
Worth knowing
A listing page can contain other people’s information. Only sites on a fixed allow list can be imported, and the page is fetched by our server.
What
What you type and choose
Examples
Answers, prompts, selected styles, saved profiles and reports, favourites, mode, credits, timestamps.
Worth knowing
Used to deliver the requested analysis, retain your saved work and apply your selected settings.
What
What the analysis concludes
Examples
Style profiles, match scores, explanations, and the reasoning shown beside them.
Worth knowing
Opinions produced by a model. They can be wrong, and you can tell us so.
What
Technical records
Examples
Requests, errors, timings, IP address, browser and device details, approximate region from the network.
Worth knowing
Used for service operation, fault diagnosis, security and abuse prevention.
What
Support
Examples
Your messages, anything you attach, and the history of the conversation.
Worth knowing
Messages remain with the ticket. Attachment cleanup depends on both the age of the file and closure or resolution of the ticket; see Retention and security.
What
Payments
Examples
Public purchases are not currently available.
Worth knowing
The public service does not collect card details. Reports of an unexpected charge are handled through support; do not send full payment credentials.
03

Where it comes from

  • From you: when you register, sign in, turn on two-factor, recover an account, upload or choose photographs, answer questions, change a setting, or write to support.
  • From a listing page you asked us to import.
  • From your browser and network automatically, the way any website receives a request — the request itself, and what it carries.
  • From the providers that run the service for us, named further down this page.
  • From another person, only where you or they had the right to give it.

The service also tells you these things at the point they matter.

What you are told, and when
When
Creating an account
What it says
What is required and what is optional, with this policy and the User Agreement linked before the account exists.
When
Before your first analysis
What it says
Who receives the photographs, what is sent with them, why, which country they are processed in, and how to withdraw. Nothing runs until you have answered.
When
Importing a listing
What it says
Which sites can be imported, and that our server fetches the page.
When
Cookies
What it says
Cookies and browser storage support sessions, guest work, preferences and the integrations you use. Their purposes are described in Cookies and local storage below.
04

What we use it for

  • Running your account: sign-in, sessions, two-factor, recovery, preferences, and what your plan gives you access to.
  • Doing what you asked for: analysing the photographs you chose, building a Vibe Profile, comparing it against a property, and keeping what you saved.
  • Importing a listing you pointed us at, and telling you why when it fails.
  • Counting the runs you have used on Basic and on the Expert demo, and stopping that count being circumvented.
  • Keeping the service standing up and safe: finding faults, noticing abuse, investigating incidents, holding backups.
  • Answering you when you write, and telling you about something that affects your account or its security.
  • Meeting a legal obligation, or defending a claim.

Permission for external AI analysis and the Vibe Memory option are separate. You can withdraw them in Privacy settings without closing the account. Withdrawal concerns subsequent use; it does not reverse completed processing or automatically delete saved results or existing memory. Use the memory reset or deletion controls, or contact us, to request removal.

We limit use to the purposes described in this policy. A materially different purpose requires an updated notice and a valid legal basis, including renewed consent where required.

05

Photographs, and what the analysis does with them

The outputs — a style profile, a match score, the explanation beside it — are inferences. A model reads pixels and produces an opinion. It is often useful and sometimes wrong. Treat it as an opinion.

  • Vibe does not perform face recognition, identity verification from photographs, emotion detection, or any decision about whether someone qualifies for something.
  • We do not sell image data, use it for targeted advertising or use it ourselves to train a general-purpose model. We send selected data to an external provider to perform analysis. We have not independently confirmed all of that provider’s downstream training and retention practices; the provider disclosure below explains this limitation.
  • You need the right to submit each photograph. It is worth a second look before you do: documents on a desk, a screen left on, a name on a parcel, a face in a mirror.
  • No Vibe profile or score is used by us to decide anything about employment, housing, credit, insurance, health, education, or law enforcement — and it should not be used that way by anyone else.
  • Report an inaccurate or harmful output to contact@aera.rent. We review the report and explain the correction, removal or other action available; a model-generated opinion cannot always be amended in place.
06

Who else sees it

The following providers and recipients support the service. An integration receives data only when it is enabled and the relevant feature is used. Providers may use subprocessors under their own terms; this list is not a certification of their entire processing chain.

Providers and other recipients
Who
Amazon Web Services
What they get
The application runs there, so everything the service holds passes through it.
Where
United States (us-east-2).
Who
Neon
What they get
The database: your account, your saved profiles and reports, everything durable.
Where
United States (us-east-2).
Who
Upstash
What they get
Managed cache: temporary application data and reusable image facts, which can describe room contents. New background Vibe Match results are held in the database rather than removed on first retrieval.
Where
Managed infrastructure. The processing region has not been independently confirmed for this policy.
Who
Abacus.AI
What they get
Selected, resized and metadata-stripped photographs; image facts, profile preferences and text needed for the requested analysis. Account credentials are not analysis inputs.
Where
United States.
Who
Listing sites you choose to import from
What they get
The request for the page you asked for. They see an ordinary visit, made by our server.
Where
Wherever that site is.
Who
Atlassian (Bitbucket)
What they get
The source code and the build pipeline. Not your content.
Where
Not applicable to your data.
Who
Regulators, courts, professional advisers
What they get
Only what is necessary for a specific matter or a binding lawful request.
Where
Depends on the matter.
Who
A future owner
What they get
If Vibe is ever sold or transferred, what that requires, under confidentiality.
Where
Location depends on the recipient; material changes are notified.
Who
Cloudflare Turnstile, when enabled
What they get
Registration anti-abuse checks may receive browser, network and challenge information.
Where
Cloudflare infrastructure; processing countries depend on the provider’s service.
Who
Pinterest, when you connect it
What they get
Authorisation requests and the image-selection requests you make through the integration.
Where
Pinterest infrastructure under its own terms.

External analysis is supplied by Abacus.AI under its customer terms. We do not authorise general-purpose model training on your content. We have not obtained independent confirmation of all provider or subprocessor retention and training practices, so we cannot guarantee that processing is transient or excluded from every downstream training use. Do not submit sensitive information that you cannot permit to be processed on this basis. This disclosure does not replace our legal duties to protect your information.

Development and maintenance use coding assistants in an environment with access to production systems. User content is not routinely supplied as development input, but technical access is possible. This policy does not represent those tools as isolated from production data or certify that their access has been independently audited.

If you enable a sharing link for a profile or report, anyone with that link can view its public presentation, including the images and analysis included in it. Disabling the link stops subsequent access through it; it cannot recall copies already downloaded or shared by a recipient.

To avoid analysing the same image repeatedly, Vibe Match caches image-derived room facts using a fingerprint of the prepared image, the model and the analysis format. These facts can be reused across runs and accounts that submit the same image. They do not include the requesting user’s profile, but a fingerprint is not a guarantee of anonymity. The cache is not a public gallery and has its own retention described below.

Nothing is sold or rented, and none of it is used for advertising.

07

Where it is processed

Vibe runs in the United States. Data about you therefore leaves the country you are in, which is worth knowing in advance.

  • The application and the database sit in Amazon’s and Neon’s US East (Ohio) region.
  • Photographs selected for an analysis are processed in the United States by Abacus.AI. The run does not start until you have been told that and agreed to it.
  • The operator accesses the systems from Georgia for administration and support. The development-access disclosure above also applies.
  • If a provider, a country, or a purpose changes materially, this page changes, and the notices inside the product change with it.
08

How long it stays, and how it is kept

Retention depends on the data category and the purpose for which it is held. Deleting a saved report is distinct from clearing temporary processing data, shared image facts, provider-held copies or backups.

Background Vibe Match runs have a twenty-four-hour window from the start of the run for retrieving and saving the finished result. We privately keep the complete analysis result, working copies of the reduced, metadata-stripped images rather than your original uploads, and a record of whether the run allowance was reserved, used or returned. This lets you retrieve the result again after a connection failure and prevents duplicate returns of the same allowance. Saving triggers deletion of the working image copies; the saved report keeps its separate lifetime described below. After the window expires, scheduled cleanup removes the temporary result, remaining image copies and settled allowance record. Failed cleanup is retried; an unsettled allowance record is kept until the deduction or return is resolved. These temporary data are also covered by the account deletion process.

How long each thing is kept
What
Your account and profile
How long
Until you delete it. Deletion is scheduled with a fourteen-day grace period you can cancel, then carried out.
What
Sessions, two-factor and recovery records
How long
Until they expire, are replaced, or the account is deleted.
What
Photographs and imports
How long
As part of the profile or report you saved, until you delete that or the account.
What
Copies sent for analysis
How long
Subject to the provider’s customer terms and applicable law. We cannot confirm a fixed per-run deletion deadline across the provider and its subprocessors.
What
Profiles, scores and explanations
How long
Until you delete them or the account. Nothing expires on its own — keeping it is what you asked for.
What
Working copies from a background run
How long
Saving triggers deletion. Any remaining copies are removed by scheduled cleanup after the twenty-four-hour run window; cleanup failures are retried.
What
Technical and security logs
How long
For as long as they are useful against faults and abuse, then removed on the ordinary retention of the platforms above.
What
Support messages
How long
Messages remain with the ticket. Cleanup selects attachments from resolved or closed tickets once the file exceeds the configured retention age, normally thirty days from upload. Open-ticket files may remain longer; removal occurs when cleanup runs successfully.
What
Reusable image facts
How long
Managed-cache entries expire after thirty days. A separate, size-limited process-memory cache has no fixed time expiry and is cleared by eviction or process restart. It is not automatically linked to account deletion.
What
Personal-data export files
How long
Download access expires after twenty-four hours. Access expiry is not a guarantee of immediate physical deletion from storage or backups.

Safeguards include password hashing, optional two-factor authentication, session controls, encryption in transit, separation of secrets from source code, image re-encoding to remove original metadata, and checks on imported URLs. No system is risk-free. Cleanup can require retries, and provider copies and backup cycles are separate from deletion of active account records. We do not promise immediate removal of every physical copy.

09

What you can ask for

Most of it you can do yourself without writing to anyone. Privacy settings hold an export of your data and the deletion request; Security settings hold your password, two-factor, and every device currently signed in.

Requests
What you want
A copy of your data
What happens
Ask for an export in Privacy settings and download it when it is ready. The file stays available for a day.
Where it stops
The self-service export may omit records where disclosure would expose another person’s information or protected security material. Contact us for an access request beyond that export; any refusal must have an applicable basis.
What you want
A correction
What happens
Contact us with the information you believe is inaccurate and the correction requested. We investigate and respond.
Where it stops
A model-generated opinion may require removal or an explanation rather than an in-place edit. We explain any refusal and available complaint route.
What you want
Deletion
What happens
Schedule it in Privacy settings: fourteen days to change your mind, then it happens.
Where it stops
Limited records may remain for a legal obligation, fraud investigation or backup cycle. Shared image facts and provider copies are not automatically cleared by account deletion; their separate retention is described above. Contact us for a deletion request beyond the account controls. Applicable deletion rights remain unchanged.
What you want
Withdrawing a consent
What happens
Use Privacy settings to withdraw an optional permission. Contact us if another device still offers processing or a withdrawal is not reflected.
Where it stops
Withdrawal concerns subsequent processing; it does not undo completed analysis or itself delete saved results or existing memory.
What you want
Challenging an output
What happens
Write to contact@aera.rent for a human review and an explanation of the action taken.
Where it stops
The result depends on the issue and applicable rights. The complaint response periods below apply, subject to shorter legal deadlines.

The operator handles requests and may ask for proportionate evidence of identity before disclosing or changing personal information. A New Zealand access or correction request is answered within twenty working days, subject to any lawful extension notified to you. We do not charge for requests under this policy.

10

Cookies, local storage and communications

The service uses cookies and browser storage for operation and preferences. The application does not load a Google Analytics browser tag or advertising pixel. We do not use information inferred from your photographs for advertising. Operational logging and a provider’s own technical processing are distinct from advertising tracking.

  • Session and guest-handoff cookies keep you signed in and carry guest work into an account. Core admission and Pinterest authorisation can use additional cookies when those features are used.
  • Browser storage can retain language and theme choices, analysis consent acknowledgements and information needed to resume work. Clearing storage can remove those local preferences and resumable state; it does not delete server-held records.
  • Approximate region may be inferred from your network address, by us or by a hosting provider, as it is on any website. Vibe never asks your browser for precise location.
  • We may contact you about support, account security or material service changes. Marketing communications require the applicable permission and an opt-out. You can disable optional communications in Privacy settings; this does not stop replies to support requests or necessary security notices.
  • Nothing inferred from your photographs is used for marketing.
11

Age, incidents, and complaints

Age

Vibe is for adults; the minimum age is 18. It is not built for children and carries no parental-consent flow, which is why the age limit is there. If we learn that an account belongs to someone under 18, it is closed and its data deleted.

If something goes wrong

We investigate and contain suspected loss, unauthorised access or disclosure. Where applicable legal notification thresholds are met, we notify affected people and the relevant authority, including the Australian Information Commissioner or New Zealand Privacy Commissioner as applicable. The operator is responsible for incident handling and notification.

Complaints

  1. Write to contact@aera.rent with enough detail to identify what happened. Do not send passwords, recovery codes or identity documents by ordinary email; they are not needed.
  2. You get an acknowledgement within five working days and an answer within thirty, with the reasoning behind it.
  3. If that does not settle it, a reader in Australia can complain to the Office of the Australian Information Commissioner and a reader in New Zealand to the Office of the Privacy Commissioner. Your own local regulator may also take it.
12

Changes and contact

This page changes when the service changes. Anything material is said inside the product before it takes effect.

Contact
Who
Operator
How
Sergei Kovalev, a natural person. 19 Pirosmani Street, Batumi, Adjara 6000, Georgia. There is no registered company.
Who
Privacy questions and requests
How
Sergei Kovalev is the privacy contact: contact@aera.rent or +995 585 890 610.
Who
Australia and New Zealand
How
Use the same contact. No separate local representative is currently appointed; this does not exclude any applicable legal obligation.