Get the app

Legal

Privacy Policy

What personal data HAI collects, why we collect it, who we share it with, and what rights you have over it.

Last updated Read the Terms of Service

This document is complete but not yet final. A few facts are shown as [LIKE_THIS] because we do not have them confirmed yet, and the notes marked Not settled yet flag the parts still under review. We would rather show you the gaps than fill them with something plausible.

1Introduction

This Privacy Policy explains what personal data HAI collects, why we collect it, who we share it with, and what rights you have over it.

HAI is a social coordination app. It helps you see which of your friends are free, suggest something to do, get a yes or a no, and meet up. Everything in this policy describes the app as it actually works today. Where a feature does not exist yet, it is not described here.

We have tried to write this in plain English. If anything is unclear, write to legal@joinhai.app and we will explain it.

2Who we are

HAI is a product and brand operated by IONESCU ANDREI V SOFTWARE PFA.

IONESCU ANDREI V SOFTWARE PFA is the data controller for the personal data described in this policy, within the meaning of the EU General Data Protection Regulation (GDPR).

Operator
IONESCU ANDREI V SOFTWARE PFA
Registered office
Bd. Al. Lăpușneanu nr. 179, bloc S5, scara A, Constanța, 900419, Romania
Fiscal identification code (CUI)
[CUI]
Trade Register registration number
[TRADE_REGISTER_NUMBER]
Privacy and legal contact
legal@joinhai.app
Phone
+40 721 333 445

We have not appointed a Data Protection Officer. We are not required to.

3Scope of this Privacy Policy

This policy covers the HAI mobile application for iOS and Android, and the parts of joinhai.app that relate to the app.

It does not cover:

  • other people's apps or websites that you reach from HAI — for example when you open a Google Maps or Apple Maps link to get directions to a place;
  • your device's operating system, or the app store you installed HAI from;
  • what other HAI users do with information you choose to show them.

4Personal data we collect

We collect four kinds of data:

  1. 1Data you give us — your email address, your password, your date of birth, optionally your phone number, your username and display name, and anything you add to your profile or type into the app.
  2. 2Data created by using HAI — friendships, rooms, the plans you propose, how you vote, when you say you're free, and your location while you choose to share it.
  3. 3Data your device provides — a push notification token if you allow notifications, and, if you agree to analytics, technical facts about your device.
  4. 4Data we read but do not keep — the phone numbers in your address book, if you allow contact access. These are used to find matches and then discarded.

The sections below go through each of these.

5Account and authentication data

Accounts in HAI are handled by Supabase Auth, a service we use as our processor.

Email and password. To create an account with an email address you give us an email and choose a password. We send a six-digit code to that address and you type it back in to confirm the account. Your password is sent directly to Supabase Auth, which stores it as a cryptographic hash. HAI never receives, stores or logs your password in readable form, and neither we nor anyone else can read it back.

Phone number (optional). You may add a phone number. We send a one-time code by SMS and you type it back to verify the number. Verifying a number does two things: it confirms you control it, and it makes your account findable by people who already have that number in their address book (see section 8). You can skip this step, and HAI works without it.

Sign in with Google or Apple. The app supports signing in with Google or Apple. If you use one of these, the provider tells us the identity information you agree to share with them — typically a provider account identifier and an email address. We do not receive your password for those accounts.

Sessions. Once you are signed in, your session tokens are stored on your device, encrypted with AES-256. The encryption key is held in the iOS Keychain or the Android Keystore. The tokens are not stored on your device in plain text.

What we hold: email address, phone number if you added one, a password hash, provider identity if you used Google or Apple, a display name carried over from sign-up, an internal account identifier (a random UUID), and account timestamps.

6Profile information

Your HAI profile holds:

  • a username (3–30 characters, letters, numbers and underscores);
  • a display name;
  • an optional profile picture;
  • an optional bio (up to 280 characters);
  • an optional city.

Who can see what. This distinction matters, so it is spelled out:

  • Your username, display name and profile picture can be seen by any signed-in HAI user who searches for you by name, or who has your phone number in their address book. That is how people find each other, and it is the trade-off of being findable.
  • Your bio and city are shown only to people you are friends with, people you share a room with, and people with a friend request pending between you in either direction.

Profile pictures are stored in a public bucket. When you upload a picture it is resized, converted to JPEG and stored with our hosting provider at an address that is not password-protected. This means anyone who has the exact address of the image file can open it, even without a HAI account. Within the app, the address is only handed to people who can already see your profile. Please do not use a profile picture you would not be comfortable being publicly accessible.

Your date of birth is not part of your profile. We ask for it once, when you create your account, purely to check that you are old enough to use HAI (see section 26). It is stored separately from your profile, in a part of our database our public API cannot reach; it is never shown to anyone, never returned to the app, and never used for anything else.

We do not ask for or store your gender, sexual orientation, religion, political views, health data, biometric data, or any other special category of data under Article 9 GDPR.

7Social and interaction data

Using HAI creates records of what you do in it:

  • Friendships — who sent a request, who accepted, and when.
  • Rooms — the groups you create or join, their names and pictures, your role in them, and when you joined. Rooms are private by default. A room can be made public by its admins, in which case any signed-in user can find the room by name and see its name, picture and member count — but never who is in it, what has been proposed, or where anyone is.
  • Proposals — the activity, title, proposed time, expiry and place of anything you suggest.
  • Votes — your yes or no on a proposal, visible to the other members of that room.
  • Availability — when you mark yourself free, for how long, which activities you're up for, and an optional short note. Visible to your friends and to people you share a room with.
  • Places — when you add a place by pasting a Google Maps link, HAI stores the place's name, category, address and exact coordinates. Places are a shared catalogue: every signed-in HAI user can see every place in it. Do not add a place you do not want other users to be able to find, such as your home address.
  • Invite codes — the codes you generate, who redeemed them, and when.
  • Notifications — the notifications sent to you, whether you have read them, and their delivery status.
  • Blocks — who you have blocked, and when. Only you can see your block list; the person you blocked is not told.
  • Reports — if you report someone or something, we store what you reported, the reason you chose, anything you wrote, and when. Only you and we can see your reports; the person reported is never told who reported them.

HAI has no chat or messaging feature. There are no private messages to store.

8Contacts and friend discovery

Giving HAI access to your contacts is entirely optional. You can skip it during set-up, turn it off later in your device settings, and use the whole app without it.

What happens if you allow it. HAI reads the names and phone numbers in your address book, on your device. It does not read email addresses, postal addresses, birthdays, contact photos or notes. Numbers are converted to international format on your device, de-duplicated, and sent in batches to our own server function, which:

  1. 1computes a keyed hash (HMAC-SHA256) of each number, using a secret key that exists only on our server and is never present in the app;
  2. 2compares those hashes against the hashes of numbers that HAI users have verified for their own accounts;
  3. 3returns the matching profiles — username, display name, profile picture, and whether you are already connected;
  4. 4discards the numbers and the hashes. Nothing from your address book is written to our database.

What we do store is a single keyed hash of your own verified phone number, so that other people's address books can find you. If you change your verified number, the old hash is replaced.

Being honest about hashing. A keyed hash of a phone number is pseudonymised data, not anonymous data. It still relates to an identifiable person, and we treat it as personal data throughout this policy. The key is what stops the stored set being reversed by brute force; it is not a claim that the data has stopped being about you.

Invitations. Contacts who are not on HAI are listed in the app so you can invite them. If you choose to invite someone, HAI opens your phone's own share sheet with a message and an invite code in it. HAI does not send messages to your contacts. You send them yourself, through whichever app you pick, and we do not keep a record of who you invited.

Legal basis. Reading your address book is done on the basis of your consent, which you give through the permission prompt and can withdraw at any time in your device settings. The subsequent matching, and the storage of the hash of your own number so that others can find you, are carried out to provide the friend-discovery feature you asked for (performance of a contract, Article 6(1)(b)).

9Location and map information

Location sharing in HAI is off until you turn it on, and this section describes exactly what happens when you do.

What is stored. When you share your location, HAI stores one row: your current coordinates, an accuracy figure in metres, who you have chosen to share with, when the sharing ends, and when the position was last updated. That row is overwritten every time your position updates.

We do not keep a location history. There is no table of past positions. When your position is updated, the previous one is gone.

Coordinates are exact. HAI does not blur, round or approximate your position. We would rather say this plainly than offer an "approximate area" setting that nothing actually enforces.

Who can see it. Only two audiences are possible, and you pick which:

  • Friends — the people you are connected to on HAI; or
  • Selected rooms — only the members of specific rooms you choose.

Anyone you have blocked is excluded in both directions. Strangers can never see your location. There is no "nearby people" feature, no public map, and no way for someone who is not your friend or room-mate to see where you are. This is enforced on the server, not only in the app.

How long it lasts. By default sharing expires — you choose one hour, four hours or eight hours, and the server will not accept a period longer than 24 hours. You can also choose "Until I turn it off", which has no expiry; the app says so on the button, and it is the one duration that keeps being shown to you while it is on.

Turning it off. Two options, and they mean different things:

  • Hide (on the Map tab) deletes the stored position entirely.
  • Setting your audience to "Nobody" in Settings takes you off every map immediately but leaves the row in place, unreadable by anyone, until it expires.

Background updates. While you are sharing, HAI keeps your pin current even when the app is not open, using your device's background location service. Updates happen roughly every 75 metres of movement, or every couple of minutes on Android. This is deliberately visible: iOS shows its blue location indicator, and Android shows a permanent notification saying "Sharing your location — tap to stop". Background updates stop when you stop sharing, when the sharing period expires, or when you revoke the permission.

Other uses of location. The app also reads your current position while you are using it, in order to centre the map and to work out how far away a place is. Unless you are sharing, that reading is used on your device and is not sent to our servers.

Maps. Map tiles are provided by Mapbox. Loading a map means Mapbox receives a request for the area you are looking at, along with your IP address. Mapbox's own usage-and-location telemetry is switched off in HAI — we never turn it on.

Legal basis. Location sharing is based on your consent, given by choosing to share and reinforced by the OS permission. You can withdraw it at any time, in the app or in your device settings.

10Device information

Push tokens. If you allow notifications, we store a push token issued by Expo for each device you use, along with the platform (iOS or Android), a device identifier, and when it was last seen. This is what lets us deliver a notification to the right device. Tokens are removed when a device is unregistered, and disabled when the push service tells us the device no longer exists.

Technical device information for analytics. Only if you agree to analytics (see section 12), our analytics provider records: device brand, manufacturer, model, device type, operating system name and version, app version and build number, language, region, time zone, and whether the device is physical or a simulator.

Network information. Like any internet service, our hosting provider, our analytics provider and our map provider receive your IP address and standard connection information when your device talks to them. This is inherent to how the internet works and is used to route responses, protect against abuse, and keep the service running.

Crash reporting. HAI does not include a crash-reporting or error-monitoring SDK. If your device sends a crash report, it goes to Apple or Google under their own terms, not to us.

11User-generated content

The content you create in HAI is: your profile picture, your username, display name, bio and city, room names and room pictures, proposal titles, availability notes, and the details of places you add.

We store this so we can show it to the people it is meant for. We do not use it to train machine-learning models, we do not sell it, and we do not use it for advertising.

HAI does not use automated content moderation or automated scanning. Content is reviewed when somebody reports it. You can report a person, a room or a plan from inside the app — open it, choose "Report", pick a reason and add anything you want us to know. Reporting somebody also blocks them by default, and you can turn that off in the same step. A person reads every report and acts on the ones that break our Terms.

You can also block anyone from their profile without reporting them, and manage the list in Settings → Privacy → Blocked accounts. Blocking is silent — the other person is not told — and it ends any friendship between you.

If you would rather write to us, support@joinhai.app reaches the same place.

12Analytics

HAI uses PostHog for product analytics — to understand which parts of the app people use, where they get stuck, and what to build next.

Analytics is off unless you say yes. We ask you once, on a dedicated screen during set-up. Until you agree, the analytics library captures nothing at all — not a screen view, not an app-open event. This is enforced inside the library, not by us remembering to check.

If you agree, we record:

  • Events: signing up, verifying a phone, answering the permission prompts, sending and accepting friend requests, creating and joining rooms, creating and voting on proposals, starting and stopping location sharing, setting yourself free, opening a notification, and changing your analytics setting.
  • Screen views, recorded as generic screen names such as "Room" — never as a specific address containing an identifier.
  • Person properties: your account identifier, email address, username, whether you have a profile picture and bio, when your profile was created, and the device information listed in section 10.
  • Your answers to the four onboarding survey questions (how often you go out, who you go out with, what you like doing, and where you heard about HAI).

What analytics never records: message text, other people's display names, phone numbers, email addresses other than your own, and coordinates of any kind. When you start sharing your location, the event records only the audience and the duration — never where you are.

Session replay and automatic tap-capture are switched off.

The survey and consent. The survey is asked before the analytics question. Your answers are held on your device until you answer the analytics question. If you say yes, they are sent then. If you say no, they are deleted from your device without ever being sent.

Changing your mind. Settings → Privacy has the same switch. Turning it off stops capture immediately.

Legal basis: consent (Article 6(1)(a)).

13Push notifications

If you allow notifications, HAI sends them when something happens that concerns you: someone proposes a plan in one of your rooms, someone votes yes, a plan is confirmed or cancelled, someone sends you a friend request, or someone accepts yours.

Notifications are generated by our database, queued, and delivered through Expo's push service, which hands them to Apple's push service on iOS or Google's on Android. The notification's title and body may contain a display name and the title of a plan, because that is what makes the notification useful — which also means that text passes through Expo, Apple or Google in transit.

You can turn notifications off at any time in your device settings, and mute individual rooms in the app.

Legal basis: delivering the notifications you asked for is part of providing the service (contract); the OS permission is the mechanism by which you switch it on.

14How we use personal data

Create and secure your account
So you can sign in and only you can
Show your profile to the people who can see it
So your friends know who they're looking at
Maintain your friendships and room memberships
The app is the social graph
Deliver proposals, votes, plans and availability
The core purpose of HAI
Show your position to the audience you chose, while you choose
The map feature
Match your contacts against HAI accounts
So you can find friends who are already here
Send notifications
So plans reach you in time
Keep the service running, prevent abuse and investigate problems
So HAI works and stays usable
Understand how the app is used, in aggregate
To improve it — only with your consent
Check that you are old enough to use HAI
So the app is not offered to children below the minimum age
Review content and accounts that are reported to us
So HAI stays usable and people can be protected from each other
Answer your support and privacy requests
Because you asked, and because the law requires it

We do not: sell personal data, share it with advertisers or data brokers, use it for behavioural advertising, or use it to make automated decisions that produce legal or similarly significant effects on you.

Creating and maintaining your account; authentication
Contract — 6(1)(b)
Email and phone verification
Contract — 6(1)(b)
Your profile, and showing it to those permitted to see it
Contract — 6(1)(b)
Friendships, rooms, proposals, votes, availability, invites, places
Contract — 6(1)(b)
Delivering push notifications you have enabled
Contract — 6(1)(b)
Reading your address book
Consent — 6(1)(a)
Matching contacts and storing the hash of your own number so others can find you
Contract — 6(1)(b), to provide the discovery feature you enabled
Sharing your location with your chosen audience
Consent — 6(1)(a)
Product analytics and survey answers
Consent — 6(1)(a)
Keeping the service available; security, abuse prevention, fraud prevention, operational logging
Legitimate interests — 6(1)(f). Our interest is in running a service that is not abused; we balance it against your interests by keeping logs limited to what our providers generate as part of running the infrastructure
Handling reports of abuse, blocking, and enforcing our Terms
Legitimate interests — 6(1)(f), and protecting the rights of other users
Verifying that you meet the minimum age
Legal obligation — 6(1)(c), and legitimate interests — 6(1)(f) in not offering a location-sharing service to children
Responding to lawful requests, and retention required by law
Legal obligation — 6(1)(c)

A permission prompt on iOS or Android is not by itself GDPR consent. Where we rely on consent, we ask separately and explain what for — that is what the analytics screen and the sharing controls are.

16When we share personal data

We share personal data in four situations:

  1. 1With other HAI users, according to the visibility rules described above — your friends, your room-mates, people searching for your username, and people who have your number in their contacts.
  2. 2With our service providers (processors), listed in section 17, who process data on our instructions.
  3. 3Where the law requires it — for example in response to a valid legal order.
  4. 4To protect people — where we believe in good faith that disclosure is necessary to prevent serious harm, or to establish, exercise or defend legal claims.

We do not sell personal data, and we have never done so.

17Service providers (processors)

Supabase (Supabase, Inc.)
Authentication, database, file storage, server functions — our core infrastructure. Receives effectively all the data in this policy: account data, profile, social graph, location while shared, profile pictures, notifications, contact hashes
Expo (650 Industries, Inc.)
Push notification delivery, and app build/update infrastructure. Receives push tokens and notification content
Apple (APNs)
Delivering notifications on iOS. Receives device token, notification content
Google (Firebase Cloud Messaging)
Delivering notifications on Android. Receives device token, notification content
Mapbox (Mapbox, Inc.)
Map tiles and styles. Receives requests for map areas, and your IP address. Mapbox's own analytics telemetry is disabled in HAI
PostHog
Product analytics — only where you consented. Receives account identifier, email, username, device information, product events, survey answers
SMS provider
Delivering the one-time code for phone verification. Receives your phone number and the code
Email provider
Delivering account confirmation and password reset codes. Receives your email address and the code
Google / Apple
Sign-in, if you use it. Receives the identity information you agree to share

Not settled yet

Pending review: the names of the SMS and transactional-email providers must be filled in before publication, and data processing agreements must be in place with every provider above.

18International data transfers

HAI is operated from Romania and serves users in the European Union. Some of our providers are established outside the EEA, principally in the United States, which means some personal data may be transferred outside the EEA.

Where that is the case, transfers must be covered by an appropriate safeguard under Chapter V GDPR — such as Standard Contractual Clauses, or a provider's certification under the EU–US Data Privacy Framework.

Not settled yet

Pending review: the hosting region of our Supabase project, the analytics region, and the transfer mechanism relied on for each provider have not yet been confirmed and must be verified and stated here before publication. We will not name a safeguard we have not checked.

19Data retention

We keep personal data for as long as we need it for the purpose it was collected for.

Account, profile, friendships, room memberships
For as long as your account exists
Proposals, votes, plans
For as long as the room exists, or until deleted with your account. Expired proposals are marked expired rather than removed
Location
Overwritten in place; deleted when you tap Hide, and removed with your account. There is no history
Notifications
Read notifications older than 30 days and any notification older than 90 days are deleted
Push tokens
Until the device is unregistered or the push service reports the device as gone
Hash of your verified phone number
For as long as your account exists; replaced if you change the number
Profile pictures
Until replaced or your account is deleted
Places you add
The place stays in the shared catalogue after your account is deleted, with your name removed from it
Availability entries
Deleted 30 days after the window ends
Invite codes
Deleted 90 days after being redeemed, or 30 days after expiring unused
Reports
Kept while open. Deleted two years after being resolved, or immediately if the account they concern is deleted
Analytics data
For our analytics provider's retention period
Infrastructure and security logs
For our providers' retention periods

These periods are enforced by scheduled jobs in our database, not by hand.

Not settled yet

Pending review: we have not yet fixed retention periods for analytics data or for our providers' infrastructure logs.

20Account deletion

You can delete your HAI account from inside the app: Settings → Delete account.

Deleting your account permanently removes: your login (email address, phone number, password hash and any linked Google or Apple identity), your profile, your profile pictures, your friendships and blocks, your room memberships, your availability, your stored location and sharing settings, the proposals you created, your votes, your push tokens, the notifications addressed to you, the hash of your phone number, and the invite codes you created.

Some things behave differently, and it is worth knowing which:

  • Rooms you created are handed over rather than deleted: ownership passes to another admin, or to the longest-standing member if there is no other admin. A room you created and were the only member of is deleted, along with its plans and its picture. Your own membership disappears either way.
  • Places you added stay in the shared place catalogue, with your name removed from them. They are part of a shared reference list that other people's plans point at.
  • Reports you filed are deleted with your account. Reports other people filed about you are deleted too, when your account goes.
  • Notifications already delivered to other people may still contain your display name in their text, until those notifications are pruned.

We may also need to keep a limited amount of information for a limited period where we have a legal obligation to, or to establish, exercise or defend legal claims — for example if there is an unresolved abuse complaint.

Analytics. If analytics is configured with deletion credentials, deleting your account also asks our analytics provider to delete your person record and the events attached to it. That deletion is processed by them asynchronously rather than instantly. If you would like confirmation, or if you want it done for an account you have already deleted, write to legal@joinhai.app.

21Security

We use reasonable technical and organisational measures designed to protect personal data against loss, misuse and unauthorised access.

Measures we can describe because they are in the code:

  • All traffic between the app and our servers is encrypted in transit (HTTPS).
  • Passwords are stored only as hashes, by our authentication provider. We never see them.
  • Your session tokens are encrypted on your device with a key held in the iOS Keychain or Android Keystore.
  • Access to database rows is controlled by row-level security policies on the server, so what you can read is decided by the database and not only by the app.
  • Location visibility, profile visibility and blocking are enforced server-side.
  • Identity data — the hash of your phone number and your invite codes — is held in a database schema that is not exposed through our public API at all.
  • The key used to hash phone numbers exists only in our server environment and is never shipped inside the app.
  • Profile pictures are size- and format-limited on the server, not only in the app.

No service can promise perfect security, and we do not. If a personal data breach occurs that is likely to result in a risk to your rights and freedoms, we will notify the competent supervisory authority within 72 hours where required, and notify affected users where the law requires it.

22Your permissions and choices

Turn contacts access on or off
Your device settings. HAI works without it
Turn location access on or off
Your device settings, and the Hide button on the Map tab
Choose who sees your location
Settings → Privacy: friends, selected rooms, or nobody
Choose how long you share for
The duration options when you start sharing
Turn notifications on or off
Your device settings; individual rooms can be muted in the app
Turn analytics on or off
Settings → Privacy
Edit or remove your profile picture, bio and city
Settings → Edit profile
Delete your account
Settings → Delete account

23Your GDPR rights

If you are in the EU or EEA, you have the following rights over your personal data:

  • Access — to be told whether we process data about you, and to receive a copy of it (Article 15).
  • Rectification — to have inaccurate data corrected (Article 16). Most profile data you can correct yourself in the app.
  • Erasure — to have your data deleted (Article 17). You can do most of this yourself with Settings → Delete account.
  • Restriction — to have processing limited in certain circumstances (Article 18).
  • Portability — to receive the data you gave us in a structured, commonly used, machine-readable format, and to have it transmitted to another controller where technically feasible (Article 20).
  • Objection — to object to processing based on our legitimate interests, on grounds relating to your particular situation (Article 21).
  • Withdrawing consent — where we rely on consent, to withdraw it at any time (Article 7(3)). Withdrawing consent does not affect processing carried out before you withdrew it.
  • Not to be subject to automated decision-making producing legal or similarly significant effects (Article 22). We do not carry out such decision-making.

24How to exercise your rights

Write to legal@joinhai.app from the email address on your HAI account, or by post to the registered office in section 2.

Tell us which right you are exercising and what you want. We may ask for information to confirm that the request really comes from you — we are not going to hand somebody's data to whoever asks for it.

We will respond within one month. If your request is complex, or you have made several, we may extend that by up to two further months and will tell you why within the first month.

There is no charge, unless a request is manifestly unfounded or excessive.

25Complaints

If you think we have handled your personal data unlawfully, please tell us first — most things are quicker to fix directly.

You also have the right to complain to a supervisory authority. In Romania that is:

Autoritatea Națională de Supraveghere a Prelucrării Datelor cu Caracter Personal (ANSPDCP)B-dul G-ral. Gheorghe Magheru nr. 28-30, Sector 1, 010336 Bucharest, Romaniawww.dataprotection.ro

If you live in another EU or EEA country, you may complain to the supervisory authority there instead.

26Children and age eligibility

You must be at least 16 to use HAI.

Sixteen is the age at which, under Romanian law implementing Article 8 GDPR, a child's own consent to an information society service is valid — so HAI does not need, and does not ask for, parental consent.

How we check. We ask for your date of birth when you create your account, and we refuse to create an account for anyone below 16. We store the date of birth in a separate part of our database that our public API cannot reach at all; it is never shown on your profile, never returned to the app, and never used for anything except this check.

We do not knowingly collect personal data from anyone under 16. If you believe someone below that age is using HAI, tell us at legal@joinhai.app and we will close the account and delete its data.

27Changes to this Privacy Policy

We may update this policy — for example when HAI gains a feature that handles data differently. The "Last updated" date at the top always tells you when.

If a change materially affects how we use your personal data, we will tell you in the app or by email before it takes effect, and where the change requires your consent we will ask for it.

Previous versions are available on request from legal@joinhai.app.

28Contact

Privacy, GDPR requests, legal notices
legal@joinhai.app
Account problems, technical support, general questions
support@joinhai.app
Phone
+40 721 333 445
Post
IONESCU ANDREI V SOFTWARE PFA, Bd. Al. Lăpușneanu nr. 179, bloc S5, scara A, Constanța, 900419, Romania

HAI is a product and brand operated by IONESCU ANDREI V SOFTWARE PFA.