Goro Terms of Service

Effective date: 2026-08-01 Last updated: 2026-08-01

These Terms of Service ("Terms") are a contract between you and PROMPTIFY S.R.L., a company registered in Romania, registered office at Strada Prof. Nicolae Oblu, Nr. 24A, Bloc B2A, Etaj 2, Ap. 22, Municipiul Iasi, Judetul Iasi, Romania, trade register number J22/1745/06.06.2023, company registration number (CUI) 48270068, EUID ROONRC.J22/1745/2023, VAT number RO48310979 ("Goro", "we", "us"). They govern your use of the Goro gateway at usegoro.ai, app.usegoro.ai, api.usegoro.ai and mcp.usegoro.ai, and any API, MCP server or documentation we provide (together, the "Service").

By creating an account, generating an API key, or calling the Service, you agree to these Terms. If you do not agree, do not use the Service.

Three other documents form part of this agreement and are incorporated by reference:

The Acceptable Use Policy, published at https://usegoro.ai/legal/acceptable-use, which sets hard limits on what you may do with the data endpoints.
The Privacy Policy, published at https://usegoro.ai/legal/privacy, which explains what we do with data.
The Data Processing Agreement, published at https://usegoro.ai/legal/dpa, which is the Article 28 contract covering the personal data you send through the Service.

If there is a conflict, the AUP wins on questions of permitted use, the DPA wins on the processing of personal data under Article 28, and these Terms win on everything else.

1. What the Service is

Goro is a pay-per-call gateway. It gives an AI agent or an application one account, one API key, one balance and one billing model for calling web data tools.

Most endpoints in the Goro catalog map one to one onto a third-party actor hosted on the Apify platform (apify.com). The image and video endpoints run on kie.ai, and the voice endpoints run on Fish Audio. When you call an endpoint:

We validate your input against that endpoint's published JSON schema, and fill in any defaults the schema declares.
We forward the result to the execution provider. We do not rename your fields, narrow your query, or turn options on or off beyond filling in those published defaults.
The provider runs the tool. On Apify the actor is written and maintained by an independent developer, not by us.
We return the tool's output untouched, capped at 5,000 items per run.

Point 1 is worth reading twice. A field you leave out is filled with the default our schema declares, and the filled copy is what we send upstream. On some endpoints that default changes what comes back and how much of it: twitter.followers returns the follower list by default and the smallest request the tool accepts is 200 followers, and the LinkedIn search endpoints have a profile-detail mode that defaults to the least revealing of the options. inspect shows you every default before you run anything, and setting a field yourself always overrides ours.

What we sell is authentication, a single prepaid wallet, budgets, discovery across the catalog, and one predictable billing model. We do not sell a cleaned, normalized or verified dataset, and we do not sell the underlying data itself. Read section 8 carefully, because it is the part of this agreement people most often assume says something it does not.

The catalog, the endpoints in it, and their schemas are listed in the web app at app.usegoro.ai. They change.

2. Eligibility and accounts

The Service is offered for business and professional use only. By using it you confirm you are using it in the course of a trade, business, craft or profession, that you are at least 18, and that you have authority to bind the entity you are acting for. The Service is not offered to consumers.

We do not check this at signup. There is no age gate and no eligibility check in the signup flow, so the paragraph above is a warranty from you rather than a control on our side. If we find you are using the Service as a consumer, we may close your account and refund your unused cash balance. Until we do, the mandatory consumer law of the country you live in applies to you whatever the rest of this document says. That is not generosity, it is how consumer law works, and sections 7, 11 and 16 are written on the assumption that you are a business.

You sign in with Google or with an email one-time code, through Supabase Auth. One account gets one workspace. You are responsible for everything done under your account, including by your agents, your software and your team.

You must give accurate information and keep it current. We may refuse, suspend or close an account at our discretion, subject to section 12.

3. API keys and account security

Your API key is your credential. It looks like goro_live_ followed by a random string.

We show your key once, at creation, and never again. We store only a SHA-256 hash of it, plus the first 12 characters for display. We cannot recover a lost key. We can only revoke it and issue a new one.
Anyone holding a valid key can spend your wallet balance. Treat it like a payment credential.
You are responsible for keeping keys secret, for rotating them, and for revoking any key that may have leaked. You can revoke keys at any time in the web app.
You are liable for all usage and all charges incurred with your keys, including usage you did not intend, until the key is revoked. We do not reverse charges for leaked keys.

Rate limits apply per key and per workspace, and a separate cap limits how many runs one workspace can have in flight at once. Responses tell you where you stand against them. See section 9.

If you connect through the MCP server, the same applies to OAuth tokens issued against your account.

4. The wallet, and what credits are

Goro runs on a prepaid wallet. You add funds, then calls draw down against the balance.

All balances are held in US dollars. USD only. Checkout is priced in USD. In the rare case that a payment settles in another currency, we do not credit it to your wallet, because that would mean converting it at a rate you never agreed to. We refund it in full instead. See section 7.
There are no subscriptions. Every payment is a one-time top-up. We do not create recurring plans, and no plan, seat or monthly fee exists.
Wallet credit is not money, is not a deposit, and is not e-money. It is a prepaid balance redeemable only against the Service.
Wallet credit is not withdrawable, but unused cash is refundable. You cannot cash it out to a bank account, transfer it to another account, or spend it anywhere but here. What you can do is ask us to return what is left to the card you paid with. Section 7.1 is the whole of that, including its limits.
Credit does not accrue interest.
Your cash balance does not expire. Only promotional credit expires, under section 6.
The ledger in your account is the record. It is append-only, and every balance change references either a run or a Stripe payment. If your view of the balance and the ledger disagree, the ledger governs.

Top-ups run through Stripe hosted Checkout. Card details never reach our servers. Presets are $5, $20 and $100, and custom amounts are allowed from $5 up to $10,000 per transaction.

Card storage, and this happens whether or not you want automatic top-ups. Every top-up checkout session is set up so that Stripe saves your card against your customer record for possible later off-session use. Not just the first one. The card is held by Stripe, never by us. There is no self-serve way to remove a stored card. Ask us at hello@usegoro.ai and we will remove it.

Automatic top-ups. You can turn on a rule that tops your balance back up without you present. It is off unless you turn it on, it needs a saved card, and you set both numbers yourself on the Wallet page: the balance that triggers a top-up (at least $5) and the balance it tops you back up to (at least $10 above the trigger). When a run leaves your available balance below your trigger, we charge the saved card the difference. You can switch it off in the same place at any time, and switching it off takes effect immediately.

Two things about it we would rather say here than let you find out from a statement. We do not notify you before or after an automatic charge, because the product has no outbound email at all. And the charge is described on your statement as a Goro wallet auto-reload, and appears in your ledger like any other credit. If either of those is not acceptable to you, leave the rule off, and top up by hand.

5. How a call is priced and charged

Every endpoint publishes how it is priced, in the catalog and in inspect. There are three shapes today, and the catalog tells you which one applies before you call.

Cost-plus, which is how the scraping and search endpoints work. You pay a published multiple of what the run actually cost us at the execution provider, clamped to a published floor and ceiling for that endpoint. It is not a list price we invented.
Metered, which is how the video and speech endpoints work. You pay a published rate per measured unit of your own input, such as a second of video or a thousand bytes of text, with a floor and a maximum number of units.
Per call, which is how the image endpoints and the voice management calls work. A published flat price for the call.

Whichever shape applies, the money moves the same way:

Hold. Before the run starts, we estimate the cost from your request and place a hold on your wallet. The hold is bounded by that endpoint's published minimum and maximum. The maximum is a backstop, not the normal charge.
Capture. When the run completes, we compute the real charge, never above the hold. We capture that amount and release the rest of the hold back to your wallet.
Release. If the run fails, times out, is stopped, is blocked by one of your budgets, or never starts, we release the entire hold and charge you nothing.

Additional rules, all enforced in code:

Failed calls are not charged. This is not a goodwill policy, it is how the ledger works.
A run can never be charged twice. Capture and release are idempotent per run.
Promo credit is spent before cash on every hold.
If your balance is not enough for the hold, the call is rejected with HTTP 402 and nothing is debited. No run starts, and you cannot go negative.
You can set an optional daily or monthly budget cap that either blocks or notifies. Blocked runs are not charged.

Read this part. A run that succeeds is charged even if it returns nothing useful:

A successful run with zero results still costs money. Actors commonly charge a start fee for every run, plus usage, and our charge is a multiple of that real cost with a per-endpoint floor. If you ask for a profile that does not exist, or a search that matches nothing, the run completes normally, returns an empty list, and bills.
Output is capped at 5,000 items per run. A run truncated at that cap is charged on its real cost, not on the number of items you received. The response does not flag truncation, so a run that returns exactly 5,000 items may have had more available.
If the provider does not report a usable cost for a run that otherwise succeeded, we charge the endpoint minimum. This happens when the provider returns no cost figure at all, or returns exactly zero, which we treat as unreliable rather than free. The minimum for each endpoint is published in the catalog, so you can always see the worst case in advance.
Provider costs, and therefore your costs, depend on what the third-party tool charges. See section 8.

If we charge you because our own code failed, that is our error and we will credit it back. Our settlement path has a fallback that charges the endpoint minimum when our billing logic itself fails on an otherwise successful run, so that a hold is never left stranded on your wallet. That is an operational safeguard, not a charge you owe. Tell us and we will credit it. We will not keep it.

Changing prices and the catalog. We may change the markup, the per-endpoint floors and caps, and the catalog at any time. A change to the markup or to an endpoint's floor or cap takes effect when it is published in the catalog at app.usegoro.ai, and applies only to runs started after that. It never applies retroactively to runs already charged. Adding, changing or removing an endpoint can happen with no advance notice at all, because the tool underneath it can change or disappear with no notice to us. See section 8. The price that applies to a call is the one published at the moment you make it, so read the price at call time rather than trusting a number you cached.

6. The signup promo

New accounts get $1.00 in promo credit, added automatically on first sign-in. It requires no card.

The promo expires 30 days after it is granted. On expiry the unused balance is zeroed. It is not extended, restored or paid out.
Promo credit is spent before your cash balance.
It is not cash, is never withdrawable, and is never refundable.
One promo per account. In practice that means one per sign-in identity, and we know that plus-addressed emails and disposable domains can each get their own. We may withhold or reclaim promo credit, and close the accounts involved, where we believe someone is creating multiple accounts to farm it.

7. Refunds

Two different things happen when a call goes wrong, and only one of them is a refund.

A call that fails is never charged in the first place. Before a call runs we place a hold on your balance, and we only convert that hold into a charge once the call has actually completed and we know what it cost. If the call fails, times out, or you stop it, the whole hold is released and nothing is taken. If it completes but returns nothing and cost us nothing, it bills nothing. This is automatic, it needs no request from you, and it is not a refund.

Everything below is about money that has already left your card.

7.1 Unused balance

You can ask for your unused cash balance back at any time. Email hello@usegoro.ai. We return it to the card you paid with.

Four limits, and they are the honest kind:

We refund what is left, not what you spent. Money already spent on calls is gone upstream: we paid the execution provider for those runs on your instruction, and we cannot recover it.
Promotional credit is not included. It was never paid for, so there is nothing to return.
Card networks stop accepting refunds against an old payment after a while, typically around 180 days. Past that a refund to the original card may not be possible at all, and we would have to agree another route with you.
Refunds are not self-service and part of the work is manual. There is no button. A person issues them. For some payments we have a tool that returns the money and adjusts your ledger in one step; for a card top-up made through hosted checkout we do the same thing in two, the refund in Stripe and the ledger entry by hand. Either way the money comes back and your balance is reduced by exactly what was returned. It is not instant.

7.2 Where we refund without being asked

If we stop offering the Service, or we close your account for any reason other than your breach of these Terms or the AUP, we return your unused cash balance. We are not going to keep money you prepaid for a service we decided to stop delivering.
If a payment settles in a currency other than US dollars, we refund it in full rather than crediting a converted amount at a rate you never agreed to. See section 4.
If our own billing code charged you in error, we put it back. See section 5.
If you change your mind within 14 days of a top-up and have not spent any of it, we refund it in full. We do not think you should have to argue about a purchase you have not used.

7.3 What we do not refund

Calls that completed and returned data you did not find useful. The call ran and cost us money to run.
Charges arising from a third-party tool's own behaviour, pricing or output quality. See section 8.
Usage on a key you did not keep secret. See section 3.
Expired promotional credit.

7.4 If you are a consumer

Section 2 says this Service is sold to businesses. If you are nonetheless a consumer under the law of the country you live in, that law gives you rights this section cannot take away, including a statutory right to withdraw from a distance contract. Those rights apply in addition to everything above, and where they conflict with it, they win.

8. Third-party tools, and what we do not control

This is the most important section in this document.

We resell execution of software we did not write and do not control. Most endpoints are a third-party actor published on Apify by an independent developer. We are not that developer's agent, and they are not ours. Apify hosts them. The image and video endpoints run at kie.ai and the voice endpoints at Fish Audio, and the same principle applies to both. We run your call under our own account with each provider, which means the provider sees us as its customer, not you.

You accept, specifically, that:

A tool can break. It can stop working, return errors, return partial data, or return nothing at all, at any time and without notice, usually because the site it reads from changed.
A tool can disappear. Its author can deprecate it, restrict it, or remove it. If that happens, the matching Goro endpoint stops working and we may remove it from the catalog with no notice.
A tool's price can change. Its author sets the price. On the cost-plus endpoints we bill a multiple of the real cost of your run, so a price rise upstream raises what your call costs immediately, without us changing anything. On the metered and per-call endpoints the rate is one we publish, so a rise upstream reaches you as a change to the published price instead.
A run can bill a start fee even when the result is empty, as described in section 5.
Output shape can change. We return the tool's items untouched, so if the author changes the fields, your integration sees that change directly. We do not maintain a stable normalized schema across tools.
We do not verify the data. We do not check that a profile, a review, a phone number, an email address or a price is accurate, current, complete, or that the person or business it describes is who the tool says it is.

Your input goes upstream as you wrote it, plus our declared defaults. Whatever you send us, including any name, URL, email address or search phrase, is sent to the execution provider and to the tool. We do not store it. Do not send anything through the Service that you are not entitled to send to a third-party processor.

Upstream terms apply to you, as far as you can see them. We do not tell you which actor is behind an endpoint. Actor identifiers are deliberately withheld from discover, inspect and run, so we do not ask you to comply with a licence we keep from you, and we carry that risk ourselves. What you are responsible for is:

Apify's published terms of service and acceptable use policy, and the equivalent terms of the other execution providers, which apply to the traffic you generate through us.
The terms, robots directives and technical restrictions of any site or platform the data comes from. You know which platform you are pulling from, because the endpoint name says so.
Everything in the AUP.

If your usage causes us to breach an upstream agreement, or gets one of our provider accounts restricted, suspended, throttled or billed for abuse, that is a material breach of these Terms and you indemnify us for it under section 11.

9. Acceptable use and limits

Your use of the Service is governed by the Acceptable Use Policy, published at https://usegoro.ai/legal/acceptable-use, which is part of this agreement. Read it before you touch the people-data endpoints.

In summary, and without limiting the AUP, you must not use the Service to:

Break any law that applies to you, to the people whose data you collect, or to us.
Collect or process personal data without a valid legal basis, or in breach of data protection law. Several endpoints return personal data at scale, including names, employment history, contact details, follower graphs, comments and reviews. Deciding whether you may lawfully collect that data is your responsibility, not ours.
Harass, stalk, dox, profile, discriminate against or endanger anyone.
Send unlawful direct marketing, including to contact details obtained through the Service. Note that the AUP goes further than "unlawful" here, and bans cold outreach built on Goro-sourced contacts outright.
Circumvent authentication, paywalls or access controls, or collect data that is not publicly accessible.
Resell raw access to the Service in a way that lets a third party call it under their own name without agreeing to these Terms, unless we have agreed that in writing.
Attack the Service or the upstream platforms, including through excessive concurrency or automated retries designed to evade limits.

You are responsible for having a lawful basis for every call you make, for the notices and rights of the people whose data you collect, and for responding to those people if they contact you.

Limits. Rate limits apply to the authenticated API, per API key and per workspace, with a tighter limit on starting runs than on reading. A separate cap limits how many runs one workspace can have in flight at once. Responses carry headers showing the applicable limit, what you have left and when it resets, so you can see where you stand without having to hit it. The numbers themselves are operational and we may change them at any time, with or without notice, to protect the Service or an upstream provider, and we may add per-endpoint restrictions or volume caps on the same basis. We do not commit to a specific number in this contract.

10. Disclaimers

The Service is provided "as is" and "as available", with all faults.

To the maximum extent permitted by law, we disclaim all warranties, express, implied or statutory, including merchantability, fitness for a particular purpose, non-infringement, and any warranty arising from course of dealing or trade usage.

Without limiting that, we do not warrant:

That any data returned is accurate, complete, current, lawful to use, or fit for any purpose.
That any endpoint, tool or upstream source will remain available, remain priced as it is, or keep returning the same fields.
That the Service will be uninterrupted, timely, secure or error free.
That any particular run will return results, or any particular number of results.

There is no service level agreement and no uptime commitment. We may perform maintenance, change or remove endpoints, and change the Service, at any time.

Nothing in these Terms excludes liability that cannot be excluded by law, including for fraud, fraudulent misrepresentation, or death or personal injury caused by negligence.

11. Limitation of liability, and indemnity

To the maximum extent permitted by law:

Neither party is liable for indirect, incidental, special, consequential or punitive damages, or for loss of profit, revenue, business, goodwill, anticipated savings, or data, however caused. This exclusion does not apply to your obligations under the indemnity below, or to your obligation to pay for usage. Fines, penalties, regulatory action and third-party claim costs covered by the indemnity are recoverable in full, and neither this bullet nor the cap below limits them.
Our total aggregate liability arising out of or relating to the Service and these Terms, in contract, tort, or otherwise, is limited to the greater of (a) the amounts you actually paid us in the 12 months before the event giving rise to the claim, and (b) USD 100. Note the shape of that: "greater of" makes USD 100 a floor rather than a ceiling, so a customer who has spent $4,000 with us has a $4,000 cap.
We are not liable for the acts, omissions, pricing, availability or output of any execution provider, of any third-party tool author, or of any site the data comes from.

Two things this cap does not do. It does not limit either party's liability where the law does not allow it to be limited. And it has no effect on Article 82 of the GDPR, which makes a processor directly liable to a data subject for damage caused by its own breach of processor obligations. A contract between you and us cannot cap what a third party is owed.

You indemnify us. You will defend, indemnify and hold us harmless against any claim, loss, fine, penalty, regulatory action or cost, including reasonable legal fees, arising from: your use of the Service; the data you collect through it and what you do with it afterwards; your breach of these Terms, the AUP, the DPA, an execution provider's terms or a tool licence; and any claim by a person whose personal data you collected through the Service.

12. Suspension and termination

You can stop using the Service at any time and revoke your keys. To close your account, contact hello@usegoro.ai. There is no self-serve closure, so this is a manual process on our side.

We may suspend or terminate your access, in whole or in part, immediately and without notice, if:

You breach these Terms or the AUP, or we reasonably believe you have.
Your usage puts one of our provider accounts, another provider relationship, or the Service at risk.
We are required to by law, by a regulator, or by an upstream provider.
We stop offering the Service, or the endpoint you rely on.

On termination: your keys stop working, in-flight runs may be cancelled and their holds released, and your right to use the Service ends. Sections 7, 8, 10, 11, 13 and 14 survive.

Your balance on termination. If you close your account, or we close it for any reason other than your breach, we refund your unused cash balance under section 7. If we close it because you breached these Terms or the AUP, your unused balance is forfeited. Promo credit is never refunded.

Your data on termination. Terminating does not by itself delete your account record. Your run inputs were never stored, and your run outputs are deleted within 24 hours of each run whether you terminate or not, so there is normally nothing of that kind left to remove. What remains is your account, workspace, keys, ledger and run metadata, and Privacy Policy section 9 sets out what we delete on request and what we have to keep.

We may discontinue the Service entirely on reasonable notice, and if we do, section 7.2's refund applies.

13. Data, privacy, and rights in content

Our handling of personal data is described in the Privacy Policy.

What we store, and what we do not. We do not store your run inputs at any point: they are validated, priced and passed to the execution provider, and there is no column in our database that could hold one. We store your run outputs as a handover buffer only, so that a slow run stays collectable, and they are deleted shortly after you first fetch them and unconditionally 24 hours after the run finished, whichever comes first. We store metadata about every run: which endpoint, when, what it cost, how many rows came back, and any error. We store the raw text of your discover queries when nothing in the catalog matches them, for 90 days. We use all of this to operate the Service, to bill you, and to support and debug it.

Deletion. The retention above is automatic and needs no request from you. Where you want something removed sooner, or want your account and its data deleted, email hello@usegoro.ai. There is no self-serve deletion and no closure flow, so it is done by hand. Privacy Policy sections 6 and 9 have the detail, including what we have to keep for accounting purposes and why.

Do not send us data we should not be holding. Do not put special-category personal data into a run input, meaning data about health, racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetics, biometrics, sex life or sexual orientation, and do not use the Service to assemble it. Do not send credentials, session tokens or cookies. Your input is forwarded to a third party, so it leaves our system as you wrote it.

Rights in what you send and what you get back.

You keep whatever rights you have in your input. You grant us a non-exclusive, worldwide, royalty-free licence to receive it, forward it to the execution provider and the tool, and process it, for the sole purposes of running and supporting the Service and billing you.
We claim no ownership of your run output. We do not sell it, licence it to anyone else, or use it to build a dataset, a training set or any other product, and we do not aggregate it across customers. We may use aggregate, non-identifying operational figures, such as which endpoints get called and how often, to run and improve the Service.
We grant you no rights in the underlying data. The output is whatever a third-party tool read from a third-party source. Whether you may lawfully collect, keep or use it is your decision and your risk, under section 9 and the AUP. Nothing in these Terms is a licence to any source platform's content, to any tool author's work, or to any individual's personal data.

Our platform. The Service, the catalog, the endpoint schemas, the documentation and the software are ours or our licensors'. You get a limited, revocable, non-transferable right to use them through the API and the MCP server as intended. You may not copy or systematically extract the catalog to build a competing gateway.

Controller and processor. For the personal data in your run inputs and run outputs, you are the controller and we act as your processor. That allocation, and an honest account of the four facts that make it contestable, is set out in Privacy Policy section 2 and in section 4 of the Data Processing Agreement at https://usegoro.ai/legal/dpa. The DPA forms part of this agreement, applies from the moment you first send personal data through the Service, and covers instructions, sub-processors, security, deletion and audit. Where it and these Terms conflict on the processing of personal data, the DPA wins.

14. Taxes

Prices and charges are stated exclusive of VAT and any other tax or duty. You are responsible for any tax due on your purchase, other than tax on our income, including accounting for it yourself where a reverse charge applies to you.

What the checkout does not do today. It does not calculate or collect VAT, it does not ask for your VAT registration number, it does not collect a billing address beyond whatever Stripe requires for your payment method, and it does not issue a VAT invoice. If you need an invoice, email hello@usegoro.ai and we will issue one. We would rather tell you that than write a clause describing a tax flow the checkout does not have.

15. Changes to these Terms

We may update these Terms. The version in force is always the one published at https://usegoro.ai/legal/terms, with the "Last updated" date at the top.

A change that materially affects you takes effect 14 days after we publish it. Any other change takes effect when published. Publication is the notice, and that is deliberate rather than lazy: there is no outbound email in the product, so we have no reliable way to reach you individually and we are not going to promise one we cannot keep. Check the page. If we add outbound email later, we will also tell you directly, and this clause will change.

Continuing to use the Service after a change takes effect means you accept it. If you do not accept a material change, stop using the Service and tell us within 30 days, and we will refund your unused cash balance.

The Privacy Policy, the Acceptable Use Policy and the Data Processing Agreement carry the same clause, the same period and the same channel.

16. Governing law and disputes

These Terms are governed by the laws of Romania, without regard to conflict of law rules. The United Nations Convention on Contracts for the International Sale of Goods does not apply.

The courts of Iasi, Romania have exclusive jurisdiction over any dispute arising out of or relating to these Terms or the Service.

If, despite section 2, you are a consumer, nothing in this section takes away your right to bring proceedings in the courts of the country you live in, or the protection of the mandatory law of that country.

Before starting proceedings, both parties will try in good faith to resolve the dispute by contacting the other in writing and allowing 30 days to respond.

17. General

Entire agreement. These Terms, the AUP, the Privacy Policy and the DPA are the whole agreement between us on the Service, and replace any earlier discussion, proposal or landing page copy.
No waiver. Not enforcing a right once does not waive it.
Severability. If a clause is unenforceable, the rest stays in force and the clause is read down to the minimum change needed.
Assignment. You may not assign these Terms without our written consent. We may assign them to a successor in connection with a merger, acquisition or sale of assets.
No agency. Nothing here creates a partnership, agency, employment or joint venture.
Force majeure. Neither party is liable for a failure caused by something outside its reasonable control, including the failure of an upstream provider.
Third parties. No one other than you and us has any right to enforce these Terms.
Notices. You contact us at hello@usegoro.ai. We reach you by publishing at the URLs above, and, where a message is specific to your account rather than to everyone, at the email address on your account.

18. Contact

PROMPTIFY S.R.L. Strada Prof. Nicolae Oblu, Nr. 24A, Bloc B2A, Etaj 2, Ap. 22, Municipiul Iasi, Judetul Iasi, Romania Trade register number J22/1745/06.06.2023, CUI 48270068, EUID ROONRC.J22/1745/2023, VAT RO48310979 hello@usegoro.ai