Privacy Policy

Your privacy is fundamental. This policy explains how we handle data across both sides of Pushary: our control plane for AI agents and our push notification platform.

Last updated: November 18, 2026

This Privacy Policy describes how RalphNex OÜ (Registry Code: 16932562), operating as Pushary, collects, processes, stores, and protects personal information when you use our platform. Pushary provides a control plane for AI agents and a push notification platform. We are established in Estonia. Service providers and processing locations depend on the services used; establishment in the EU does not mean all processing stays in the EU.

1. Data Controller Information

RalphNex OÜ, a company registered in Estonia under Registry Code 16932562, acts as the data controller for personal data collected through the Pushary platform and website. For inquiries regarding data processing, contact us at business@pushary.com.

When you use Pushary to send notifications to your end-users, or to relay approval requests and notifications between your AI agents and you, you act as the data controller for that subscriber and agent interaction data, and we act as a data processor on your behalf.

2. Information We Collect

2.1 Account Information (Data We Control)

When you register for a Pushary account, we collect:

  • Identity Data: First name, last name, email address, and profile image (provided through Clerk authentication)
  • Account Data: User ID, authentication tokens, account preferences, timezone settings, and whether you signed up on the website, in the iOS app or in the Android app
  • Workspace Data: Workspace names, slugs, team member relationships, and role assignments (owner, admin, member, viewer)
  • Billing Data: Stripe customer ID, subscription plan, payment status, and billing history (processed through Stripe; we do not store credit card numbers)

2.2 Site Configuration Data

For each site you create within your workspace, we store:

  • Site name, domain, and configuration settings
  • VAPID key pairs (public and private keys) generated uniquely per site for cryptographic push notification authentication
  • API key hashes and prefixes (full API keys are shown only once upon generation)
  • Site icons, logos, and branding assets you upload

2.3 Subscriber Data (Data We Process on Your Behalf)

When end-users subscribe to notifications through your site, we collect and process:

  • Push Subscription Data: Endpoint URL, P256DH key, and authentication key required for Web Push protocol delivery
  • Device Information: Browser type, operating system, device type (desktop/mobile/tablet), and user agent string
  • Geographic Data: Country, city, and timezone derived from IP address geolocation (if enabled)
  • Custom Attributes: Tags, external IDs, and custom metadata you assign to subscribers through our SDK or API
  • Engagement Data: Subscription date, last active date, notification delivery count, click count, and subscription status

2.4 Analytics and Event Data

We collect analytics data to provide reporting and improve the Service:

  • Notification events: impressions, clicks, dismissals, delivery successes, and failures
  • Campaign performance metrics: total targeted, sent, delivered, clicked, and failed counts
  • Daily aggregated statistics per site
  • Action button interactions with associated action IDs

2.5 Mobile App Analytics

The Pushary mobile app for iOS and Android collects usage analytics only while app analytics is on. In the EEA, the UK (with Guernsey, Jersey and the Isle of Man), Switzerland, Canada and Australia, and wherever the app cannot tell your country from your connection, the app asks "Share usage analytics?" on first launch, with the options Allow and Don't allow. Before you choose Allow there, nothing is sent and no analytics identifier is stored on your device, except as described for Apple Ads in Section 2.6. Everywhere else, app analytics is on by default.

You can turn app analytics on or off at any time in the app under Settings > Privacy > Share usage analytics. Turning it off stops collection for your account on that device. It does not affect processing that took place before you turned it off.

While app analytics is on, the app sends the following to PostHog:

  • Product events: pseudonymous events when the app is first opened, sign-up is completed, onboarding is started and completed, the subscription screen is viewed, and a purchase is started, cancelled, or fails (including the store's error code)
  • App and device details: app name, identifier, version and build, device manufacturer, model and type, whether it is an emulator, operating system and version, screen size, language setting, and time zone
  • Identifiers: a random identifier that the analytics SDK generates for the installation, and your Pushary account identifier once you sign in
  • Internal test account flag: whether the account is a Pushary internal test account, sent as yes or no and never as the email address
  • Install campaign (Android only): the campaign parameters (utm_source, utm_medium, utm_campaign, utm_content, utm_term) that Google Play passes to the app at install, if there are any
  • Link campaign: the same campaign parameters on a link that opens the app, and never the rest of that link

App analytics does not collect your email address, name, commands, agent conversations, notification content, approval requests or answers, precise location, or a location derived from your IP address (IP geolocation is turned off for app analytics). It does not use advertising identifiers (IDFA or the Android advertising ID) and does not track you across other companies' apps or websites. This data is not sold, and it is not used to show you ads.

We use app analytics to understand where people get stuck during setup and subscription, to measure conversion, and to improve the app.

Legal basis: where the app asks first, your consent (Art. 6(1)(a) GDPR) and, where applicable, the rules on storing and accessing information on your device. Everywhere else, our legitimate interests in improving the app and measuring conversion (Art. 6(1)(f) GDPR); you can object at any time by turning app analytics off.

2.6 App Store and Google Play Subscriptions

RevenueCat processes App Store and Google Play purchase receipts and the subscription status for your workspace.

When a signed-in member who has app analytics on starts a purchase, the app stores that member's Pushary account identifier with the workspace's subscription record at RevenueCat, so that revenue can be attributed to the member who purchased. If app analytics is off, or the purchase is cancelled or fails, the identifier is removed.

Apple Ads (iOS only): while app analytics is on (see Section 2.5), the app gets a short-lived code from Apple on your device and passes it to RevenueCat, our subscription provider. RevenueCat sends the code to Apple, and Apple says whether you installed Pushary from one of our Apple Ads. If you did, Apple can also include the ad's campaign, ad group, keyword, ad and placement, the country or region, whether it was a first download or a redownload, and whether you tapped the ad or only saw it. RevenueCat stores this with your workspace's subscription record. We use it only to see which of our Apple Ads work, never to show you ads. None of this uses your advertising identifier (IDFA) or App Tracking Transparency. Two limits apply. Once the app has fetched the code, it keeps offering it until the app is fully quit, so if someone else signs in on the same device before then, their workspace can get the same answer, even if they have app analytics off. And turning app analytics off takes effect only after the app is fully quit and reopened, and does not delete an answer already stored. Legal basis: where the app asks first (see Section 2.5), your consent (Art. 6(1)(a) GDPR); everywhere else, our legitimate interest in measuring our own ads (Art. 6(1)(f) GDPR), which you can object to by turning app analytics off.

Our server forwards the subscription lifecycle events it receives from RevenueCat to PostHog for revenue reporting: trial started, payment, renewal, cancellation, refund, billing issue, expiration, plan change, and transfer. Each event includes the product, the store, the price and currency, estimated tax and store commission, transaction identifiers, the workspace identifier, and the store's country code.

An event is linked to a member only when that member has app analytics on and belongs to the workspace. Otherwise, it is reported for the workspace without creating a person profile.

Legal basis: for revenue reporting at workspace level, our legitimate interests in understanding subscription revenue (Art. 6(1)(f) GDPR). For reporting linked to a member, that member's consent where the app asks first (Art. 6(1)(a) GDPR), and otherwise our legitimate interests (Art. 6(1)(f) GDPR).

2.7 Technical and Log Data

We automatically collect technical information when you access our platform:

  • IP addresses and request metadata
  • Browser type, version, and language preferences
  • Access times, pages visited, and referral URLs
  • API request logs including endpoints, timestamps, and response codes
  • Error logs and diagnostic information for troubleshooting

2.8 AI Agent Platform Data (Data We Process on Your Behalf)

When you connect an AI agent (such as Claude Code, Codex, Cursor, or Hermes) to Pushary, the agent runs on your own machine. The decision path forwards only what is needed for an approval or notification. Session history is on by default. Each session on a computer signed in to Pushary syncs a transcript that is redacted and encrypted on your machine. Your phone can decrypt it, and authorized Pushary compliance admins can recover it for documented legal obligations. A workspace admin can turn session history off.

For each approval request or notification, we receive and process:

  • The question or decision: the prompt your agent needs you to answer, such as whether to run a command or change a file, together with that command, or the file's path and the change itself, up to 4,000 characters with known secrets removed
  • The tool name: the agent tool involved, such as Bash, Edit, or Write
  • The interaction type: whether the request is a confirmation, a selection, or a free-text question
  • Optional context: a short plain-text note your agent or hook may attach to explain the request
  • Your decision: your approval, denial, or typed answer, and the time you responded
  • Agent and session identifiers: the agent type and name, a machine identifier, and a session identifier used to group related activity
  • Notification content: for completion or error alerts, a title and body, plus any summary, list of changed file names, error message, error file name, or next steps your agent chooses to include

Outside the locally redacted, encrypted transcript path described below, the following never leaves your machine and is never sent to or stored by us:

  • Readable source code and file contents, apart from the change an approval request shows you
  • Readable agent transcripts and conversation history on routine product paths. Session history syncs transcripts by default after encrypting them on your machine. Your phone can decrypt them, and authorized Pushary compliance admins can recover them for documented legal obligations. A workspace admin can turn session history off for the workspace, and you can turn it off on one computer in the Mac app's settings or by running pushary transcripts off. When you sign in, a session that is already running syncs its earlier conversation from the last 14 days, or 30 on Agent Pro, Team, Partner and Enterprise, up to 20 MB per session. After history is turned back on, the CLI may also sync conversation written while history was off. Explicitly turning history back on in the Mac app starts with conversation written from then on.
  • Environment variables, secrets, credentials, and API keys
  • The contents of files your agent only reads. For a file it writes or edits, an approval request carries the file's path and the change, up to 4,000 characters with known secrets removed

A copy of each pending question is kept in our Redis cache for ten minutes, or until its deadline, at most twenty-four hours. Notification context is held for up to twenty-four hours. A durable record of each question, the tool involved, and your decision is written to your audit trail. Section 6 says how long it is kept. We never write your code to the audit trail. Session transcripts are redacted and encrypted on your machine before they leave by default. The session key is wrapped separately for your phone and Pushary's provider recovery key; authorized compliance admins can recover an exact session for a documented legal obligation. You can turn sync off on the agent machine at any time.

You direct what your agents send. For data transmitted through the agent integration, you act as the data controller and Pushary acts as a data processor on your behalf, on the same terms that apply to subscriber data above.

2.9 Auto Mode Training Data (Optional, Off by Default)

Auto Mode is our work on better permission defaults. To support it we can keep a minimized record of how permission decisions turn out. This is off unless a workspace owner or admin turns it on, and it is never enabled for you by default. While it is off, nothing described in this subsection is collected.

When a workspace has opted in, and only where you personally answered a request rather than a rule or a timeout resolving it, we store a derived summary of that decision:

  • The category of the action: the capability involved (read, edit, shell, network, or destructive) and a risk class derived from the tool and its target
  • The shape of the target: whether it looked like source, test, documentation, configuration, or a secret, expressed as a category rather than a path
  • Structural properties: whether the action appeared reversible and how wide its effect looked, each expressed as a category
  • The outcome: whether you approved or denied, and how long you took to answer
  • Version markers: the schema, extractor, and consent versions in force when the record was written

These records never contain your command, file path, prompt, source code, environment variables, or secrets. They are built on your own machine from the raw values, and only the derived categories are transmitted. Where a matched policy pattern is included, it is passed through secret redaction and truncated.

You can turn this off at any time in your agent settings, and we stop writing new records immediately. Turning it off changes nothing else about how the Service works. Records already written are retained according to your plan's retention window (see Section 6).

3. Legal Basis for Processing (GDPR Article 6)

We process personal data under the following legal bases:

  • Contract Performance (Art. 6(1)(b)): Processing necessary to provide the Service you have subscribed to, including account management, notification delivery, and billing
  • Legitimate Interests (Art. 6(1)(f)): Processing for platform security, fraud prevention, service improvement, and analytics where our interests do not override your rights
  • Legal Obligation (Art. 6(1)(c)): Processing required to comply with applicable laws, including tax regulations, court orders, and regulatory requirements
  • Consent (Art. 6(1)(a)): Where applicable, processing based on your explicit consent, which you may withdraw at any time

For subscriber data that you collect through our platform, you are the data controller and must ensure you have obtained appropriate consent or legal basis from your end-users.

4. How We Use Your Information

We process collected information for the following purposes:

  • Service Delivery: Operating and maintaining our event-driven notification platform, processing notification delivery through our Kafka-based message queue, and providing real-time analytics
  • Account Management: Creating and managing your account, authenticating access, processing workspace and team management operations
  • Billing Operations: Processing subscription payments through Stripe, managing plan changes, and maintaining billing records
  • Platform security: Detecting and preventing fraud, unauthorized access and abuse through application access controls.
  • Customer Support: Responding to inquiries, troubleshooting issues, and providing technical assistance
  • Service Improvement: Analyzing usage patterns, identifying performance issues, and developing new features
  • Communication: Sending service updates, security alerts, and important notices related to your account
  • Agent Control: Relaying approval requests and notifications between your AI agents and you, applying the per-tool permission policies you configure, and recording decisions to your audit trail
  • Improving Permission Defaults: Where a workspace has opted in, using minimized decision records to improve permission defaults and develop Auto Mode
  • Legal Compliance: Fulfilling legal obligations, responding to lawful requests, and protecting our legal rights

Pushary applies the permission policies you configure. Where you have set a rule that approves or denies a tool call without asking, that rule is applied automatically, and a budget limit you set can automatically pause your agents. These rules decide whether an AI agent may take an action. They are applied to tool calls, and they are not used to evaluate, profile, or make decisions about people. We do not use automated processing to make decisions about individuals that produce legal effects or similarly significant effects.

5. Data Sharing and Disclosure

We do not sell, rent, or trade your personal information. We may share data in the following limited circumstances:

5.1 Service Providers (Sub-Processors)

We engage trusted third-party service providers who process data on our behalf under strict contractual obligations:

  • Clerk (Authentication): User authentication and identity management - processes account credentials and session data
  • Neon (Database): PostgreSQL database hosting - stores all platform data with encryption at rest
  • Vercel (Hosting): Application hosting and CDN - processes request data and serves the dashboard application
  • Railway (Infrastructure): Runs our background worker, the event stream, and the cache - processes notification delivery events, agent presence, and pending questions
  • Redis (Cache): Temporary storage of pending agent questions and notification context, held only until you respond or until they expire
  • Stripe (Payments): Payment processing - handles billing data and payment transactions
  • Resend (Transactional Email): Delivers account, billing, and digest emails - processes your email address and the message content
  • PostHog (Product Analytics): Used for website usage analytics (with your cookie consent), error analytics, mobile app analytics (see Section 2.5), and subscription revenue reporting (see Section 2.6). Processes pseudonymous product usage events and subscription events. Processing locations require verification for the configured project.
  • Google Ads (Advertising measurement): Subject to your website advertising choices, we share Google click identifiers (gclid, gbraid, wbraid), SHA-256-hashed email addresses, trial and first-payment events, subscription or invoice identifiers, and the amount and currency actually paid with Google to measure advertising conversions. Advertising storage and event reporting require your prior consent in the EEA, UK and Switzerland. You can change your choice in Cookie settings.
  • X (Advertising measurement): Subject to your website advertising choices, we share X click identifiers (twclid), SHA-256-hashed email addresses, account-creation, trial and first-payment events, account, subscription or invoice identifiers, and the amount and currency actually paid with X to measure advertising conversions. The browser pixel also receives browser and network information. Advertising storage and event reporting require your prior consent in the EEA, UK and Switzerland. You can change your choice in Cookie settings.
  • TikTok (Advertising measurement): Subject to your website advertising choices, we share TikTok click identifiers (ttclid) and browser identifiers (_ttp), SHA-256-hashed email addresses and account identifiers, IP address and browser user agent, sign-up button taps, account-creation, checkout-start, trial and first-payment events, account, checkout or invoice identifiers, the plan, and the amount and currency actually paid with TikTok to measure advertising conversions. The browser pixel also receives browser and network information. Advertising storage and event reporting require your prior consent in the EEA, UK and Switzerland. You can change your choice in Cookie settings.
  • Slack (Optional Team Delivery): Delivers approval requests to a workspace channel when you connect Slack - processes the question text and the decision outcome
  • Push Service Providers (Google FCM, Mozilla, Apple APNs): Notification delivery - receives push subscription endpoints and encrypted notification payloads
  • Expo (Mobile Push Delivery): Relays notifications to the Pushary mobile app - receives device push tokens and notification payloads
  • RevenueCat (Mobile Subscriptions): Manages App Store and Google Play subscriptions. Processes purchase receipts and subscription status for the workspace; when the member who starts a purchase has app analytics on, that member's Pushary account identifier; and on iOS, while app analytics is on, the Apple Ads attribution of the install (see Section 2.6)

Partner logos: when a business invites you to receive its approval requests, the Pushary mobile app and the hosted approval page show that business's logo. The logo loads from a web address the business chose, which can be a server outside Pushary. That server receives your IP address and the details every image request carries, such as the app or browser version. Pushary sends it nothing else.

5.2 Legal Requirements

We may disclose information when required by law, including:

  • Response to valid legal process (subpoenas, court orders, warrants)
  • Compliance with applicable laws, regulations, or government requests
  • Protection of our legal rights, property, or safety
  • Prevention or investigation of possible wrongdoing

5.3 Business Transfers

In the event of a merger, acquisition, reorganization, or sale of assets, your information may be transferred as part of the transaction. We will notify you of any such transfer and any changes to applicable privacy terms.

6. Data Retention

We retain personal data only as long as necessary for the purposes described in this policy:

  • Account Data: Retained while your account is active and for 30 days following deletion request to enable account recovery
  • Subscriber Data: Retained according to your subscription plan's data retention window (currently 7 days on Free, 30 days on Starter, 90 days on Growth, 180 days on Pro, and unlimited on Enterprise)
  • Agent Interaction Records: Your agent audit trail (each question, the tool involved, and your decision) is kept until you delete your site or your account, and is deleted with it. Your plan's data retention window sets how far back your dashboard shows these records (currently 30 days on Agent, 90 days on Agent Pro, 365 days on Team, and unlimited on Enterprise). We do not delete older records automatically
  • Pending Agent Questions: a copy of each pending question is held in our Redis cache for ten minutes, or until its deadline, at most twenty-four hours, and notification context for up to twenty-four hours. The question itself stays open until you answer it, it reaches its deadline or your agent withdraws it
  • Session Transcripts: Transcripts synced by session history are stored encrypted until you delete your site or your account, and are deleted with it. We do not delete older transcripts automatically. Turning session history off stops new syncing and keeps the transcripts already stored
  • Auto Mode Training Records: Where enabled, minimized decision records are kept until you delete your site or your account, and are deleted with it
  • Analytics Data: Aggregated daily statistics retained according to your plan's data retention limits. Product analytics events in PostHog, from the website and the mobile app, are retained for 12 months and then deleted
  • Notification Event Logs: Retained according to your plan limits; individual notification records may be purged after delivery confirmation
  • Billing Records: Retained for 7 years as required by Estonian tax law and applicable accounting standards
  • Security Logs: Retained for 90 days for security monitoring and incident investigation

Upon account deletion, we will delete or anonymize your personal data within 30 days, except where retention is required by law or necessary to protect our legitimate interests.

7. Data Security

We implement comprehensive technical and organizational measures to protect your data:

7.1 Technical Safeguards

  • Encryption in Transit: All data transmitted to and from our platform is encrypted using TLS 1.2 or higher
  • Encryption at Rest: Database storage encrypted using AES-256 encryption at the infrastructure level
  • Workspace access: Server authorization and workspace-scoped database queries check access to team data.
  • VAPID Authentication: Unique cryptographic key pairs per site for secure push notification delivery
  • API Key Security: API keys stored as secure hashes; full keys shown only once upon generation
  • Secure Authentication: Authentication handled by Clerk with support for MFA and secure session management
  • Signed decision links: Signatures detect tampering. Treat a valid link as sensitive and share it only with the intended recipient.
  • Data Minimization: Approval requests carry the question, the tool name and the command or change you are asked to approve, up to 4,000 characters, with known secrets removed. Session transcripts are redacted and encrypted on your machine; routine product paths store ciphertext, while authorized compliance admins can recover an exact session for a documented legal obligation

7.2 Operational Safeguards

  • Access controls limiting data access to authorized personnel
  • Regular security assessments and vulnerability monitoring
  • Incident response procedures for security events
  • Secure development practices and code review processes

7.3 Infrastructure Security

  • Hosting on SOC 2 Type II certified infrastructure (Vercel, Neon)
  • Geographic redundancy and automated backups
  • DDoS protection and rate limiting
  • Isolated worker processes for notification delivery

While we implement industry-standard security measures, no system is completely secure. We cannot guarantee absolute security of your data.

7.4 Compliance Posture

Pushary is operated by an Estonian company. We do not hold GDPR certification or an independent platform security attestation. Our assessments are internal; infrastructure-provider certifications do not certify our own platform. Contact us to review processing, retention and contractual requirements for your use. This policy is not a guarantee of regulatory compliance.

8. Your Privacy Rights

We respect your rights regarding your personal data. Depending on your location and applicable laws, you may have the following rights:

  • Right to Access: Request a copy of the personal data we hold about you
  • Right to Rectification: Request correction of inaccurate or incomplete personal data
  • Right to Erasure: Request deletion of your personal data where there is no compelling reason for continued processing
  • Right to Restrict Processing: Request limitation of processing while we verify accuracy or assess objections
  • Right to Data Portability: Receive your personal data in a structured, commonly used, machine-readable format
  • Right to Object: Object to processing based on legitimate interests
  • Right to Withdraw Consent: Where processing is based on consent, withdraw that consent at any time
  • Rights Regarding Automated Decisions: Request human intervention in, and object to, any decision based solely on automated processing that produces legal effects or similarly significant effects concerning you

To exercise any of these rights, contact us at business@pushary.com. We will respond within 30 days. We may request verification of your identity before processing your request. business@pushary.com.

9. Data Location and Transfers

Processing locations depend on the service and deployment configuration. Storage, backups, support access and onward processing may have different locations. The following services process data; contact us for the applicable verified processing schedule:

  • Primary Database: Neon PostgreSQL; storage, backup and support locations require deployment-specific verification
  • Application Hosting: Global CDN with edge processing
  • Background Worker and Event Stream: Railway - runs notification delivery, agent presence, and retention jobs
  • Question Cache: Redis, running alongside our background worker, temporarily stores pending agent questions and notification context
  • Authentication: Clerk processes authentication data
  • Payments: Stripe processes billing data
  • Product Analytics: PostHog; the configured project region and onward processing require verification

Some of our service providers operate internationally. When your data is transferred outside the European Union, we work with providers who implement appropriate data protection measures.

10. Cookies and Tracking Technologies

We use cookies and similar technologies to operate and improve our platform:

10.1 Essential Cookies

Required for platform functionality. These cannot be disabled:

  • Authentication session cookies (managed by Clerk)
  • CSRF protection tokens
  • Load balancer session persistence

10.2 Functional Cookies

Enhance your experience by remembering preferences:

  • Theme preferences (light/dark mode)
  • Dashboard layout settings
  • Language preferences

10.3 Analytics Cookies

Help us understand platform usage:

  • Page view tracking
  • Feature usage analytics
  • Error tracking and diagnostics

10.4 Mobile App Analytics

Analytics in the Pushary mobile app runs only while app analytics is on: where the app asks first, only after you allow it, and elsewhere by default. You can turn it on or off at any time in the app under Settings > Privacy > Share usage analytics (see Section 2.5).

You can control cookie preferences through your browser settings. Disabling certain cookies may affect platform functionality.

11. Data Processing Relationship

When you use Pushary to send notifications to your end-users, we process subscriber data on your behalf. Our commitments include:

  • Processing data according to your instructions for notification delivery
  • Maintaining confidentiality of subscriber information
  • Implementing technical and organizational security measures
  • Assisting with data subject requests upon your instruction
  • Deleting or returning data upon account termination

The same processor commitments apply to the data you transmit through the AI agent integration, including the questions, decisions, and audit records described in Section 2.8.

Enterprise customers requiring formal data processing agreements should contact us at business@pushary.com.

12. Children's Privacy

The Pushary platform is designed for business use and is not directed to children under the age of 16. We do not knowingly collect personal information from children. If you become aware that a child has provided us with personal information without parental consent, please contact us at business@pushary.com, and we will take steps to delete such information.

If you use Pushary to send notifications, you are responsible for ensuring your service is appropriate for your audience and that you comply with applicable laws regarding children's privacy (including COPPA in the United States).

13. California Privacy Rights (CCPA)

If you are a California resident, you have additional rights under the California Consumer Privacy Act (CCPA):

  • Right to Know: Request disclosure of categories and specific pieces of personal information collected
  • Right to Delete: Request deletion of personal information we have collected
  • Right to Non-Discrimination: Exercise privacy rights without discriminatory treatment
  • Right to Opt-Out: We do not sell personal information; therefore, there is no sale to opt out of

To exercise CCPA rights, contact us at business@pushary.com. We will verify your identity before processing requests.

14. Changes to This Policy

We may update this Privacy Policy periodically to reflect changes in our practices, technologies, legal requirements, or for other operational reasons. We will notify you of material changes by:

  • Posting the updated policy on our website with a new effective date
  • Sending email notification to registered account holders for significant changes
  • Displaying a notice in the dashboard interface

We encourage you to review this policy periodically. Your continued use of the Service after changes take effect constitutes acceptance of the updated policy.

15. Contact Us

For questions, concerns, or requests regarding this Privacy Policy or our data practices, please contact our data protection team:

RalphNex OÜ

Registry Code: 16932562

Jurisdiction: Estonia, European Union

Infrastructure locations: Vary by service; contact us for the applicable processing schedule.

Email: business@pushary.com