Privacy Notice

1. Controller and processor roles

OptiNext Kft. is controller for its website, registration, subscriptions, invoicing, support and service security. Contact info@optinext.hu; company details appear above and in the Imprint. We do not claim to have appointed a separate data protection officer.

For agency-entered client information, creatives, reviewers and campaign data, the customer or its client determines purposes and Publsy processes on instructions. If the agency is a processor, Publsy is its subprocessor. The Data Processing Terms define this relationship. External social platforms can also act as separate controllers under their own notices.

2. Data categories, purposes and legal bases

Accounts and teams: name, email, password hash, role, workspace/client access, language, time zone, invitations and authentication events. Purposes are identification, contract delivery and permissions. For an individual’s own contract the basis is GDPR Article 6(1)(b); for business contacts and staff it is the legitimate interest in contractual cooperation and secure work, Article 6(1)(f).

Subscriptions and purchases: buyer type, billing name/address/country/tax number/email, plan, provider identifiers, payment and invoice status, token purchases and usage. Purposes are service delivery, accounting and tax obligations. Bases are contract and legal obligation under Article 6(1)(c), with legitimate interest for necessary representative data. Publsy does not store full card numbers or CVC codes.

Client work: contacts, briefs, brand information, captions, uploaded/generated images and video, character/product references, calendar, comments, approval decisions and times, and reports. Processing follows customer instructions. The customer must establish a lawful basis and provide notices for uploads and reviewer invitations.

Contact and complaints: details, messages and attachments needed to address your enquiry. Bases are contractual necessity for contract requests, legitimate interest for business contacts and legal obligation for mandatory complaint handling. Operational, approval and billing notices are not newsletter subscriptions.

Security and evidence: technical logs, IP addresses or derived digests, timestamps, request/error identifiers, access/activity trails and accepted document versions/hashes. Purposes are troubleshooting, abuse prevention and evidence of statements, limited to necessity. Basis is legitimate interest in secure service and legal claims. Cookie acceptance is not general consent to this processing.

Analytics and advertising effectiveness measurement: only after separate consent, through permitted public page views and separate completed-registration/verified-payment server events. The basis is GDPR Article 6(1)(a), including consent for device storage/access. Refusal does not prevent service use.

3. AI and external API/OAuth access

An AI request sends only the brief, instructions and specifically selected validated reference files needed for the task. The feature identifies the model and calculated cost. Do not submit special-category data, identity documents, passwords or portraits you lack rights to use. Requested depictions of people do not mean Publsy performs biometric identification.

Publsy does not use client-workspace material as a source for its own advertising or training its own general AI model. The AI provider’s endpoint-specific technical/security retention follows its terms. We do not promise zero retention or exclusively EEA AI processing without a separately established arrangement.

An external assistant you authorise, such as a ChatGPT or Codex connection, can access only the designated client and allowed actions. Revoke it separately when no longer needed. Data sent to an external assistant is also subject to that service’s handling; revoking Publsy access does not automatically erase copies already held there.

4. Facebook, Instagram and other social data

Connecting a platform involves the account/page ID, name, granted permissions and credentials needed for authorised operations. For Facebook and Instagram this supports selecting authorised pages and professional profiles, uploading/managing content and retrieving post/profile metrics. Other social integrations may use only data necessary for actually enabled, authorised features.

Social access tokens are stored with protection and must not appear in public approval links or measurement tags. Disconnect in Publsy and revoke application permissions at the platform. See Data Deletion for Meta-specific instructions. Published material and a platform’s own records may remain under that platform’s policies.

5. Recipients and international transfers

Access is limited to authorised workspace members, designated reviewers and operators who need it for their work. Infrastructure and email: HOSTINGER INTERNATIONAL LIMITED (Cyprus), including media-processing VPS and backups. AI: OpenAI, with OpenAI Ireland Limited/affiliates as determined by the applicable EEA contract. Payments: Stripe, with Stripe Technology Europe, Limited/affiliates under the applicable EEA arrangement. Invoicing: Tacit Project Kft., 1064 Budapest, Podmaniczky utca 57., Hungary (Tacito). The relevant service contract determines the exact contracting entity.

Consent-based measurement uses Google Ireland Limited (Google Tag Manager and Google Analytics 4) and Meta Platforms Ireland Limited (Meta Pixel). Social connections involve the chosen platform, including Meta for Facebook/Instagram. Payment and social providers may be separate controllers for their own legal/security purposes. Necessary information may also go to authorities, accountants or legal advisers under applicable requirements; invoice reporting to NAV is handled by the invoicing process.

Providers or their subcontractors may process or access data outside the EEA, including the United States. The safeguard depends on the actual recipient and operation: an applicable adequacy decision or appropriate GDPR safeguards, such as standard contractual clauses and necessary supplementary measures. We do not assert that every recipient or operation has the same certification. Request transfer information and copies of safeguards at info@optinext.hu. The Data Processing Terms contain the subprocessor list.

Hostinger DPA

OpenAI DPA

Stripe Privacy

Tacito

Google Privacy

Meta Privacy

6. Retention, backups and deletion

Active account/project data is processed while required by the service relationship and customer instructions. Termination or a deletion request does not trigger uncontrolled database deletion: the operator separates returnable/deletable workspace data from records that must be retained. Return or live-system deletion under the Data Processing Terms is normally completed within thirty days after authority and scope are clarified.

Invoices and accounting records are retained for at least eight years under Hungarian accounting law. Necessary contract and acceptance evidence may remain for the general five-year claim period after the relationship ends; an ongoing claim may extend this as necessary. Consumer complaints and replies are kept for three years. This does not impose a five-year retention period on every creative.

Security and operational logs are restricted and retained as necessary for troubleshooting, incidents or legal claims. There is no single automatic deletion deadline enforced across all hosting, application and third-party logs. We review the necessity of our log files regularly, at least quarterly, and remove those no longer needed. Ask about retention of a specific event.

VPS backups keep fourteen daily, eight weekly and twelve monthly restore points. Deleted data may therefore remain in an older restricted backup for approximately twelve months. Backups are not used for routine business activity and age out through the retention cycle. Previous deletion instructions must be reapplied after restoration. We do not promise immediate erasure from every backup copy.

The one-year extra-token validity is a usage deadline, not a payment-record retention limit. Browser-storage and measurement-cookie durations are set out separately in the Cookie Notice; providers can have different retention in their own systems.

7. Rights, sources and remedies

We receive data from you, authorised workspace managers, inviters/reviewers and the social/payment providers you authorise. Required registration data is necessary to establish and bill the service; optional measurement/marketing is not a condition of use.

Where applicable, request access, correction, erasure, restriction and portability, and object to processing based on legitimate interests. Withdraw measurement consent in Cookie settings at any time without affecting earlier lawful processing. Objections and legal bases are assessed individually; closing an account cannot erase mandatory accounting records.

Contact info@optinext.hu. After necessary and proportionate identification, we respond without undue delay, normally within one month; any justified extension is explained within that period. For data processed on behalf of your client, we help route the request to its controller and follow lawful instructions. We do not require passwords or full card details.

Complain to the Hungarian National Authority for Data Protection and Freedom of Information (NAIH), 1055 Budapest, Falk Miksa utca 9–11., Hungary; postal address 1363 Budapest, Pf. 9.; website https://naih.hu; customer-service email ugyfelszolgalat@naih.hu. Check its site for formal filing methods. You can also approach another competent supervisory authority or a court without first complaining to us.

Publsy does not make solely automated decisions producing legal or similarly significant effects on you. Consent-based Google/Meta measurement can involve additional provider-side statistics/advertising processing, explained before your choice. Material processing changes are communicated in advance; consent for a new purpose is requested separately.

NAIH

GDPR

Consent-based registration and payment measurement

With analytics consent, Google Analytics 4 may receive completed registration events and positive payments verified by Stripe. A zero-value trial, failed payment or a thank-you page view alone is not a purchase. Google advertising data use requires its own Google Ads choice; Meta consent does not grant it. Ad personalization and remarketing remain disabled.

Separate Meta consent covers Pixel page views and server-side completed registration and verified payment events. Shared data are browser identifiers, event type and time, an opaque stable event identifier and, for purchases, amount, currency and product type. We do not send names, email addresses, billing addresses, customer creative content, form fields, authentication tokens or private application URLs. Browser identifiers may constitute personal data; we do not describe them as fully anonymous.

The optional publsy_measurement_id cookie is set only after an explicit choice, for up to 6 months. Checkout measurement consent and delivery records are stored separately on the server. Withdrawal suppresses the affected channels of unsent events. Later renewed consent does not retroactively permit an old checkout. Network failures may require the withdrawal notification to retry on a later page load. Provider policies also apply to data already sent. Consent contexts expire no later than 6 months after the choice. The automatic scheduler removes browser, customer and checkout references from expired measurement contexts. Delivery payloads are cleared after 7 days; only an opaque event key preventing repeat delivery and the technical status remain. Original orders, payments and invoices are unaffected.

Google and Meta remain the measurement providers. The existing provider, international transfer, legal basis and data-subject rights sections also apply to these events. Service use and payment remain independent of optional measurement.