# Privacy and security

Canonical URL: https://www.intellipush.com/en/trust/

The Intellipush Trust Centre brings together four main topics: privacy and cookies, GDPR and data processing, security, and responsible use with anti-spam.

Provider categories and data processing: https://www.intellipush.com/en/gdpr/#subprocessors

Analytics is optional. Google Analytics 4 is managed through GTM and loads only after valid analytics consent. Both acceptance and rejection are shared between www.intellipush.com and portal.intellipush.com through consent-store v2. The choice lasts 180 days from the explicit choice; reads do not renew expiry. LocalStorage acceptance alone does not grant consent. Advertising consent remains denied. The choice can be changed using footer privacy settings. This supersedes the 2026.08 privacy notice statement that analytics does not load. See /en/privacy-policy/#website-analytics.

## Acceptable Use Policy

Version 2026.08; effective 2026-08-18.

This policy is a binding part of the service terms and applies to the portal, APIs, integrations, files and SMS, email, voice and related messaging functions where enabled. The customer is responsible for recipients, content, sender identity and lawful use. Intellipush provides channel-specific opt-out and suppression functions where available and may follow up complaints, suspicious activity or misuse.

### Scope and responsibility

This policy applies to all use of the portal, APIs, integrations, files and messaging functions. The service may only be used for lawful business purposes. The customer must follow the rules in the recipient's country, applicable industry requirements and the agreement with Intellipush. Operational information from Intellipush is not legal advice, approval of a campaign or permission to send.

### Marketing messages require documented prior consent

As a contractual condition of using Intellipush, the customer must be able to document the recipient's freely given, informed and prior consent before advertising or marketing is sent through the service. This applies to SMS, email and automated voice functions where enabled, even where local law may recognise a narrower exception. Local law may impose stricter or additional requirements. Consent must be connected to an identified sender and cover the relevant channel and type of marketing. A purchased, shared, scraped or imported list does not satisfy the requirement by itself. The customer must provide evidence on request.

### Service and operational messages

Alerts, reminders and other service or operational messages must have a lawful purpose, the correct recipient and relevant content. They must not disguise advertising. The customer must assess the legal basis, transparency duties, confidentiality and channel or industry rules for the specific use. Describing a message as operational does not remove these obligations.

### Opt-out, STOP and blacklists

Marketing must provide an easy and free opt-out appropriate to the channel. For SMS where the sender setup can receive replies, Intellipush supports keywords including “STOPP” and “STOP”. With a one-way alphanumeric sender, the customer must provide another clear opt-out route. Marketing email must include a functioning unsubscribe method where required. Voice use must clearly identify the sender and provide an appropriate contact or opt-out route. The customer must verify that the chosen method works for the country, number, address, sender type and channel. Registered opt-outs are added to the blacklist and must be respected in Intellipush and in the customer's own systems and other channels.

### Sender identity and content

The recipient must understand who the sender is. The customer must have the right to use the selected sender name or number and must not mislead, impersonate others or conceal a commercial purpose. Messages must be relevant and accurate and must not be designed to circumvent filters, suppression, country rules or technical controls.

### Prohibited use

The service must not be used for spam, fraud, phishing, harassment, threats, malware, unlawful content, unauthorised data collection, purchased or scraped marketing lists without documented consent, misleading or manipulated sender identity, or attempts to circumvent filters, suppression, country rules or technical controls. The customer must not use a different channel to avoid a recipient's recorded opt-out. MMS is not included in the standard service. Premium-rate, recipient-paid or other specially regulated messaging requires a separate written agreement where Intellipush supports it.

### Sensitive and high-risk use

SMS should not contain sensitive personal data, complete credentials or other content requiring strong confidentiality. The service must not be the sole channel for emergency communications or use where delay or failure may endanger life or health or cause significant damage. Communications directed at children or other high-risk use require a separate assessment and may require written clarification with Intellipush.

### Files and links

Files shared through a public-link feature are available to anyone who has the link, even though the link is difficult to guess, unlisted and not intended for indexing. The customer must not upload unlawful, harmful, sensitive or unnecessary content and must delete or revoke sharing when it is no longer needed.

### Account security and integrations

The customer must protect passwords, API credentials and integrations, restrict user access, remove expired access and notify Intellipush of suspected misuse. Credentials and secrets must not be included in message content or exposed in public client code. The customer is responsible for actions performed through its accounts and integrations unless mandatory law or the agreement provides otherwise.

### Review and enforcement

Intellipush may request evidence, investigate complaints or suspicious activity, restrict functions, stop campaigns, or suspend and terminate the service under the terms. Measures are assessed according to risk, severity, repetition and the need to protect recipients, networks and the service. Urgent measures may be taken without prior notice.

### Report misuse

Report potential spam, fraud, unauthorised use or account misuse to info@intellipush.com. Include the sender, time, recipient number to the extent necessary and relevant message information, but do not send more personal data than the matter requires.

Source: https://www.intellipush.com/en/acceptable-use/

## GDPR and data processing

Version 2026.08; effective 2026-08-18.

This page explains how roles and the Data Processing Addendum work when Intellipush is used for enabled SMS, email, voice and related messaging functions. The DPA applies automatically as Schedule 1 to the service terms; it does not require a separate order or signature.

### The customer's and Intellipush's roles

The customer is normally the controller when it determines why recipient data is used and the essential parameters of the campaign. Intellipush is normally the processor when we process that data on the customer's documented instructions. Intellipush is also the controller for its own purposes, such as accounts, billing, support and security. Both parties retain their independent legal duties.

### The Data Processing Addendum is included

Schedule 1 to the Intellipush Business Terms of Service is the DPA between the customer and Intellipush. It applies automatically whenever Intellipush processes personal data on the customer's behalf. It covers instructions, confidentiality, security, subprocessors, transfers, assistance, breaches, audit and what happens when the service ends.

### The customer's independent responsibility

The customer must have a valid legal basis, provide required information, minimise data, keep contact data current, and handle rights and opt-outs. Under the Acceptable Use Policy, advertising and marketing through enabled channels requires documented prior consent. Standard messaging channels are not necessarily end-to-end encrypted, and sensitive or high-risk content requires a separate assessment. Intellipush features do not replace the customer's assessment of lawfulness.

### Export, termination and erasure

After termination, the customer normally has 30 days to export customer data. Customer data is then erased from active systems within 60 days and expires through the ordinary 14-day backup cycle. Statutory retention, security records, disputes and other lawful exceptions may require limited data to be retained for longer.

### Rights and assistance

A recipient should normally contact the organisation that determined the purpose of the campaign. Intellipush assists the customer with relevant requests, assessments, breaches and regulatory engagement to the extent required by the DPA and law. The customer must not send more personal data than is necessary for the assistance.

### Provider categories and data processing

Core infrastructure and backups are with AWS in Ireland. Depending on the enabled functions and selected message route, Intellipush may also use messaging-routing and delivery providers, national and international mobile and communications networks, and optional communications and support services. The exact, versioned subprocessor schedule is commercially confidential and is made available to verified customers and prospects before contracting and subsequently on request. Not every communications network, customer-selected destination or recipient acts as a subprocessor. Its role is assessed according to the actual processing and message route concerned.

### International transfers

Message routes, recipient countries, mobile networks and some supporting services may involve processing outside the EEA. Where international-transfer rules apply, Intellipush and the customer must meet their respective duties and use a valid basis and necessary safeguards for the transfer concerned.

### Security in practice

Intellipush uses risk-based organisational and technical measures. Verified high-level controls are described on the security page. The customer remains responsible for its own users, passwords, integration credentials, content and recipients. Security is an ongoing discipline, not an absolute guarantee against errors or incidents.

Source: https://www.intellipush.com/en/gdpr/

## Privacy and cookies

Version 2026.08; effective 2026-08-18.

This notice explains how Intellipush AS processes personal data as a controller and how we act as a processor when customers use the service for their own recipient data. It also covers cookies and local storage on the website and in the customer portal.

### Language choices and suggestions

Your browser language may be used locally to show a suggestion for the other language version, but the website does not redirect you automatically. If you dismiss the language suggestion, the value “1” is stored under “intellipush_language_suggestion_dismissed” in session storage until the browser session ends.

### Who is responsible

Intellipush AS, Norwegian organisation number 912 302 806, Veumveien 23, 1613 Fredrikstad, Norway, is the controller for the processing described in this notice. Questions and requests may be sent to info@intellipush.com or +47 46 20 90 90.

### Our roles

Intellipush is the controller for its own purposes, including the website, sales, account administration, billing, support, security and legally required records. When a customer determines the purpose of business messaging and uses Intellipush to process recipient data on the customer's instructions, the customer is normally the controller and Intellipush the processor. The Data Processing Addendum is automatically incorporated as Schedule 1 to the service terms.

### Data, purposes and legal bases

What we process depends on how you or your organisation uses and contacts us. We limit processing to what is necessary for the relevant purpose. References below are to Article 6(1) GDPR.

### Sources of personal data

We normally receive data directly from you, the organisation you represent, other authorised account users, or through use of the website and service. We may also receive necessary data from payment, accounting, communications and security providers. When we act as processor, recipient data and instructions come from the customer or its integrations.

### Who receives personal data

Internal access is granted according to need. We use provider categories for core infrastructure and backups, electronic communications and mobile networks, payments and accounting, email and support, and security and operational tools. Public authorities or advisers may receive data where required by law or necessary to establish or defend legal claims. We do not sell personal data.

### Processing locations and international processing

Core infrastructure and backups are located with AWS in Ireland. This does not mean that all processing takes place in Norway or the EEA. Message transmission, mobile networks, recipient destinations and some supporting functions may involve processing in other countries. Where the rules on transfers outside the EEA apply, the relevant transfer basis and necessary safeguards must be assessed for the processing concerned.

### How long data is retained

Data is retained for as long as needed for the purpose. Account and contract records may be kept while the relationship continues and afterwards where necessary for claims, security or legal records. Accounting data is retained for statutory periods. Support and security data is assessed according to the case, risk and documentation need. When Intellipush acts as processor, the export and erasure rules in Schedule 1 apply: normally a 30-day export opportunity, erasure from active systems within 60 days and then expiry through the ordinary 14-day backup cycle, subject to lawful exceptions.

### Cookies, local storage and similar technologies

The public website uses first-party local storage to remember the active language. The value “nb” or “en” is stored under the key “intellipush_language” until you change the language or clear browser data. Navigation, filters and search functions that run only in the browser do not by themselves send those interactions to an analytics provider. The contact form uses Google reCAPTCHA v2 to prevent automated abuse. It is not loaded on an ordinary page view, but only after you begin using the form. Google may then receive data including the IP address, browser and device information and interaction data, and may use cookies or local storage under its own terms. Intellipush uses the control on the basis of our legitimate interest in protecting the website and handling genuine enquiries under Article 6(1)(f) GDPR. You may contact us by email or phone without using the form. The customer portal uses technologies necessary for sign-in, session management, language, security and delivery of requested functions. At publication, the website does not load analytics or advertising technologies. If Intellipush later introduces such non-essential technology, we will update this inventory and prevent it from loading until the required consent has been obtained.

### Your rights

You may request access, rectification, erasure, restriction or portability, or object to processing, where the conditions under data-protection law are met. You may withdraw consent without affecting processing carried out before withdrawal. You may complain to the Norwegian Data Protection Authority. We may request information needed to verify your identity. If the request concerns a customer's SMS campaign, you should normally contact the organisation that determined its purpose; Intellipush assists the customer under the agreement and applicable law.

### Automated decisions

Intellipush does not make decisions as a controller that are based solely on automated processing and produce legal or similarly significant effects for you. Technical security controls may automatically restrict suspicious activity, but relevant cases may be reviewed manually.

### Children and young people

The service is designed for organisations and is not marketed to children. Customers planning processing or communications directed at children must make a separate assessment of lawfulness, risk, language and security before use. High-risk use may require written clarification with Intellipush or may be rejected under the Acceptable Use Policy.

### Security and breaches

We use organisational and technical measures appropriate to the processing and risk. A high-level description is available on the security page. If a personal-data breach occurs, we follow applicable notification duties. When acting as processor, we notify and assist the customer in accordance with Schedule 1 and the law.

### Changes to this notice

The notice is reviewed at least annually and when the processing or law changes materially. The current version and effective date appear at the top of the page. Material changes will be communicated in an appropriate way, depending on their significance and the customer relationship.

Source: https://www.intellipush.com/en/privacy-policy/

## Security and vulnerability reporting

Version 2026.08; effective 2026-08-18.

This page describes documented security controls at a level that is useful to customers without publishing details that could weaken security. The controls reduce risk but are not a certification, SLA or guarantee against incidents.

### Controls currently in use

Privileged administrative access is protected by multi-factor authentication, and remote administration of the production environment takes place through a VPN. Access is granted according to need and can be attributed to authorised users. Production and staging environments are separated for customer content. Core infrastructure and backups are located with AWS in Ireland.

### Connections and integrations

The public website, customer portal, supported REST v2 API endpoints and supported callbacks use HTTPS for data in transit. The supported REST v2 authentication flow uses OAuth 2.0. Customers must protect credentials and follow the current integration requirements. Messaging-channel transport and downstream provider controls vary by channel and route. This is not a statement that SMS, standard email or voice delivery is end-to-end encrypted or that every data item is encrypted in the same way in every system.

### Customer account security

The customer must protect passwords, API credentials and other access information, restrict access according to need, and remove access when no longer required. Secrets must not be placed in public client code or shared through insecure channels. Suspected misuse must be reported to info@intellipush.com as soon as possible.

### Messaging channels

Ordinary SMS and standard email are not end-to-end encrypted, and message content may be visible to anyone with access to the receiving device or account. Voice messages may be heard by anyone with access to the receiving telephone or voicemail. Avoid sensitive personal data, complete credentials and other confidential content in the message itself. Use neutral wording and an appropriate authenticated service where the content requires stronger protection.

### Files shared by link

Where a customer uses a feature that shares a file by link, the file is public to anyone who has the link. The link has high entropy, is not listed in a public directory and is configured not to be indexed. The customer can revoke or delete the file. Do not use this model for secret, sensitive or high-risk content without a separate assessment.

### Temporary files and backups

Temporary import files are automatically deleted within seven days. Production backups expire through a 14-day cycle. Backup is a resilience control, not a customer-accessible archive. Planned restore and re-deletion exercises form part of the improvement programme and must not be understood as an already guaranteed public control.

### Testing and follow-up

An external penetration test has been completed after a security-hardening phase. Remediation work is prioritised according to risk and remains part of the security improvement programme. This describes one completed test and does not imply certification, continuous testing, a fixed future frequency or the absence of vulnerabilities.

### Abuse and messaging security

The platform has blacklists, suppression following opt-out and campaign limits that help reduce abuse. We may investigate complaints and unusual activity and restrict or suspend use under the terms. Identifiable recipient data from customer campaigns is not reused for Intellipush's own marketing; non-identifying aggregated service statistics may be used for operations and improvement.

### Incidents and personal-data breaches

Potential incidents are assessed according to severity and affected data. We work to contain harm, preserve necessary records, address causes, and notify customers or authorities where the agreement or law requires it. We do not promise 24/7 staffing or a specific public response time unless this is set out in a separate agreement.

### Report a potential vulnerability

Send a concise description to info@intellipush.com with the subject “Security”. State the affected service, method and potential impact without unnecessary personal data. Do not extract data, alter another person's information, disrupt the service, use social engineering or publish details before the matter has been assessed.

### Improvement programme

The security programme is reviewed at least annually and following material changes. Priorities include multi-factor authentication for customer accounts, regular restore and re-deletion exercises, stricter callback-destination restrictions, more granular country and use controls, and additional automated abuse protection. These are directions of work, not promises of a feature, date or contracted service level.

Source: https://www.intellipush.com/en/security/
