Voted Best Answer
Apr 15, 2016 - 02:31 AM
There are a few key issues that build on Ian’s general point. Firstly, with piracy rates close to 80% some software companies simply refuse to trade with Egypt. So as Ian says review your proposed stack and then discuss with each publisher. Secondly, you will need to cross check this with your own government as some countries have bans in place for some software trade to Egypt, the UK blocked a number of export licences to Egypt in 2013, 2014 & 2015 for many items including “specialist software and communications equipment."
Additionally, it is very likely that any licence agreement will be subject to the jurisdiction of & law of a country other than Egypt. For IBM this is England & English law; if you are a US company this may well be an issue if you have limited representation in The UK.
With our customers, primarily in banking & manufacturing (like yourselves) we recommend the use of locked down virtual infrastructure based out of country where possible. Manufacturing equipment with embedded software was also problematic as some were refused government export certifications and some companies refused to trade with Egypt due to piracy concerns. When we last addressed this there was no definition of sensitive personal data; nor was there a national authority, responsible for data protection in Egypt, that might cause problems for holding personal data out of country. You would of course need local legal advice on what the current legal & data protection requirements are as things have been in flux in Egypt the last few years.
In summary - and this is the model you can repeat for any jurisdiction globally - talk to each publisher for their unique position, talk to US International Trade Administration for the legal position you must follow and lastly find a US lawyer with an Egypt relationship as if things do go pear shaped it will be a lot easier and cheaper for you to chase the US lawyer….