Support

This page explains how to get help with GPTpostLLM, what support can realistically do for you, and what it cannot do no matter how the request is phrased. It is written to set expectations accurately rather than generously.

1. One channel: contact@oraglegpt.org

All support is by email to contact@oraglegpt.org. There is no other channel, and that is a deliberate design rather than a gap we intend to fill:

• No telephone support queue.
• No live chat widget.
• No ticket portal or customer help desk to log in to.
• No social media support handle. Messages sent to any social account are not monitored, and in any case the product itself cannot read platform inboxes.

Email goes to a monitored mailbox read by people who work on the product. You do not pass through a triage tier that cannot answer you.

+40 753 980 299 is the company's registered telephone number. It is published because Legea nr. 365/2002 privind comerțul electronic, art. 5 requires an information society service provider to make available details, including a telephone number, that let you contact it directly and effectively for legal purposes. It is not a support hotline. It is not staffed as a helpline, there is no support queue behind it, and a technical question raised on it will be answered by being asked to write to contact@oraglegpt.org. Use it for legal, administrative or formal contact where a telephone number is genuinely required.

The registered postal address, for formal service of documents, is in Company Identification.

2. Languages and hours

We answer in Romanian and in English, in whichever of the two you write. Romanian is the language of the contract in dealings with consumers, for the reason set out in Terms of Service, which reflects OG nr. 21/1992 privind protecția consumatorilor art. 20 alin. (5).

Support is worked Monday to Friday, 09:00 to 18:00, Europe/Bucharest, excluding Romanian public holidays. Mail sent outside those hours is read at the start of the next working period. Severity 1 problems affecting the Service as a whole are worked when they are found, whatever the hour, and are handled through the incident process in Service Status rather than through this queue.

3. How to write a request that gets answered quickly

Include, in the first message:

1. The workspace name or identifier and the email address on the account.
2. What you were trying to do, in one sentence.
3. What happened instead, including the exact error text, copied rather than described.
4. When it happened, with the time zone.
5. Where: which page, which connector, which post or campaign identifier.
6. What you have already tried.
7. A screenshot, if the problem is visible in the interface.

For a publishing failure, the single most useful addition is whether /readyz was returning 200 at the time, and what the destination platform's own error message said. Both are explained in Service Status.

Please do not send passwords, API keys, OAuth tokens or platform credentials. We never ask for them and we do not need them to investigate. If you have sent one by accident, rotate it and tell us.

4. Priority levels and response targets

We classify requests on receipt using the same severity scale as Service Status.

These are targets, not guarantees. They are not a service level agreement, they do not create a contractual commitment, and no service credit or compensation attaches to missing one. We publish them because a target you can plan around is more useful than silence, not because we are undertaking to meet them in every case. Service Status states the same position about availability: there is no uptime SLA.

A first response is a human reply from a person who has read your message. It is not an automated acknowledgement, because the Service sends no automated mail of any kind.

There is no paid support tier. There is no way to buy faster responses, a named contact or an out-of-hours commitment, so nobody is behind you in the queue because they paid less.

5. What support can do

• Investigate a defect, reproduce it, and get it fixed or tell you honestly when it will not be.
• Explain how a feature works and whether it does what you need before you build a process on it.
• Look at a failed publish and tell you what the destination platform returned and why.
• Help with account, workspace and member administration, including recovering access to your account with us.
• Help you connect a supported provider, and diagnose why a connection is failing or has expired.
• Run and explain a data export of your workspace, which is a signed archive containing a manifest and your records across 48 resource families, available to you directly in the interface at Settings, Data Privacy.
• Handle a request to delete your account or close your workspace, and explain the grace period in Data Deletion Policy.
• Take a data subject request under GDPR, described in Your Data Protection Rights.
• Receive a report of abuse under Acceptable Use Policy or a copyright notice under Copyright and Takedown Policy.
• Answer billing and entitlement questions. Note that the product processes no payments: there is no card processor and no card data is collected or stored, and billing is an internal entitlement record. Refunds and cancellations are covered by Refund and Cancellation Policy and, for consumers, Consumer Rights and Dispute Resolution.

6. What support cannot do

This section exists so you do not spend a day waiting for an answer that will be no. None of these are policy choices we can waive; they are things the product does not implement.

• We cannot recover a platform account you lost. If Meta, TikTok or any other platform suspends, restricts or deletes your account there, that relationship is between you and them. We cannot appeal, escalate, contact a platform on your behalf, or restore access.
• We cannot un-publish a post that is already live on a platform. Every connector in this product is publish-only. There is no delete or edit capability on any provider. We can cancel what has not gone out yet and remove content from our systems, and that is the limit. To remove a live post, use the platform.
• We cannot retrieve analytics, insights, reach, impressions or follower data from any platform, because we never collect any. The only route by which analytics data enters the platform is your own authenticated request to /api/v1/analytics/observations. If you did not send it, it does not exist here, and no amount of support effort will produce it.
• We cannot read or fetch your comments, mentions, replies, direct messages or any inbox. No connector has any inbox capability. There is nothing to retrieve and no setting that enables it.
• We cannot make a connector do something it does not implement. Liking, reposting, moderating, replying and deleting are not implemented for any provider. A request to enable one is a feature request, not a support issue.
• We cannot connect a provider that is not connectable on this deployment. Only some providers offer a connection route here. Where one does not, no credential or setting will change that.
• We cannot recover data after the deletion grace period has run. Deletion is final by design. Read Data Deletion Policy before you confirm anything, and export first.
• We cannot decrypt or return a credential you stored with us. Stored credentials are encrypted and are deliberately excluded from data exports. Rotate it at the source instead.
• We cannot write your content, run your campaigns or advise on marketing strategy, and we cannot give legal, tax or accounting advice.
• We cannot act on an instruction from someone who is not verified as entitled to give it. For account-changing requests we verify that you control the account first. This protects you.

If the answer to your question is one of the above, we will say so directly and early rather than keep a ticket open.

7. Security reports

Suspected vulnerabilities go to contact@oraglegpt.org with the subject line "Security". Include what you found, how to reproduce it, and the impact. Please give us a reasonable period to fix it before disclosing publicly, and do not access, alter or exfiltrate other customers' data while testing. Our security posture, and what we do and do not claim about it, is set out in Security.

Suspected personal data breaches are handled under Your Data Protection Rights.

8. Escalation and complaints

If you are not satisfied with how a request was handled, reply on the same thread and ask for it to be escalated, stating what outcome you are looking for. A different person reviews it where that is practicable.

Enforcement decisions under Acceptable Use Policy have their own appeal route, set out in that policy.

If you are a consumer and the matter is not resolved with us, Consumer Rights and Dispute Resolution explains your rights and the routes available, including the Autoritatea Națională pentru Protecția Consumatorilor (ANPC) alternative dispute resolution channel at https://anpc.ro/sal/ and the complaints platform at https://reclamatiisal.anpc.ro. Nothing in this page limits a consumer's mandatory statutory rights.

9. Related pages