Privacy policy
How we collect, use, and protect your data. Plain language, no legal fog.
Last updated: April 3, 2026
1. Information We Collect
1.1 Personal Information
When you interact with our Site, we may collect personal information that you voluntarily provide to us, including:
- Name
- Email address
- Phone number
- Company name
- Any other information you provide when contacting us or signing up for our services
1.2 Non-Personal Information
We automatically collect non-personal information when you visit our Site, including:
- IP address
- Browser type and version
- Device type
- Referring URL
- Pages visited and time spent on the Site
- Cookies and similar tracking technologies
2. How We Use Your Information
We use the collected information to:
- Provide, operate, and improve our services
- Communicate with you about inquiries or services
- Personalize user experience
- Monitor and analyze Site usage to enhance functionality
- Ensure security and prevent fraudulent activities
3. How We Share Your Information
We do not sell your personal information. However, we may share it in the following circumstances:
- Service Providers: We may share information with third-party vendors who assist us in website hosting, analytics, and customer service.
- Legal Compliance: If required by law, we may disclose information to comply with legal obligations, enforce agreements, or protect our rights.
- Business Transfers: In case of a merger, acquisition, or sale of assets, your information may be transferred to a successor entity.
4. Cookies and Tracking Technologies
We use cookies and similar tracking technologies to enhance user experience and collect analytical data. You can disable cookies in your browser settings, but some features of the Site may not function properly.
5. Data Retention
We retain personal information for as long as necessary to fulfill the purposes outlined in this Privacy Policy, unless a longer retention period is required by law.
6. Security
We take reasonable precautions to protect your information. However, no data transmission over the internet is 100% secure. You acknowledge that you provide your information at your own risk.
7. Third-Party Links
Our Site may contain links to third-party websites. We are not responsible for the privacy practices of these external sites. Please review their policies before providing personal information.
8. Your Rights and Choices
Depending on your jurisdiction, you may have the right to:
- Access the personal information we hold about you
- Request correction or deletion of your information
- Opt out of marketing communications
- Withdraw consent for data processing To exercise these rights, contact us at me@pixelhomie.com.
9. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. Any changes will be posted on this page with a revised effective date. Your continued use of the Site constitutes acceptance of the updated policy.
10. Contact Us
If you have any questions about this Privacy Policy, you can reach us at:
Dima Golovenko · me@pixelhomie.com
FAQ
Before we
get started.
01 Do you also handle development?
No — I focus on what I’m best at: UX/UI and product design. But I deliver developer-ready Figma files with clean structure and clear interaction logic, so handoff to your dev team (or mine, on request) is smooth.
02 Do you work solo or with a team?
You work directly with me, start to finish — no account managers, no telephone game. For larger scopes I bring in trusted specialists, but the design and the communication stay with one person: me.
03 How do we actually work together?
Short, tight feedback loops. We agree on scope, I share work in progress regularly, and you always know what’s happening. I’m used to working async across time zones and keeping delivery on schedule.
04 Can I see the design before everything’s final?
Always. We don’t lock anything in until you’ve reviewed and approved the direction. No big reveals at the end — you’re in the loop the whole way.
05 What do you need from me to start?
A clear goal and access to context (existing product, users, references). If the brief is rough, that’s fine — part of my job is turning a fuzzy idea into a structured plan.