Who we are and what this policy covers
Aimfox is a LinkedIn outreach platform operated by SocialGrowth LLC FZ, Meydan Grandstand, 6th floor, Meydan Road, Nad Al Sheba, Dubai, United Arab Emirates. In this policy, “Aimfox”, “we” and “us” mean SocialGrowth LLC FZ.
We handle personal data in two different roles. Which one applies depends on whose data it is and why we hold it.
| Role | Whose data | What it means |
|---|---|---|
| Controller | Our account users, billing contacts, website visitors, people who contact us, job applicants | We decide why and how the data is used. This policy explains that use. |
| Processor | People our customers reach or talk to through Aimfox (LinkedIn prospects and contacts), and the content of their campaigns and conversations | Our customer decides why and how the data is used. We act only on the customer’s instructions, under our Data Processing Agreement. |
This policy applies to aimfox.com, the Aimfox web app, and our sales, support, marketing and recruitment activities. It does not cover how our customers use Aimfox; their own privacy notices do. Section 4 explains what that means if you were contacted through Aimfox.
We do not run LinkedIn and are not affiliated with LinkedIn Corporation. Data on LinkedIn itself is covered by LinkedIn’s privacy policy.
Personal data we collect as controller
We collect only what we need for the purposes in section 3. This table lists it by the group of people it is about.
| Group | Data | Source |
|---|---|---|
| Account users | Name, email, password (stored hashed), workspace, role, settings, product usage, support conversations | You, and our systems as you use the app |
| Connected LinkedIn seats | The seat owner’s LinkedIn profile details and the session data needed to run the seat on their behalf | The seat owner, when they connect the seat |
| Billing contacts | Name, company, billing address, VAT number, invoices, subscription history. Card details are held by our payment providers, not by us. | You and our payment providers |
| Website visitors | IP address, browser and device details, language, referring page, pages viewed, approximate location from IP, cookie identifiers | Our website, cookies and similar tools (section 9) |
| People who contact us or book a call | Topic, message, name, email, company (optional), meeting time | You |
| Job applicants | Name, email, location, time zone and working hours, LinkedIn profile URL, role, reason for applying, start date, browser user agent, campaign tags | You |
| Business prospects for our own sales and marketing | Name, job title, company, business email, LinkedIn profile URL | Public professional sources, LinkedIn, events, referrals, marketing partners |
We do not ask for special category data, such as health, religion or political views. Please do not send it to us.
Why we use it and our legal basis
Each use below relies on one legal basis under the EU and UK GDPR. Where we rely on legitimate interests, we have weighed them against your rights, and you can object at any time (section 8).
| Purpose | Legal basis |
|---|---|
| Create and run your account, connect LinkedIn seats, provide the service | Contract |
| Billing, invoicing, tax and accounting records | Contract; legal obligation |
| Customer support, including live chat | Contract |
| Service emails (security alerts, billing, product changes) | Contract |
| Keep the service secure, prevent fraud and abuse, enforce our terms | Legitimate interests |
| Product analytics and improving Aimfox | Legitimate interests |
| Website analytics and non-essential cookies | Consent |
| Marketing emails to customers about similar Aimfox products | Legitimate interests (opt-out in every email) |
| Marketing emails to people who are not customers | Consent, or legitimate interests where local law allows business-to-business marketing |
| Targeted advertising and affiliate tracking | Consent |
| Publish testimonials | Consent |
| Reply to enquiries and booked calls | Legitimate interests, or steps before a contract |
| Assess job applications | Steps before a contract; legitimate interests |
| Respond to legal requests, defend legal claims | Legal obligation; legitimate interests |
We do not make decisions with legal or similarly significant effects about you based solely on automated processing.
We do not sell personal data, and we do not share it for cross-context behavioural advertising except through the advertising cookies you consent to.
Data we process for our customers
When customers run campaigns in Aimfox, they are the controller and we are their processor. Our Data Processing Agreement governs this data, and the DPA prevails over this policy if they differ.
This data includes:
- Business profile details of people the campaigns reach: name, job title, company, location, headline, profile photo, LinkedIn profile link and identifier
- Connection requests, messages and replies, and other conversations on a connected seat that the platform syncs
- Lead lists, tags and notes the customer adds
- Campaign status and analytics
We use this data only to provide Aimfox to that customer. We do not use it for our own marketing, we do not sell it, we do not combine it across customers, and we do not use it to train AI models. We delete it when the customer deletes it, and within 30 days after their subscription ends (section 7).
If you were contacted through Aimfox
If you received a LinkedIn invitation or message sent through Aimfox, the person or company that sent it decides how your data is used. They are responsible for telling you about it and for answering your requests.
- To find out what data they hold, object to their outreach, or ask for deletion, contact the sender directly.
- If you can’t reach the sender, or don’t know who they are, email us at team@aimfox.com. We will pass your request to the customer within 5 business days and help them answer it.
- You can also stop most outreach on LinkedIn itself by declining the invitation, removing the connection or blocking the sender.
AI features
Aimfox can write message lines with AI when a customer turns this on. To do that, we send the AI provider the inputs the customer chooses, which can include a prospect’s public profile details and the customer’s own instructions.
- Our AI provider is OpenAI, L.L.C. (United States), used through its business API.
- When a customer translates a message, we send its text to Google Cloud Translation.
- OpenAI processes API inputs and outputs under its business terms and does not use them to train its models; it retains them for up to 30 days for abuse monitoring.
- AI-written lines are suggestions the customer controls. Aimfox does not use AI to make decisions about people that have legal or similarly significant effects.
How long we keep data, and how we protect it
We keep personal data only as long as the purpose needs, then delete or anonymise it.
| Data | How long |
|---|---|
| Customer campaign data (section 4) | For the subscription; deleted within 30 days after it ends, or sooner on the customer’s instruction |
| LinkedIn session data for a connected seat | Until the seat is disconnected, then deleted |
| Account data | For the subscription; deleted within 30 days after it ends, like campaign data |
| Billing and tax records | 5 years, or longer where tax law requires |
| Support conversations | 2 years after the last message |
| Enquiries and call bookings | 2 years after the last contact |
| Job applications | Until the role is filled, and at most 2 years |
| Marketing contacts | Until you opt out, then kept on a suppression list so we don’t contact you again |
| Security and access logs | 12 months |
| Backups | Deleted data drops out of backups within 30 days |
Security
Our measures include:
- Encryption in transit (TLS 1.2 or higher) and at rest, including backups
- Access to customer data limited to named staff who need it, with multi-factor sign-in and access reviews at least every six months
- Separation of each customer’s workspace from every other
- Logging of staff access to customer data
- Security patches within 30 days of release, and a security test of the platform at least once a year
- Confidentiality duties and data protection training for all staff
No system is perfectly secure. If you think your account has been compromised, contact us at once.
Data breaches
If a breach affects customer data, we tell the customer without undue delay and in any case within 24 hours of becoming aware of it. Where a breach affects data we control, we notify the supervisory authority within 72 hours where the law requires it, and we tell affected people when the risk to them is high.
Your rights
Depending on where you live, you can ask us to:
- Give you a copy of your personal data (access)
- Correct it (rectification)
- Delete it (erasure)
- Limit how we use it (restriction)
- Send it to you or another company in a machine-readable format (portability)
- Stop using it on the basis of legitimate interests, and stop direct marketing at any time (objection)
- Withdraw consent you gave. This doesn’t affect use before you withdrew it.
To use these rights, email team@aimfox.com. We answer within one month, and may extend that by two months for complex requests; we will tell you if we do. We may ask you to confirm your identity. If your data is customer campaign data (section 4), we pass your request to the customer.
You can unsubscribe from marketing emails with the link in any of them. You can also manage cookies through your browser settings and through the cookie banner on our website.
You also have the right to complain to a supervisory authority: in the EU, the authority in your country; in the UK, the Information Commissioner’s Office. We’d appreciate the chance to fix the problem first.
US state privacy rights
Residents of California and other US states with privacy laws can ask to know, access, correct and delete personal data, and to opt out of its sale, sharing for targeted advertising, or profiling. We do not sell personal data. We will not treat you differently for using these rights. You can use an authorised agent, and we may ask them to prove they act for you.
California “Shine the Light”. Under California Civil Code section 1798.83, California residents can ask us, once a year and free of charge, which categories of personal data we disclosed to third parties for their direct marketing in the previous calendar year, and the names and addresses of those third parties. Send your request in writing to team@aimfox.com.
Children
Aimfox is a business tool for people aged 18 and over. We do not knowingly collect data from anyone under 18. If we learn that we have, we delete it.
Changes to this policy
We update this policy when our practices or the law change, and we show the date of the latest version at the top. For material changes, we tell account users by email or in the app at least 30 days before they take effect.
Contact us
Sub-processors
This list shows the third parties that process personal data for Aimfox, where they are, and what they handle. It forms Annex III of the Aimfox Data Processing Agreement.
- Last updated
Sub-processors for customer data
These providers process personal data that Aimfox handles for its customers under the DPA.
| Sub-processor | Purpose | Location | Customer data it handles | Transfer safeguard |
|---|---|---|---|---|
| Microsoft Corporation (Azure) | Application and database hosting | United States | All | EU-US Data Privacy Framework; SCCs in Microsoft’s DPA |
| OpenAI, L.L.C. | AI-written message lines | United States | Profile data and instructions sent for AI lines, only where the customer uses them | SCCs (in the provider’s DPA) |
| Google LLC (Cloud Translation) | Translating messages | United States | Message text sent for translation | EU-US Data Privacy Framework |
| Functional Software, Inc. (Sentry) | Error monitoring | United States | Data in error reports | EU-US Data Privacy Framework |
| Intercom, Inc. | Support chat | United States | What a user writes in a support chat | SCCs (in the provider’s DPA) |
| Customer.io | Service emails and product events for platform users | United States | Platform users’ contact details and usage events | SCCs (in the provider’s DPA) |
| Brevo (formerly Sendinblue) | Service emails to platform users | France | Platform users’ contact details | Within the EU |
| Mixpanel, Inc. | Product analytics | United States | Platform users’ usage data | EU-US Data Privacy Framework |
| Userback Pty Ltd | In-app feedback | Australia | What a user submits as feedback, which may include screenshots | SCCs |
| Google LLC (Google Analytics 4, via Google Tag Manager) | Product and web analytics | United States | Platform users’ usage data | EU-US Data Privacy Framework |
Other providers
These providers handle only data Aimfox controls itself, such as billing contacts and website visitors. They never receive customer campaign data. They are listed for transparency and are covered by the Privacy Policy.
| Provider | Purpose | Location |
|---|---|---|
| Chargebee | Subscription management | United States |
| Stripe | Payments and invoicing | United States |
| Braintree (a PayPal service) | Payments | United States |
| PayPal | Payments | United States |
| Apple Pay | Payments | United States |
| Google Ads and Google Tag Manager | Paid advertising and tag management | United States |
| Stape | Server-side tag hosting for analytics and advertising | United States |
| Hyros | Advertising attribution | United States |
| Tapfiliate | Affiliate tracking | Netherlands |
| ClickCease | Ad fraud / click verification | United States |
| Vercel | Website and web app hosting (page files only) | United States |
| Supabase | Contact form and job application storage | EU (Ireland) |
| Calendly | Call scheduling | United States |
| Slack | Internal notifications about enquiries and job applications | United States |
Changes and objections
We update this list at least 30 days before a new or replacement sub-processor starts handling customer data, and we email customers who have signed the DPA. To get these notices at another address, email team@aimfox.com.
Customers may object to a change on reasonable data protection grounds within those 30 days, as set out in section 2.4 of the DPA.
Data Processing Agreement
- Version
Parties, scope and roles
This Data Processing Agreement (“DPA”) is between SocialGrowth LLC FZ, trading as Aimfox, Meydan Grandstand, 6th floor, Meydan Road, Nad Al Sheba, Dubai, United Arab Emirates (“Aimfox”), and the customer named in the signature block (“Customer”). It forms part of the Aimfox Terms of Service or other agreement under which Aimfox provides its platform to the Customer (the “Agreement”).
Scope. This DPA applies to personal data that Aimfox processes on the Customer’s behalf in providing the platform (“Customer Personal Data”), as described in Annex I. It does not apply to data Aimfox processes as controller, such as account and billing data, which the Aimfox Privacy Policy covers.
Roles. The Customer is the controller of Customer Personal Data, or a processor acting for its own clients. Aimfox is the Customer’s processor, or sub-processor where the Customer acts for its clients. Where the Customer is a processor, it confirms that its clients have authorised its instructions and this DPA, and it passes on to them any notice Aimfox gives under this DPA.
Definitions. “Data Protection Laws” means the EU GDPR (Regulation 2016/679), the UK GDPR and Data Protection Act 2018, the Swiss Federal Act on Data Protection, and any other data protection law that applies to the processing. “Personal data”, “processing”, “controller”, “processor”, “data subject”, “personal data breach” and “supervisory authority” have the meanings in the GDPR. “Sub-processor” means any third party Aimfox engages to process Customer Personal Data. “SCCs” means the Standard Contractual Clauses approved by Commission Implementing Decision (EU) 2021/914.
Customer responsibilities. The Customer is responsible for having a lawful basis for its outreach and for the instructions it gives, for giving data subjects the notice the law requires (including under Art. 14 GDPR), and for complying with LinkedIn’s terms and with marketing laws that apply to its campaigns.
Aimfox’s obligations as processor
Instructions. Aimfox processes Customer Personal Data only on the Customer’s documented instructions. These are the Agreement, this DPA, and the Customer’s use and configuration of the platform. Aimfox does not process it for its own purposes, sell it, combine it with other customers’ data, or use it to train or improve AI models, and it requires its AI providers not to do so either. If the law requires other processing, Aimfox tells the Customer first unless the law forbids it. Aimfox tells the Customer promptly if it believes an instruction breaks Data Protection Laws.
Confidentiality. Only Aimfox staff who need access to run or support the service can access Customer Personal Data. All of them are bound by confidentiality duties and trained in data protection when they join and at least once a year.
Security. Aimfox maintains the technical and organisational measures in Annex II. It may update them, but not in a way that lowers overall protection.
Sub-processors. The Customer gives general authorisation for the sub-processors listed in Annex III.
- Aimfox tells the Customer at least 30 days before adding or replacing a sub-processor that handles Customer Personal Data, by email and on the public list.
- The Customer may object on reasonable data protection grounds within those 30 days. The parties will then discuss it in good faith. If no solution is found, the Customer may end the affected part of the service and get a pro-rata refund of prepaid fees for it.
- Aimfox binds each sub-processor by written contract to data protection terms at least as protective as this DPA, and stays liable to the Customer for its sub-processors’ performance.
Data subject requests. If Aimfox receives a request from a data subject about Customer Personal Data, it passes it to the Customer within 5 business days and does not answer it except on instruction. Aimfox helps the Customer answer requests for access, rectification, erasure, restriction, portability and objection within 10 business days of the Customer’s request, through platform features where possible.
Personal data breaches. Aimfox notifies the Customer without undue delay, and in any case within 24 hours of becoming aware of a personal data breach affecting Customer Personal Data. The notice gives what Aimfox knows of the nature of the breach, the data and people affected, likely consequences, and the measures taken or proposed, and Aimfox adds detail as it learns more. Aimfox’s notice is not an admission of fault.
Other assistance. Aimfox gives the Customer the information it reasonably needs for data protection impact assessments and prior consultation with supervisory authorities, taking into account the nature of the processing.
Deletion and return. On the Customer’s instruction, and in any case within 30 days after the Agreement ends, Aimfox deletes Customer Personal Data, including from backups within the backup cycle, and confirms this in writing. Before the end of the Agreement, the Customer can export its data through the platform or ask Aimfox for an export. Aimfox may keep data only where a law binding on it requires it, and then keeps it confidential and processes it for no other purpose.
Audits. Aimfox makes available the information needed to show compliance with this DPA and Art. 28 GDPR. This includes answers to reasonable security questionnaires and summaries of its most recent security test. If that is not enough, or a supervisory authority requires it, the Customer may audit Aimfox, or appoint an independent auditor bound by confidentiality, once a year with at least 30 days’ written notice, during business hours, and at its own cost.
International transfers
Where data goes. Aimfox is based in the United Arab Emirates and hosts Customer Personal Data in the United States and Serbia. Sub-processors and their locations are in Annex III. None of these countries has a general EU adequacy decision, except US recipients certified under the EU-US Data Privacy Framework.
EU SCCs. For transfers of Customer Personal Data subject to the EU GDPR, the parties enter into the SCCs, which are incorporated into this DPA by reference:
| SCC clause | Choice |
|---|---|
| Module | Module 2 (controller to processor) where the Customer is a controller; Module 3 (processor to processor) where the Customer acts for its own clients |
| Clause 7 (docking) | Applies |
| Clause 9(a) (sub-processors) | Option 2, general authorisation, with 30 days’ notice (as in section 2.4) |
| Clause 11(a) (independent dispute body) | Optional wording not used |
| Clause 13 (supervisory authority) | The authority of the EU member state where the Customer is established; if it is not established in the EU, the authority under Clause 13(a) second or third paragraph |
| Clause 17 (governing law) | Option 1: the law of Ireland |
| Clause 18(b) (courts) | The courts of Ireland |
| Annexes I, II and III | Annexes I, II and III of this DPA |
Under Module 2 the audit, deletion and notice terms of this DPA give effect to Clauses 8.9, 8.5 and 8.6. Under Module 3, Aimfox’s notices go to the Customer, which passes them on to its clients.
UK transfers. For transfers subject to the UK GDPR, the parties enter into the UK International Data Transfer Addendum (version B1.0) issued by the Information Commissioner. Table 1 is completed with the parties in Annex I; Table 2 with the SCC choices above; Table 3 with this DPA’s annexes; and in Table 4 both parties may end the Addendum. Where a customer has signed its own UK Addendum with Aimfox on the same terms, that one applies.
Swiss transfers. For transfers subject to the Swiss FADP, the SCCs apply with these changes: the Swiss Federal Data Protection and Information Commissioner is the competent supervisory authority; references to the GDPR include the FADP; and “Member State” includes Switzerland, so that data subjects there can enforce their rights in Switzerland.
Transfer assessment. Aimfox has assessed the laws of the importing countries and applies the extra measures in Annex II, including encryption in transit and at rest, and a policy of challenging over-broad government requests. It gives the Customer a summary of this assessment on request.
General terms
Term. This DPA applies for as long as Aimfox processes Customer Personal Data, and ends when that data has been deleted under section 2.8.
Liability. Each party’s liability under this DPA is subject to the limits in the Agreement. Nothing limits a party’s liability to data subjects under the SCCs or Data Protection Laws, or any liability that cannot be limited by law.
Order of precedence. If documents conflict, this order applies: (1) the SCCs and UK Addendum, (2) this DPA, (3) the Agreement.
Governing law. Apart from the SCCs, which follow section 3, this DPA is governed by the law that governs the Agreement.
Changes. Aimfox may update this DPA to reflect changes in the law or its services, but not so as to reduce the protection of Customer Personal Data, and it gives the Customer at least 30 days’ notice.
Signatures
| Customer | SocialGrowth LLC FZ (Aimfox) | |
|---|---|---|
| Legal name | SocialGrowth LLC FZ | |
| Registered address | Meydan Grandstand, 6th floor, Meydan Road, Nad Al Sheba, Dubai, UAE | |
| Signatory name | ||
| Title | ||
| Signature | ||
| Date |
Parties and description of processing
A. Parties
| Data exporter | Data importer | |
|---|---|---|
| Name and address | The Customer, as in the signature block | SocialGrowth LLC FZ, trading as Aimfox, Meydan Grandstand, 6th floor, Meydan Road, Nad Al Sheba, Dubai, UAE |
| Contact | As in the signature block | team@aimfox.com |
| Activities | Runs LinkedIn outreach for itself or its clients on the Aimfox platform | Provides and hosts the Aimfox LinkedIn outreach platform |
| Role | Controller (Module 2) or processor (Module 3) | Processor (Module 2) or sub-processor (Module 3) |
B. Description of processing
| Item | Description |
|---|---|
| Data subjects | People the Customer’s campaigns reach on LinkedIn (business contacts and prospects); people in conversations on connected seats; owners of connected seats; the Customer’s platform users |
| Personal data | LinkedIn business profile data (name, job title, company, location, headline, profile photo, profile link and identifier); invitation and campaign status; messages and synced conversations; lead lists, tags and notes; seat owners’ LinkedIn session data; platform users’ name, email, workspace, role and usage |
| Sensitive data | None is sought. A conversation not started by a campaign may contain special category data a person chose to write. Safeguards: need-to-know access, no use for Aimfox’s own purposes, no AI training, deletion on instruction |
| Frequency | Continuous while the service runs |
| Nature of processing | Storing lead lists; sending connection requests and messages from connected seats; receiving, syncing and storing replies; generating message lines with AI on the Customer’s instruction; analytics; support; deletion |
| Purpose | To provide the Aimfox platform so the Customer can start conversations with business contacts |
| Retention | For the term of the Agreement; deleted within 30 days after it ends, or sooner on instruction (section 2.8) |
| Transfers to sub-processors | As listed in Annex III, limited to what each needs for its part of the service, for the same duration |
| Places of processing | United States and Serbia (hosting); United Arab Emirates (staff access); sub-processor locations in Annex III |
| Competent supervisory authority | As in section 3.2 (Clause 13); for UK data, the Information Commissioner’s Office; for Swiss data, the FDPIC |
Technical and organisational measures
Aimfox maintains at least these measures for Customer Personal Data.
| Area | Measure |
|---|---|
| Encryption | TLS 1.2 or higher in transit; encryption at rest for databases, files and backups |
| Access control | Role-based access limited to named staff who need it; multi-factor sign-in for staff access to production; access rights reviewed at least every six months; access removed on leaving |
| Separation | Each customer’s workspace is logically separate, so one customer cannot reach another’s data or keys |
| Logging | Staff access to customer data and admin actions on production are logged and kept at least 12 months |
| LinkedIn session data | Stored encrypted, used only by platform services, deleted when a seat is disconnected |
| Backups and continuity | Encrypted backups; redundant hosting; deleted data leaves backups within 30 days |
| Vulnerability management | Supported software versions; security patches within 30 days of release; security testing of the platform at least once a year |
| Staff | Confidentiality undertakings; data protection training on joining and at least yearly |
| Incident response | Documented process; customer notice within 24 hours of becoming aware of a breach |
| AI providers | Business API terms only; no training on customer data; minimum retention by the provider |
| Sub-processors | Assessed before use; bound by written data protection terms at least as protective as this DPA |
| Data minimisation | Only data needed for the service is collected; data deleted on instruction and at the end of the service |
| Government requests | Requests reviewed, challenged where over-broad, disclosed only as far as legally required, with customer notice unless forbidden |
Sub-processors
The Customer authorises the sub-processors listed under “Sub-processors for customer data” in the Sub-processors list, as it stands on the date this DPA is signed. Aimfox keeps that list current and gives 30 days’ notice of changes (section 2.4).
Providers listed under “Other providers” handle only data Aimfox controls, such as billing contacts. They are not sub-processors under this DPA.
